feat(propose,cli): the coverage gap had one cause, and round 7's own decomposition did not reproduce

Round 7 named two open items: a table-block candidate displacing a declared
heading (26 041 characters between entries, `md` at 3 of 4 declared headings)
and 17 590 characters after the last entry, never examined. Measured on
`a364ef4`, the first premise does not reproduce and the second is not a
separate mechanism.

`md` recovers 4 of 4, not 3 of 4. D1 (`--keep-table-heading`) is the repair
for exactly the mechanism round 7 § 5 describes, and round 7 moved it into
the default in the same commit -- so § 5 is a pre-move measurement presented
as the post-move state. That is round 7's own trap, stated in its own report:
a number about a rule is a measurement of a configuration. Nothing held the
cell, which is why it could be wrong and stay wrong.

The remaining gap has ONE cause. Every rule closes a span against the NEXT
MARK; three steps then remove a mark after its neighbour's `end` was fixed
against it. The orphan check leaks 18 527 characters over 15 of 39 documents,
`fold_units` clause 1 leaks 7 514 between entries, and the same clause on the
last run leaks all 17 590 tail characters -- with `unit_fold=False` the corpus
tail gap is 0. Round 6 already established the principle (filter at admission,
let the mark above carry the text) and it was never applied post-filter.

`--close-span-gaps` states it once, after the fold, where every removal has
happened: a span runs to the next SURVIVOR, the last to the end of the text.
It adds no boundary. Measured: 43 631 characters (2.51 %) -> 0, entries
429 = 429, K2 concepts 436 = 436, the operator's folder 52 md = 52.

All four acceptance conditions hold at once. The 12-position reference is
label-identical -- 11 of 12 under |F|[3]=12 and 10 of 12 under |F|[3]=11,
both readings reported, not one position moved. hit@8 holds [1,1,1,1,1,-] on
the round 8 bundle (436), the round 7 default (436) and Arm B (629), and the
known-negative reproduces on the new bytes: `--no-tie-shared-rank` gives
[2,1,1,1,1,-].

The pin is rebuilt against the default that actually ships
(`K2-bundle-default-20260911`, 832 files, digest 8c93e5e3...); two independent
builds of it differ in nothing, `log.md` included.

Two measurement failures are recorded rather than hidden. The corpus identity
check first used `xargs` without `-print0`, every filename split on its
spaces, `shasum` read nothing, and both sides agreed on a digest of the
failure; a control against the digest of empty input separated them. And the
smoke build cannot prove the flag arrives -- the operator's folder has a
coverage gap of zero already, so `diff -rq` is 0 either way; the plumbing has
its own test on a document that has the defect.

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

tests/test_default_bundle_pin.py

@@ -7,10 +7,10 @@ guarantee it looks like was never held by anything.
 
 This file pins the CURRENT default: `--outline-run 3 --table-grid --unit-fold
 --drop-wrapped-outline --outline-gate --first-span-from-zero
---sheet-section-rows --keep-table-heading`, plus the reading side's
-`tie_shared_rank`. Round 6 moved the first five on 2026-09-09 and round 7 moved
-the last four on 2026-09-10, each after measuring hit@8 on exactly the bundle
-its own default produces.
+--sheet-section-rows --keep-table-heading --close-span-gaps`, plus the reading
+side's `tie_shared_rank`. Round 6 moved the first five on 2026-09-09, round 7
+moved four more on 2026-09-10 and round 8 moved the last on 2026-09-11, each
+after measuring hit@8 on exactly the bundle its own default produces.
 
 The gold set is LOCAL-ONLY and stays that way: no question and no
 `gold_document` is reproduced here, and a row is named by its INDEX, the way
@@ -37,10 +37,16 @@ import okf_consume_measure  # noqa: E402
 
 #: Built by:
 #:   okf build <corpus>/K2/trinn1 \
-#:       --bundle ~/corpora/okf-telling-20260829/K2-bundle-default-20260910 \
+#:       --bundle ~/corpora/okf-telling-20260829/K2-bundle-default-20260911 \
 #:       --bundle-id k2-trinn1-20260903 --okf-version 0.2
 #: with no arm flag at all -- the package default, which is the point.
-DEFAULT_BUNDLE = Path.home() / "corpora" / "okf-telling-20260829" / "K2-bundle-default-20260910"
+#:
+#: Rebuilt 2026-09-11 for `--close-span-gaps`. Digest, from inside the bundle:
+#:   find . -type f -print0 | sort -z | xargs -0 shasum -a 256 | shasum -a 256
+#:   -> 8c93e5e3222577a2b3352ca83af980e403d3a571c3a467b83c3d8170b1df2b69
+#: Two independent builds of it differ in NOTHING (`diff -rq`), including
+#: `log.md`, which carries the corpus path and never the bundle's own.
+DEFAULT_BUNDLE = Path.home() / "corpora" / "okf-telling-20260829" / "K2-bundle-default-20260911"
 GOLD_SET = PROJECT_ROOT / ".claude/projects/2026-09-07-okf-consume-prepass/hit-at-k-questions.json"
 
 requires_default_bundle = pytest.mark.skipif(
@@ -52,10 +58,12 @@ requires_default_bundle = pytest.mark.skipif(
     ),
 )
 
-#: Measured 2026-09-10 on the bundle above. The count moved 425 -> 436 with
-#: `--sheet-section-rows --keep-table-heading`; `--first-span-from-zero` moved
-#: it by NOTHING, which is the point of that rule -- it adds no boundary and
-#: only moves one span's start.
+#: Measured 2026-09-11 on the bundle above. The count moved 425 -> 436 with
+#: `--sheet-section-rows --keep-table-heading`; `--first-span-from-zero` and
+#: `--close-span-gaps` each moved it by NOTHING, which is the point of both --
+#: they add no boundary, they only move a span's start or its end. Round 8's
+#: rule closed 43 631 characters (2.51 % of the corpus) that were in no
+#: segment, and the count is byte-for-byte the same 436.
 EXPECTED_CONCEPTS = 436
 EXPECTED_HITS = 5
 #: Rank per question INDEX, `None` for the row that misses on every bundle and