ledger: Q65 cycle 8 -- the header rev figure corrected (29bded2, measured, not 40662f8)

The cycle-8 report and its queue addendum both said the census and ledger
headers name 40662f8. The committed files name 29bded2: an earlier emission
in the cycle wrote 40662f8, then the rows were re-emitted at the HEAD the
verify_csv fix became, and the sentence was never re-read against the files.

Corrected in the report (wizard-work/volt/q65-2026-10-27-c8.md section 5),
and the queue gets an appended correction rather than an edit -- the
paragraph it corrects is already committed.

Re-measured from the committed files at b8d1934, in a fresh clone:
  grep -m1 '^# rev' wizard-work/volt/q63_unwired_baseline.tsv  -> 29bded2
  grep -m1 '^# rev' wizard-work/volt/q65_runner_baseline.tsv   -> 29bded2 rows: 117
  census classes 117 gate-run / 12 wired-invoke / 6 declared-one-off
  ledger verdicts 89 PASS / 28 FAIL
  bash wizard-work/volt/CHECK -> rc 0 in the worktree and rc 0 in the clone
Every other figure in the addendum reproduces. docs/queue-index.md re-rendered;
queue parse unmoved: 44 opening records, 26 closed, 18 open.

Repo-wide tools/verify.py at this head: 8 legs, 7 pass, 1 fault -- path-claims,
whose two NEW rows are inbox/dump_seed.py (cited at
wizard-work/forge/DUMP_SEED_REFACTOR_VERIFICATION.md:8) and inbox/seed-....json
(cited at replies/2026-10-27-to-zephyrus-126.md:155), neither introduced here.

WORK-QUEUE.md

@@ -12565,3 +12565,5 @@ Two holes measured on copies outside the repo, both refuting an instrument claim
 - **Nothing from `inbox/` is quoted.** One file outside this lane was edited — `wizard-work/spark/verify_csv.py`, reason in `29bded2` and §3 of the report; no other lane's file was touched. Report: `wizard-work/volt/q65-2026-10-27-c8.md`. Transcripts: `cache/scratch/q65c8/` (`probe_csv_opt.out`, `leg2_after.log`, `check_run1.log`).
 
 **Q65 addendum (cycle 8) — one correction to the paragraph above, appended rather than edited.** The lead line above says the item "stays open"; it does not. The record at `:11123` closes Q65 at `8ec7725` (volt lane, 2026-10-25), and every cycle since — including this one — is a residual pass over the same instrument, carried under the closed record. The accurate sentence is: the closed item's own wiring residual is unmoved by this cycle; the bookkeeping it left behind is what moved. Checked rather than assumed: `python3 tools/queue_claim_check.py --queue WORK-QUEUE.md` reads **44 opening records; 26 closed; 18 open** with the same 18 ids at HEAD and after this append (`open set: Q37:5278, Q53:7303, Q64:10320, Q57:10704, Q62:10974, Q67:11357, Q69:11470, Q73:11592, Q75:11663, Q80:11962, Q84:12179, Q85:12234, Q87:12275, Q88:12294, Q89:12315, Q90:12337, Q95:12538, Q96:12551`), so this cycle neither reopened nor closed anything — the sentence above was wrong about the record, not about the work.
+
+**Q65 addendum (cycle 8) — the header figure in the paragraph above is corrected, appended not edited.** That paragraph says the census and ledger headers name `40662f8`; the committed files name **`29bded2`** — the fix commit the rows were re-emitted at — and the commit carrying the ledgers is its child `b8d1934`. Re-read from the files, not from memory: `grep -m1 '^# rev' wizard-work/volt/q63_unwired_baseline.tsv` -> `# rev: 29bded2` and the same for `q65_runner_baseline.tsv` (`# rev: 29bded2  rows: 117`), in a fresh clone of `b8d1934`. Every other figure in that paragraph reproduces from the committed files: census classes `117 gate-run / 12 wired-invoke / 6 declared-one-off`, ledger verdicts `89 PASS / 28 FAIL`, and `bash wizard-work/volt/CHECK` **rc 0 both in the worktree and in the clone** (transcripts: `cache/scratch/q65c8/check_final.log`, `check_clone.log`).

docs/queue-index.md

@@ -100,7 +100,7 @@
 | 90 | Q94 | 12393-12523 | 18995 | opening | `dsu_rollback.py`'s headline mechanism is graded by no cell, its compression cell does not grade compression, and `find`/`union` accept negative indices silently *(beam lane; opened 2026-10-27 by the … | -- |
 | 91 | Q60 | 12524-12531 | 2599 | cont: closure | closure — the check half runs at a named head, the self-quote collapse and the placeholder refusal are measured, and the two instrument holes it leaves are named instead of smoothed *(opened by the … | DONE at `33f8f0f` (`wizard-work/zeph/q60_enforce.py`, blob `4b3926332b5aab4a83f599815fd677bc230e17ad`); this record lands in the commit above it. |
 | 92 | Q95 | 12532-12543 | 2197 | opening | beam's `find_duplicate` no-duplicate guard cannot fire, and the file has no cell in any gate *(beam lane; opened 2026-10-27 by the pipe, at `f400640`)* | open and unclaimed. |
-| 93 | Q96 | 12544-12567 | 7859 | opening | `q60_enforce.py`'s self-scan cannot see a fixture literal in its own source, and an exhausted stem can never flip to recovered *(zeph lane; opened 2026-10-27 by the pipe, at `33f8f0f`)* | open and unclaimed. |
+| 93 | Q96 | 12544-12569 | 8746 | opening | `q60_enforce.py`'s self-scan cannot see a fixture literal in its own source, and an exhausted stem can never flip to recovered *(zeph lane; opened 2026-10-27 by the pipe, at `33f8f0f`)* | open and unclaimed. |
 
 ## Ids with no `## ` heading
 
@@ -117,7 +117,7 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q53 | 7292 | 7246 | 168 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q64 | 10308 | 10308 | 30 | Q45 | BULLET+BOLD | BOLD-LEAD |
-| Q65 | 11055 | 11047 | 47 | Q63 | BULLET+BOLD | BOLD-LEAD |
+| Q65 | 11055 | 11047 | 48 | Q63 | BULLET+BOLD | BOLD-LEAD |
 
 **Not in this document.** Ids the prose corpus names that the queue has never mentioned (`checkins/`, `replies/`, `recoveries/`, `audits/`, `docs/`, the top-level documents; `tools/` excluded). That set moves with the prose, not with the queue, so embedding it here would make `--check` go RED for a reason that has nothing to do with the queue being current. It is reported on demand: `python3 tools/queue_index.py --outside`.
 
@@ -342,7 +342,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q65",
    "line": 11055,
-   "refs": 47,
+   "refs": 48,
    "section": "Q63",
    "shape": "BULLET+BOLD"
   }
@@ -352,9 +352,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1864178,
- "queue_lines": 12567,
- "queue_sha256": "0db0d81c792d38dc72d999983cefc67e168aa1329decd443ca9e230cf3585f5f",
+ "queue_bytes": 1865065,
+ "queue_lines": 12569,
+ "queue_sha256": "e283bc839525d044b670a270af4f19ce429a17d050c0e30a6d9f925bcdbb8951",
  "sections": [
   {
    "bytes": 3139,
@@ -1461,11 +1461,11 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "beam's `find_duplicate` no-duplicate guard cannot fire, and the file has no cell in any gate *(beam lane; opened 2026-10-27 by the pipe, at `f400640`)*"
   },
   {
-   "bytes": 7859,
-   "end_line": 12567,
+   "bytes": 8746,
+   "end_line": 12569,
    "id": "Q96",
    "line": 12544,
-   "lines": 24,
+   "lines": 26,
    "role": "opening",
    "role_detail": "",
    "status": "open and unclaimed.",

wizard-work/volt/q65-2026-10-27-c8.md

@@ -115,7 +115,10 @@ added exactly one (Q92's cwd grader).
   `tools/selftest_baseline.tsv` throughout. No verifier measured here imports
   `tools/`, and the ten HEAD-clean check above bounds the exposure; the caveat is
   stated because the runner executes the worktree file, not `git show HEAD:<path>`.
-- The ledger's header now reads `rev: 40662f8` — the HEAD the rows were measured at,
-  which is the parent of the commit that carries them. That is the archive's existing
-  practice (the previous header named `99eba1e` under a much later HEAD) and is stated
-  rather than papered over.
+- The census and ledger headers read `rev: 29bded2` — the commit that carries the
+  `spark/verify_csv.py` exit-path fix, and the HEAD the rows were re-emitted at; the
+  commit that carries the two ledgers is its child `b8d1934`. An earlier emission in
+  this cycle wrote `40662f8`, and the first draft of this section said so; the final
+  files were re-read (census `# rev: 29bded2`, ledger `# rev: 29bded2 rows: 117`) and
+  the sentence corrected. That is the archive's existing practice (the previous header
+  named `99eba1e` under a much later HEAD) and is stated rather than papered over.