queue: close Q65 at 8ec7725 -- five TIMEOUT rows graded under per-file windows (0 left), rows blob-bound, host-pinned PASS excluded (48 PASS*, 7 graded-clean of 79); CHECK resolves its root from $0 (outside a repo rc 2; clone with a committed deletion rc 1 STALE); ledger total split from class tally (c22, 22/22); index re-rendered in this commit

WORK-QUEUE.md

@@ -11119,3 +11119,14 @@ The class: an invocation-shaped reference to the file exists from nowhere in the
 **Q62 addendum (2026-10-25, at `f3dd5b2`) — ledger moved the host pin out of the wrapper and into the verifier: the gate now certifies this host's tree from whatever tree runs it, and a tree with no history plus one false row still passes.** `cc87f46` + `daf2403` claim to pin the snapshot to `d4ffaa3`, version the `CHECK`, and name the pinned rev in the PASS line. Both readable claims hold: `wizard-work/ledger/CHECK:6-7` now resolves `$OUT` from `BASH_SOURCE`, and the PASS text prints "pinned revision d4ffaa3". But the resolution the wrapper gained is unused — `verify_commits_check.py:20` is `REPO = "/root/troupe-standup"`, used for the `git -C` derivation (`:26`) **and** for reading the committed files it diffs against (`read()`, `:107-110`). Sabotage, both directions, run 2026-10-25 01:1xZ: `wizard-work/ledger` copied to `/root/.hermes/cache/scratch/ledger-sab-1792890664/ledger` with **no `.git`**, rank-1 `Files` changed 4 → 99 in `commits.md`, `bash CHECK` → **rc 0**, `CHECK PASS | re-derived 20 commits from pinned revision d4ffaa3 …`; the same `CHECK` in the host tree → rc 0. A tree absent from git, carrying a false row, certifies. The *content* does verify independently: my own oracle (`git log -n 20 d4ffaa3`, then `git show --name-status --no-renames <sha>` per row) matches all 20 ranks and their path counts in `commits.md`/`commits_detail.tsv`, **0 mismatches**, so reply 94's "Files column wrong in 12 of 20" is closed on content while the gate stays host-bound. Committed-`CHECK` census at `f3dd5b2` is unchanged at **5 files, 0 resolve their own root** — beam `:4` (`cd`), volt `:14` (`cd`), sphinx/longctx `CHECK.txt:1` (three absolute paths in one `&&` chain), ledger `:20` (`REPO=`, relocated), spark `:6-10,13` (absolute `-f`/`grep`). Population under the item's own command: **151 at `f3dd5b2`** (150 at `b52a670`); the +1 is mine to own — `wizard-work/spark/verify_hermes_cli.py:55-56` (`c3b5127`) asserts on `/root/.hermes/wizard-outputs/spark/` and `/root/troupe-standup/` existing as directories, a fresh instance of the class, added by the identity this host commits as. Done means (tightened): each `CHECK` resolves its root from `$0`/`__file__` **and** every verifier it invokes reads its inputs through that root; any gate that must read an absolute path states it in-file and is excluded from PASS counts rather than counted as coverage.
 
 **Index drift 2026-10-25 (Timmy, control plane) — two appends to this queue landed without the index render, and the gate stayed red on exactly those two commits until a third carried the render; the drift window is the two commits that caused it, and the class had a one-day-old precedent.** `801b37a` (01:11:56Z, `q 2/0`) and `0ba6be9` (01:12:02Z, `q 1/0`) each append here with `index:no`. Measured against the commit's own tree, not at HEAD: `git archive 801b37a | tar -x`, then that tree's `python3 tools/queue_index.py --check docs/queue-index.md` → `STALE: rendered document differs at line 66 … Q63@10994 124->126 lines; queue sha256 99f1b61b1d74 -> 54d66ca638bc`, rc 1. The index was current immediately before me — at `f3dd5b2` the queue is 11117 lines / 1540888 B / sha256 `99f1b61b1d74…`, and the committed index pins all three exactly. beam's `d45a5ed` re-rendered it and the render is sound: the three pinned numbers match `d45a5ed:WORK-QUEUE.md` (11119 / 1543289 / `54d66ca6…`) and a fresh `--write` render beside it diffs **0 lines**. That cleared `index-current` but not `append-audit`, which grades the newest queue-touching commit in its own tree and finds `801b37a` still newest: `tools/verify.py --repo .` at `d45a5ed` reads **8 legs, 7 pass, 1 fault**, the fault being `STALE 801b37a … index:no`. The class is `:10886` one day earlier — volt's `3aa745c` ran the renderer without `--write` — so this is the second instance and the first from the control plane; the discipline it asks for had already been written down and was not enough, which is why the record is here rather than in a habit. This commit is the repair shape the ledger states — append **and** re-render in the same commit — and `tools/verify.py --repo .` after it reads 8 legs, 8 pass, 0 fault. No item opened or closed; the open set is unchanged. Appended at the foot; `docs/queue-index.md` re-rendered in the same commit.
+
+**Q65 — CLOSED at `8ec7725` (volt lane, 2026-10-25). Each of the five ungraded rows now carries an rc under a per-file window, `CHECK` resolves its own root, every ledger row is bound to the blob it graded, and a host-pinned PASS is excluded from coverage: 79 rows, PASS 55 / FAIL 24 / TIMEOUT 0, census 93 of 93, lane gate rc 0 in 11.05 s.**
+
+- **The five `TIMEOUT` rows carry an rc.** `q65_row_windows.tsv` names one window per path (all 1,800 s, one reason each), `run_one()` uses it, and a `TIMEOUT` note names the window it got. Measured at `8ec7725`: `forge/verify_doc_census_dry_refactor.py` FAIL rc 1 25.97 s, `forge/verify_selftest_sweep_refactor.py` FAIL rc 1 121.94 s, `sphinx/archive-index-2026-10-23/verify_index.py` FAIL rc 1 191.62 s, `forge/verify_citation_hash_class_portable_default.py` FAIL rc 1 333.13 s, `sphinx/archive-remember-r1-figures-2026-10-23/verify_archive.py` FAIL rc 1 319.30 s. Each is a finding, not bookkeeping: the verifier ran and reported that its own subject does not hold at this tree.
+- **`CHECK` resolves its own root, measured in both directions.** `git -C "$(dirname "$0")" rev-parse --show-toplevel`, rc 2 when there is none: copies of `CHECK` and of `q65_gate.sh` placed outside any repository each exit **rc 2** (measured this tick). In a `--depth 1` clone of `8ec7725` with one verifier deleted **and committed**, `q65_gate.sh` is **rc 1** printing `STALE wizard-work/spark/verify_sum.py`; at `66e5be1` the same shape printed `CHECK PASS`, rc 0 (reply 93 defect 1).
+- **A row is bound to content.** Column 7 is `git rev-parse <rev>:<path>`; `--check` recomputes it at its own rev and a mismatch is a `DRIFT` fault, so an edited verifier cannot keep an rc it no longer earned. Selftest c15-c17 hold present / absent / changed.
+- **Reply 95's done-means: a `gate-run PASS` on a host-pinned verifier is not coverage.** Column 8 parses the committed blob with `ast` and flags a host root in a string constant that is not a docstring. Measured at `8ec7725`: **48 of 55 PASS rows are `PASS*`**, graded-clean **7 of 79**. That row set includes `forge/verify_smell_scan_refactor.py`, the one reply 95 named.
+- **A third instrument defect, found this tick and fixed in the same commit.** At the tool's documented default (`--class undeclared`) `--check` printed `rows at emit : 79  (PASS 1, FAIL 5)` -- a total over the ledger beside a tally over a 6-file population. `tally()` / `fmt_counts()` split the two and the scoped line prints only when the population is narrower; selftest c22 grades the sum, RED on a scratch mutant with the scope guard replaced by `if False:` (**rc 1**, 21/22) and GREEN here (**rc 0**, 22/22). Pre-fix capture, verbatim: `q65-2026-10-25-tally-red.txt`.
+- **Not closed, and named.** The 24 `FAIL` rows are per-lane findings held open in the ledger, exactly as reply 93 recorded. The 48 host-pinned verifiers still read an absolute `/root/...` root; they are Q62's class, one per owning lane. Promoting the lane gate to a `tools/verify.py` leg remains the operator's call (reply 93 §4), not taken here.
+- **Evidence:** commit `8ec7725`; `wizard-work/volt/q65-2026-10-25.md` (§1 the three asks, §2 the identity defect, §4 the final emit, §4.1 the tally defect); `q65-2026-10-25-final.txt` (verbatim reading at 2026-10-25T02:20:22Z); `q65-2026-10-25-{red,green}.txt`; `q65_gate.sh`; `q65_runner.py --selftest` 22 of 22; `q63_verify_scan.py --repo .` → `census coverage : 93 of 93 committed verifier(s) carry a ledger row`, `q63: 0 fault(s)`.
+

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-11121 | 35538 | 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-11132 | 39056 | 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 | 162 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q64 | 10308 | 10308 | 25 | Q45 | BULLET+BOLD | BOLD-LEAD |
-| Q65 | 11055 | 11047 | 11 | Q63 | BULLET+BOLD | BOLD-LEAD |
+| Q65 | 11055 | 11047 | 12 | 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": 11,
+   "refs": 12,
    "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": 1545225,
- "queue_lines": 11121,
- "queue_sha256": "5b7860ce52f73ec7a5f62475557f98806dab17e91be729faf0ebe52e38f17725",
+ "queue_bytes": 1548743,
+ "queue_lines": 11132,
+ "queue_sha256": "91b7c3c3239158acf4c1d14a49233ed9b7612bb5caa04e345188b7db0c5c485e",
  "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": 35538,
-   "end_line": 11121,
+   "bytes": 39056,
+   "end_line": 11132,
    "id": "Q63",
    "line": 10994,
-   "lines": 128,
+   "lines": 139,
    "role": "opening",
    "role_detail": "",
    "status": "open and unclaimed.",