timmy: queue appendix -- Q65's two unrowed verifiers closed at 92745b2 (103 of 103, CHECK rc 0, re-measured at a46547c), and a46547c's stray 218-byte path opened as beam's

WORK-QUEUE.md

@@ -11210,3 +11210,12 @@ The class: an invocation-shaped reference to the file exists from nowhere in the
 - **Green, measured at `8bb1aeb`:** `q63_verify_scan.py --repo .` — 103 committed, wired 10, gate-run 85 (FAIL 24, PASS 61), code-grep unwired 8, tolerance 8 `declared-one-off`, coverage **103 of 103**, `NEW 0`, **0 fault(s)**, rc 0. `q65_runner.py --check --class gate-run,undeclared` — **87 rows (PASS 63, FAIL 24)**, `graded 87 of 87`, `graded-clean 9 of 87`, host-pinned 54, `tree audit 0 unclassed of 103`, **0 fault(s)**, rc 0. `bash wizard-work/volt/CHECK` **rc 0**, `CHECK PASS: census covers every committed verifier; runner ledger grades clean.` Selftests **22/22** and **10/10**.
 - **Nothing closed early, and the remaining fault is named.** The forge file is still invoked by nothing — its census fault clears because it is *graded by execution*, Q65's own contract, not because a caller appeared (`git grep -F verify_scan_dry_refactor` still returns only its own prose doc). 54 `PASS*` rows remain Q62's class one per owning lane, 24 `FAIL` rows remain per-lane findings, and the census is still not a `tools/verify.py` leg — the operator's call at reply 93 §4, not re-argued here, and nothing in `tools/verify.py` noticed either reopening.
 - **Evidence:** `wizard-work/volt/q65-2026-10-25-c3.md` (§1 red, §2 the two gradings, §3 the four-hunk diff, §4 the host pin both ways, §5 the omission controls, §6 green, §7 what stays open); `q65-2026-10-25-c3-red.txt`, `-c3-green.txt`, `-c3-controls.txt`, `-c3-reemit.diff`; `git diff --numstat` `4 2` and `3 1` on the two ledgers. No other lane's file edited. Appended at the foot; `docs/queue-index.md` re-rendered in this commit.
+
+
+---
+
+**Q65's two unrowed verifiers closed at `92745b2`, 2026-10-25 (timmy) — census 103 of 103 and `volt/CHECK` rc 0, measured by a second lane at `a46547c`; and beam's `a46547c` adds one tracked path whose name is a mangled heredoc, so this tick closes one item and opens a small one.**
+
+- **Closed item: the Q65 census had two unrowed committed verifiers at `a14a132`, one of them unwired.** Done was defined as census **103 of 103**, `q65: 0 fault(s)` and `volt/CHECK` rc 0 at a tree where both files carry a graded row. `92745b2` meets it — volt graded both by execution through the runner, one run each (`verify_scan_dry_refactor.py` PASS rc 0 2.48 s, `verify_lcmm_dossier.py` PASS rc 0 6.20 s, ledger 85 → 87 rows) — and I re-measured it rather than accepting the record: clean clone of `a46547c`, `q63_verify_scan.py` **coverage 103 of 103**, `NEW 0`, **0 fault(s)**; `q65_runner.py --check` **87 rows (PASS 63, FAIL 24)**, graded 87 of 87, **graded-clean 9 of 87**, host-pinned 54, `tree audit 0 unclassed of 103`, **0 fault(s)**; `bash wizard-work/volt/CHECK` **rc 0**; selftests **10/10** and **22/22**. Finished by `92745b2`. The forge row stays `PASS*` (host pin `L38:/root/troupe-standup`) and the file is still invoked by nothing — its census fault cleared because it is graded by execution, which is Q65's contract, not because a caller appeared. The census is still **not** a `tools/verify.py` leg: nothing in the 8 legs noticed the reopening at `a14a132` and nothing will notice a fourth verifier landing without a row. That stays the operator's call at reply 93 §4, not re-argued here.
+- **Opened item: `a46547c` (beam) adds one tracked path that is a failed redirect, not a file.** Tree entry `100644`, **185 B**, blob `763936956721f3ba047d25b884f17862469482c3`; the name is **218 bytes** with **7 embedded newlines** and 7 double quotes, beginning `wizard-work/beam/CHECK` and continuing into the shell line that was meant to be the redirect and then the whole CHECK body. Its bytes are `30653c6:wizard-work/beam/CHECK` minus the trailing newline (`git cat-file` vs `git show`, one differing line, `\ No newline at end of file`), so nothing was lost and `wizard-work/beam/CHECK` itself is 186 B before and after. Ranked **repo hygiene, not a fault class**: at `a46547c`, `python3 tools/verify.py --repo .` is **8 legs, 8 pass, 0 fault** and `path_claim_check` is **1803 distinct, 27 missing, 0 new**; the path is not a `verify_*.py`, so the census is unmoved. What it does cost: `git ls-files` prints the name C-quoted as a single token beginning `"wizard-work/beam/CHE`, `git show`/`git diff` on it is unreadable, and a checkout onto a filesystem that refuses newlines in names fails on it alone. Done means no tracked path contains a newline and the removal is a commit of its own. Owner: **beam** — the file is another party's (`STANDING-AGREEMENT.md:86`), the ask is `replies/2026-10-25-to-beam-25.md`, and this tick did not touch it.
+- **Evidence:** `replies/2026-10-25-to-volt-54.md` and `replies/2026-10-25-to-beam-25.md` (the measurements in full); `wizard-work/volt/q65_runner_baseline.tsv` and `q63_unwired_baseline.tsv` as `92745b2` left them (87 / 8 / 8 = 103, counted from the TSV, not the prose); the clone readings above, all re-run at `a46547c`. Nothing from `inbox/` is quoted. No other lane's file was edited by this tick; the changed files are the two replies, this entry and `docs/queue-index.md`. Appended at the foot.

docs/queue-index.md

@@ -63,7 +63,7 @@
 | 53 | Q60 | 10830-10889 | 9719 | opening | Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)* | open and unclaimed. |
 | 54 | Q61 | 10890-10945 | 9624 | opening | beam's `topo_sort` drops generator dependencies, and its gate imports a copy outside the repo *(beam lane; opened 2026-10-24 by the pipe, per reply 88 to zephyrus)* | open and unclaimed. |
 | 55 | Q62 | 10946-10993 | 3717 | opening | 147 committed gates read `/root/.hermes/wizard-outputs`; two of them cannot pass from a clone *(no lane owns it; opened 2026-10-24 by the pipe, per reply 89 to zephyrus)* | open and unclaimed. |
-| 56 | Q63 | 10994-11212 | 71960 | opening | Six committed verifiers print PASS while asserting nothing, and eight are run by no gate *(no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)* | open and unclaimed. |
+| 56 | Q63 | 10994-11221 | 75435 | opening | Six committed verifiers print PASS while asserting nothing, and eight are run by no gate *(no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)* | open and unclaimed. |
 
 ## Ids with no `## ` heading
 
@@ -80,7 +80,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 | 165 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q64 | 10308 | 10308 | 28 | Q45 | BULLET+BOLD | BOLD-LEAD |
-| Q65 | 11055 | 11047 | 27 | Q63 | BULLET+BOLD | BOLD-LEAD |
+| Q65 | 11055 | 11047 | 30 | 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`.
 
@@ -250,7 +250,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q65",
    "line": 11055,
-   "refs": 27,
+   "refs": 30,
    "section": "Q63",
    "shape": "BULLET+BOLD"
   }
@@ -260,9 +260,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1581647,
- "queue_lines": 11212,
- "queue_sha256": "da672a09fa909fd7f06890c64bc86b170db85c8d5e0fc5dd17628039d8531fd0",
+ "queue_bytes": 1585122,
+ "queue_lines": 11221,
+ "queue_sha256": "ff0ef4d687a2741fad97cbdbc881acef9aec7b7a89d1d9461b166317fb252c36",
  "sections": [
   {
    "bytes": 3139,
@@ -925,11 +925,11 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "147 committed gates read `/root/.hermes/wizard-outputs`; two of them cannot pass from a clone *(no lane owns it; opened 2026-10-24 by the pipe, per reply 89 to zephyrus)*"
   },
   {
-   "bytes": 71960,
-   "end_line": 11212,
+   "bytes": 75435,
+   "end_line": 11221,
    "id": "Q63",
    "line": 10994,
-   "lines": 219,
+   "lines": 228,
    "role": "opening",
    "role_detail": "",
    "status": "open and unclaimed.",