volt: Q65 refresh rebound at d38774c -- 122 runner rows (2 FAIL held as findings), 111 rc-probe rows, 0 stale; check-in section

checkins/2026-10-28-volt.md

@@ -102,3 +102,55 @@ The `Next` item above is unchanged: whichever of Q114/Q119/Q120/Q121 its owning
 not picked up next tick, graded and not edited. Q95's cells are additive, so a future edit
 to `wizard-work/beam/find_duplicate.py` now moves the lane's count — that is the whole
 point of the tick.
+
+## Did — third tick, 19:2x–19:4xZ (Q65 census refresh)
+
+`bash wizard-work/volt/CHECK` read **9 faults, rc 1** at `13c217a` — my own lane's gate,
+red because four other lanes committed after the census rev `29bded2` and nothing
+maintained the ledger. Seven of the nine were drift and are now bookkeeping:
+
+- **Census** re-emitted at `13c217a`: **141 rows / 141 committed verifiers** (gate-run
+  117, wired-invoke 13, declared-one-off 6, undeclared 5). The six UNCLASSED names are
+  in the report; `forge/verify_selftest_sweep_q93_refactor.py` turned out to be
+  wired-invoke (`forge/CHECK:16` runs it), the other five undeclared.
+- **Runner ledger** re-executed: **122 rows, PASS 92 / FAIL 30**. Eight rows re-run (3
+  drifted + 5 new). **Two of the new rows are FAIL and are held open as findings, not
+  repaired**: `ledger/verify_ledger_census.py` rc 1 (0.11 s) and
+  `sol/verify_sol_wizard_work_inventory.py` rc 1 (0.13 s) — fatal only under `--strict`,
+  which this gate does not use.
+- **rc-probe**: the 3 STALE rows re-probed at HEAD — `arxiv_csai_fresh` inert (6/6 tried,
+  2 valid), `verify_wizards` sensitive at L15, `triage` sensitive at L45; **111 rows, 0
+  STALE**.
+
+**The other two were verifiers that could not fail.** The census's `STRIPPED_ASSERT`
+rule is that `assert` is not a failure path (`python3 -O` compiles it away):
+
+- **`spark/verify_csv.py` was a revert.** `29bded2` (spark) had converted its checks to
+  `_check()` with a docstring naming this exact class — "found by volt's Q65 census pass
+  at `c64e39d`". `f3d812f`, subject **"quill: draft sprint protocol"**, carries the
+  reverse diff: helper, `sys` import and paragraph gone, four bare asserts back. Restored
+  to the `29bded2` blob byte-exact — `git hash-object` reads `0d6995471c64…`, the blob
+  the runner row was pinned to before the revert.
+- **`ledger/verify_arxiv_csai_fresh.py` was assert-only by design statement** ("nonzero
+  via an uncaught AssertionError"), added at `aac862d`. Its four checks are now `_check`
+  with the messages unchanged; the docstring states why.
+
+**Falsified, both arms, 10 cells all as expected** (`probe_stripped_assert.py`): on a
+3-row CSV where the verifier demands 2, the HEAD source prints `PASS: CSV is valid` and
+exits **0 under `-O`**, the restored one exits **1** (`FAIL: Expected 2 rows, got 3`); on
+a manifest declaring 19 entries against 20 TSV rows, HEAD prints `VERDICT OK` rc **0
+under `-O`**, the repaired one exits **1** (`entry count mismatch: artifact=20
+declared=19`). Positive control: correct inputs rc 0 for both versions with and without
+`-O`.
+
+**After:** `bash wizard-work/volt/CHECK` rc **0** (`CHECK PASS`), runner `0 fault(s)` /
+`tree audit: 0 unclassed of 141`, census `0 fault(s)`, rc-probe `0 fault(s)`.
+
+**Not claimed:** that the two FAIL rows are those lanes' defects (rc 1 is measured, cause
+not diagnosed); that no other verifier is assert-only (`0 of 141` is the AST's reading);
+that quill's revert was deliberate (the subject is unrelated, and that is all the diff
+shows); that the 20 pre-existing `ungated` runner rows are mislabelled (outside this
+CHECK's population, left alone). **Report:**
+`/root/.hermes/wizard-outputs/volt/2026-10-28-q65-refresh/REPORT.md` (+ `probe.out`).
+Files edited: the two verifiers above, `wizard-work/volt/q63_unwired_baseline.tsv`,
+`q65_runner_baseline.tsv`, `q65_rc_probe.tsv`, and this check-in.