fix(consume): a covered title rises only past titles that answer no more of the question

Round 16's partition read every concept whose WHOLE title the question
accounts for before everything the fusion ranked above it. That is a claim
about the covered title's PRECISION, and it overrode the fusion even against
a title answering MORE of the question. Measured on a 26-concept bundle of
five documents: the question names a section by three title tokens and holds
a neighbour's whole one-token title (1 of 9 question tokens); the fusion put
the named section at rank 1, the partition moved the neighbour over it.

A covered concept now RISES through the fusion's order and stops beneath the
first concept whose title answers more question tokens, by equality, than it
holds, or beneath a covered concept the fusion put above it. With nothing
above it answering more it reaches the top exactly as before. Same flag
(--title-covered / --no-title-covered), no new parameter, no new constant.

Measured before this commit, delivered ranks from build_payload:
- known-negative: rank 2 -> 1; the payload equals --no-title-covered's
- three own probes on that bundle: 1, 1, 1 (unchanged from round 16)
- R761 XML, 2 761 concepts: hit@1/8/50 6/6 - 6/6 - 6/6 at default k and at
  --k 50, KP rank 1; 8 of 8 payloads byte-identical to 7cca9e0 at BOTH k
- payloads byte-identical to 7cca9e0: K2 pinned 6/6, Arm B 6/6, N100/N200/
  N500 15/15; tests/test_default_bundle_pin.py 7 passed, file untouched
- candidates measured beside it: min title length (R761 hit@1 3/6), share of
  the question (holds only for 1/9 < s <= 1/6), order inside the group
  (group of one: no effect), stop list (no title involved is one)

Suite on the staged set: 1600 passed, 1 skipped.

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

README.md

@@ -454,6 +454,22 @@ bundle and on **0 of 21** measured cells across the pinned K2 bundle, Arm B and
 the three N bundles, whose payloads are byte-identical either way.
 `docs/2026-09-10-k3-runde16-hele-tittelen-tar-ruten.md`.
 
+**Since round 17 the partition is bounded by RECALL**, under the same flag. A
+covered title states its PRECISION — it says nothing the question did not ask —
+and round 16 let that claim override the fusion even against a title answering
+MORE of the question: on a 26-concept bundle of five tender documents, a
+question naming a section by three of its title tokens also held a neighbour's
+whole one-token title, and the neighbour took rank 1. A covered concept now
+rises through the fusion's order and stops beneath the first concept whose
+title answers more question tokens, by equality, than it holds. On the
+standard's bundle nothing stood above a covered concept answering more, so its
+8 payloads are byte-identical at both `k`; the 27 payloads where the rule never
+fires are byte-identical too. A minimum title length, a share of the question,
+an order inside the group and a stop list were measured beside it and not
+taken. 0.8.1's unbounded order is reproducible by no flag;
+`--no-title-covered` still gives the pre-0.8.1 order.
+`docs/2026-09-11-k3-runde17-dekningen-stopper-ved-en-bredere-tittel.md`.
+
 It emits the § 8 shape — `contract`, `bundle` (`bundle_id` plus a
 `sha256-tree:` content identity), `budget` (unit, instrument, limit, spent and a
 validated known-positive), `denominators`, `excerpts` and `withheld` — and every