feat(propose,cli): typography as a reserve, and the two of our own numbers it took to measure it

K3 round 5. Three questions, three answers, and two of them correct a figure
this repository published.

RETRIEVAL FIRST, because it could have reversed a default. hit@8 over the six
questions on BOTH K2 bundles -- Arm B at 629 concepts and the shipped default
at 492 -- is 5 of 6 with ranks 1,1,1,1,1,- on each, so 0 of 6 rows lost. The
order's rule reverses `--unit-fold` at >= 2 of 6; it does not fire, and the
default stands. The gold sets shrink (49->26, 20->17, 43->36, 11->18) while
every rank holds at 1, which is the fold merging concepts rather than removing
a document from the top.

TWO PUBLISHED NUMBERS CORRECTED, both ours. The S7 candidate ranks 96 of 629
and 159 of 492 were measured with the cost vocabulary passed to
`concept_scores` and NOT to `document_scores`, while `build_payload` passes it
to both; scored the way the shipped payload scores it, the same concept is 10
of 629 and 19 of 492. And round 4 attributed its non-delivery to the default
move -- measured here, it is not delivered on the Arm B bundle either, for a
different reason (knapsack eviction at 68 046 bytes of a 120 000 budget, versus
`below_k`). That column had been inherited from round 3's own build, never
re-measured.

`--pdf-headings font-reserve`, OFF, and the hypothesis behind it is falsified
by its own condition rather than by a score: position 7, the one position the
flag exists for, has THREE outline runs, so the reserve is silent there at
every minimum. It changes 0 of 12 cells on the reference and reaches 4 of 39
corpus documents, none of them rated. Built anyway because it was authorised
and because the condition is now measured rather than assumed. The predicate
lives in one place (`propose.heading_reserve_applies`) and the door receives it
as a callable, like `gate`: a plan indexes the exact string it was proposed
against, so a reserve firing on one side only would make every document it
touches a coded rejection.

The `xlsx` re-reading is confirmed on the artifact -- 11 `rule:sheet-section`
units plus 1 `rule:table-block` ingress -- but the number alone makes the cell
worse (distance 1 -> 2), because the criterion counts that ingress as a table
that should have been merged. A hit needs both halves ratified, and the
reference is the operator's.

`--sheet-section-rows` as a default: three cells better and none worse on the
twelve positions, but the K2 control moves -- row 1's gold document splits 1 ->
12 concepts and its best concept ranks 2 instead of 1. Condition not met,
default not moved.

Default build byte-identical before and after (`diff -r`, 30 md files).
Suite 1441 -> 1449; three of the eight were red first.

Report: docs/2026-09-08-k3-runde5-hitat8-og-skriftakse.md

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

CLAUDE.md

@@ -309,7 +309,7 @@ and fixtures, never code.
   `docs/2026-09-08-k3-arm-f-mot-enhetsarket.md`,
   `docs/2026-09-08-k3-runde2-per-filtype.md` and
   `docs/2026-09-08-k3-runde3-per-filtype.md`.
-- **Two PDF READER flags, both off, and they sit BEFORE every segmentation
+- **Three PDF READER flags, all off, and they sit BEFORE every segmentation
   flag** -- an arm changes how the proposer cuts a text, these change what the
   text says. `--pdf-headings font` infers a heading from typography (dominant
   font size above the document's character-weighted body median AND a bold font
@@ -335,6 +335,31 @@ and fixtures, never code.
   become a default -- an optional dependency in the default path would make an
   ordinary install fail on the first scanned page. Report:
   `docs/2026-09-08-k3-runde4-pdf-skrift-og-ocr.md`.
+  **`--pdf-headings font-reserve`** is the third value on that same option
+  (`none`, `font`, `font-reserve` — three answers to one question, so no caller
+  can ask for two at once): the same typographic rule applied ONLY where Arm D's
+  outline gate admits no run at all, typography as a second heading source where
+  there is no first one. The condition lives in ONE function
+  (`propose.heading_reserve_applies`) that the proposer and the door both
+  consult, the door receiving it as a callable the way it already receives
+  `gate` — a plan indexes the exact string it was proposed against, so a reserve
+  firing on one side only would turn every document it touches into a coded
+  rejection. It reads the gate AS CONFIGURED, so at `--outline-run 0` it is
+  unconditional and equals round 4's "font instead of Arm D". **Off, and the
+  measurement is that it changes nothing measurable:** on the twelve-position
+  reference it alters **not one cell** — the five positions where it fires are
+  one PDF whose glyphs carry no ToUnicode mapping and four office documents the
+  PDF reader never touches — and the position it was built for has **three**
+  outline runs, so the reserve is silent there by construction. Its reach is
+  real but unrated: **4 of 39** readable corpus documents, none in the sample.
+  Report: `docs/2026-09-08-k3-runde5-hitat8-og-skriftakse.md`, which also
+  corrects two of this repository's own published figures — the S7 candidate
+  ranks (96 of 629 / 159 of 492 were measured with the cost vocabulary reaching
+  only half the ranker; consistently scored they are **10 of 629** and **19 of
+  492**) and round 4's attribution of that concept's non-delivery to the default
+  move (it is not delivered on the Arm B bundle either, by a different
+  mechanism). hit@8 over the six published questions holds at **5 of 6 on both
+  K2 bundles**, so the default move cost the retrieval side nothing.
 - Consume a bundle: `okf consume <bundle> --question "<q>"
   [--k N] [--limit N] [--out PATH] [--ref IDENTITY]` — the **pre-pass**
   `docs/consumption-contract.md` § 1 defines, and the only reading direction