Quimper, France

# OT New Article Writing Agent
**Project Instructions · Odyssey Traveller Content Operations · September 2026 (v2.15)**

—

## Changelog — v2.15 (18 September 2026)

Adds a placement variant for shorter articles, found while fixing Quimper, France.

– **On short articles (roughly under 800 words, the same rough boundary the old
proportionality exception used), the two blocks sit differently than on a full-length
article:** the tour CTA moves down, below the first 3–4 paragraphs rather than
immediately after the opening paragraph, and the Tour Specialist block moves to the
very end of the article — after the last body paragraph, before any closing
“articles about X” / external-links boilerplate — rather than the natural halfway
point.
– **Why:** on a short page, a full hero CTA landing immediately after one short opening
paragraph is front-loaded and crowds the actual content; letting the reader get a
little further into the piece first, then closing with the Tour Specialist invitation
once they’ve read the whole thing, reads more naturally.
– **Full-length articles are unchanged:** tour CTA immediately after the opening
paragraph, Tour Specialist block at the natural halfway point, exactly as before.
– **This only changes placement, not the v2.14 rule that both blocks are always
present.** Short articles still get both, unconditionally — just positioned lower and
at the end respectively instead of top-and-middle.

—

## Changelog — v2.14 (18 September 2026)

Removes the last two carve-outs under which an article could end up with no tour CTA.
David’s direction: **every article gets a tour CTA and a Tour Specialist block, always,
full stop — no length exception, no “no current tour” exception.**

– **The ~800-word proportionality exception is repealed.** v2.13 already made the two
blocks unconditional for the multi-tour case; this closes the remaining gap. A short
destination guide no longer gets just the Tour Specialist block — it gets both, the
same as every other article. If a full-width CTA looks disproportionate on a very
short page, that’s a length problem to flag, not a reason to drop the block.
– **”Article’s destination is not on any current tour → do not add” is repealed.** Every
article gets a tour CTA. When an existing article being audited has no `Tour Name` /
`Tour URL` set, this is no longer a reason to skip the CTA — it’s a gap to close.
Stop and ask David which tour fits best (the same “stop and ask” already used when
these fields are empty on a new article), rather than defaulting to Tour Specialist
only. If the destination genuinely isn’t on any current itinerary, ask whether the
nearest relevant tour (by geography or theme) should be used, or whether this is a
multi-tour case.
– **The “Unsure → flag it, do not add” line is repealed for the same reason.** Being
unsure which tour fits is a reason to ask, not a reason to leave the CTA off. The
multi-tour selection gate already exists for exactly this situation — use it instead
of skipping.
– **Net effect:** the sweep table’s item 11 changes from “conditional, do not add by
default” to unconditional. The single remaining judgement call is *which* tour (or
tours) to use, decided via the existing single-CTA / multi-tour-gate logic — never
*whether* to add one.
– **Quimper, France was fixed under the old v2.13 rule (both exceptions) earlier this
session — it now needs a second pass** to add the tour CTA that was correctly withheld
under the old rule but is required under this one. Any other article fixed under the
old proportionality or no-current-tour exceptions during this sprint needs the same
revisit.

—

## Changelog — v2.13 (18 September 2026)

Corrects a standing-rule error found while fixing the Marmottan Monet Museum article’s
multi-tour CTA, and documents a new WordPress paste-failure pattern found in the same
session.

– **The multi-tour card does NOT replace the Tour Specialist block. Every article gets
both, always.** v2.6 stated the multi-tour card replaces the Tour Specialist block “so
the reader isn’t prompted twice.” That rule is wrong and is reversed here: David has
confirmed the standing practice is a tour CTA (single **or** multi-tour) near the top of
the article, immediately after the opening paragraph, **and** a separate Tour Specialist
block at the natural halfway point — unconditionally, on every article, with no
exception for the multi-tour case. Any article previously built to the old “replaces”
rule is missing a block and should get one added next time it’s opened.
– **New known WordPress paste-failure pattern: the first `` tag in a post’s body can
be silently stripped on save, regardless of its URL, alt text, or surrounding markup.**
Found on the Marmottan Monet Museum article: a multi-tour CTA’s first row image
vanished from the live page across five different attempts — a fresh cache-busted URL,
a brand-new re-uploaded image with a new attachment ID, removing all blank lines in the
block, and restructuring the div nesting. None of it mattered. Swapping the row order
proved the bug is positional, not content-based: whichever image is the first ``
anywhere in the post body gets eaten on save; the second (and any later) image is
unaffected. Root cause is unconfirmed (most likely a theme or SEO-plugin routine that
auto-detects “the first content image” for an og:image/thumbnail fallback and strips
the literal tag to avoid a duplicate), but the workaround is reliable: **insert a tiny,
visually-hidden 1×1 decoy `` at the very top of the post body, before the H1**,
referencing any real, already-uploaded site image. That decoy becomes the true first
image and absorbs the strip, leaving every real image in the article — including the
first row of a multi-tour CTA — intact. Add this decoy any time an article’s very first
visible image (a CTA row image, a figure early in the body) goes missing after ruling
out URL and markup causes. Decoy markup:

“`html

“`

Place it immediately after the `