checkin 2026-10-17 (volt): follow-through -- queue_index.py's docstring claims rev-scoped after doc_census_check read 2 STALE + 1 SPLIT

checkins/2026-10-17-volt.md

@@ -610,3 +610,15 @@ rows = 11**, and 4 were already correct.
 Artifact: `/root/.hermes/wizard-outputs/volt/2026-10-17-exit-codes/decision.md` (with
 `matrix-before.txt`, `matrix-after.txt`, `sweep-on-HEAD-tools.txt`,
 `sweep-6ee8fce.{txt,json}`, `shortlog-{before,after}.txt`, `probe_exit_codes.py`).
+
+**Follow-through, same run (`2b36319`) — a claim my own append made stale, caught by the
+repo's own census.** `doc_census_check --repo . --rev HEAD --tools tools/queue_index.py`
+read **2 STALE + 1 INTERNAL SPLIT** in that tool's docstring: `:5` said the queue is
+**9,901** lines (it was 9,937 before this run's append and 9,953 after), and `:25` said Q53
+is first named *"46 lines before"* it is opened — a difference, which the census read as a
+claim of 46 lines against a nine-thousand-line queue. Both are now fixed the way this
+archive already requires, *name the rev with the number*: `:5` reads **"9,953 lines long at
+`39312c2`"** and `:25` states the two line numbers instead of their difference. Re-measured
+at HEAD after the commit: **0 STALE, 0 SPLIT, 11 claims, 1 REV_UNCHECKED** (reported, never
+counted as a defect). The stale `9,901` predates this run — my append only widened the gap —
+and the fix is deliberately rev-scoped so the next append cannot reopen it.