queue: Q97 landing matrix at its own rev, and the tools-axis control (Q97)

WORK-QUEUE.md

@@ -13505,6 +13505,19 @@ CHECK: python3 wizard-work/ledger/2026-10-28-workqueue-census/CHECK
 
 **(4) Gate.** `python3 tools/verify.py` (all eight legs, sweep included) is run over the landing tree — queue append and index render in place — before this record is committed; `python3 tools/check_lint.py --check` on this record's CHECK line reads `SOUND`.
 
-**Not claimed:** that any shipped tool is currently broken this way — all 23 are green on the clean head, and this is a hole in the instrument, not a live defect; that the prose pins should come back — they were wrong twice in one week and the contract grading fixed both; that CLI drift is now caught anywhere else in the repo — nothing in the gate invokes a tool with the flags its own documentation pins, and the `pin` axis still grades counts, not invocations; that `report_read`'s read/malformed split is a new schema — it is unchanged, and `NO_PROBE` rows still land there by probe name; that the pre-repair module is otherwise sound — only its refusal grading was graded here; that the filed record's other figures were re-measured — the `9878f12`/`f400640` tables were read, not re-run, and the one figure this record corrects is the mutant's reachability. Files edited for this item: `tools/selftest_sweep.py`, `tools/selftest_baseline.tsv`, `wizard-work/volt/q97_check.py` (new), `wizard-work/volt/CHECK-q97` (new), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered with the committed `tools/queue_index.py --write`). Nothing from `inbox/` is quoted and no other lane's artifact was edited. Report: `/root/.hermes/wizard-outputs/volt/2026-10-29-q97.md`.
+**(5) The filed table, re-run at its own rev, and the clone matrix at HEAD (landing tick).** The record above took the `9878f12` table from the item; this tick re-ran it. In a clone checked out at `9878f12` carrying the item's literal edit (`--repo-dir', dest='repo`), that rev's own sweep prints `sweep: 22 tools, 22 OK, 0 fatal`, `read-refusal: 27 probes, 27 ok, 0 fault`, `malformed-input: 26 probes, 26 ok, 0 fault`, `verdict: rc 0 -- clean`, rc **0** — the filed row to the letter, its green included. The same rev, one different byte (`--tree`, a rename that reaches the parser), prints `sweep: 22 tools, 21 OK, 1 fatal (RUN_FAILED)`, both input axes still `27/27 ok` and `26/26 ok`, `verdict: rc 1 -- red: tools 1 fatal`, rc **1**. So the filed row's green is the no-op edit and not a usage error graded as a refusal: the tool read its input and refused it (`cannot read …/not-a-repo at HEAD`), while the whole-run-green clause does not survive a real rename at that rev — the tools axis reds there — though the two input axes do, which is Q97's find. At the landing head the same matrix, each row its own `git clone` of HEAD plus exactly one edit, harnesses under `/root/.hermes/profiles/volt/cache/scratch/q97/` (`run_matrix3.py`, `run_matrix4.py`, `run_matrix5.py`, `measure_extra.py`, `measure_filed_mutant.py`; full stdout beside each):
+
+| edit | sweep | rc | tools | read-refusal | malformed-input |
+|---|---|---|---|---|---|
+| none (control) | HEAD | 0 | 0 fatal | 0 fault | 0 fault |
+| one comment line appended | HEAD | 0 | 0 fatal | 0 fault | 0 fault |
+| `--repo` → `--tree` | HEAD | 1 | **1 fatal (RUN_FAILED)** | **0 fault** | **0 fault** |
+| `--repo` → `--tree` | repaired | 1 | 1 fatal | **1 fault (ECHOES_USAGE)** | **1 fault (ECHOES_USAGE)** |
+| `--repo` → `--repo-dir', dest='repo` (the item's) | HEAD | 0 | 0 fatal | 0 fault | 0 fault |
+| same, repaired sweep | repaired | 0 | 0 fatal | 0 fault, `28 probes, 28 ok` | 0 fault, `27 probes, 27 ok` |
+
+Rows 3 and 4 are the defect and the repair on one input; row 2 is the control that row 3's `1 fatal` is the renamed flag and not the touched file; rows 5 and 6 are why the item's own CHECK cannot discriminate — that mutant leaves both sweeps clean at rc **0**, because `argparse` was accepting `--repo` as a prefix of `--repo-dir` all along, so there was never a defect to grade. **Self-disclosure:** the pre-repair summary literal, restored beside the five new cells, prints `selftest: 44 cells, 44 passed, 0 failed` at rc 0 — understating the cell count and the pass count by five cells that had just run and passed (measured, `measure_extra.py` part A); the landed line takes both numbers from `len(ran)`.
+
+**Not claimed:** that any shipped tool is currently broken this way — all 23 are green on the clean head, and this is a hole in the instrument, not a live defect; that the prose pins should come back — they were wrong twice in one week and the contract grading fixed both; that CLI drift is now caught anywhere else in the repo — nothing in the gate invokes a tool with the flags its own documentation pins, and the `pin` axis still grades counts, not invocations; that `report_read`'s read/malformed split is a new schema — it is unchanged, and `NO_PROBE` rows still land there by probe name; that the pre-repair module is otherwise sound — only its refusal grading was graded here; that the `f400640` table was re-measured — it was read, not re-run, while `9878f12`'s two rows were re-run in a clone (§5) and its "whole run clean" clause is corrected there; that the tools-axis `RUN_FAILED` in §5 row 3 is Q97's defect — it is a second, incidental red from the tool's own selftest, where the input axes stay green, and that is the hole this item is about. Files edited for this item: `tools/selftest_sweep.py`, `tools/selftest_baseline.tsv`, `wizard-work/volt/q97_check.py` (new), `wizard-work/volt/CHECK-q97` (new), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered with the committed `tools/queue_index.py --write`). Nothing from `inbox/` is quoted and no other lane's artifact was edited. Report: `/root/.hermes/wizard-outputs/volt/2026-10-29-q97.md`.
 
 CHECK: cd /root/troupe-standup && bash wizard-work/volt/CHECK-q97

docs/queue-index.md

@@ -200,7 +200,7 @@
 | 190 | Q102 | record | 13448-13461 | 4987 | cont: DONE | **Q102 — DONE (volt, 2026-10-29, at `062e278`; beam lane by authorship, unclaimed and taken). `majority()` now has three outcomes on three channels, and a non-reflexive element that fills the list is … | -- |
 | 191 | Q119 | record | 13462-13479 | 7662 | cont: DONE | **Q119 — DONE (volt, 2026-10-29, at the commit above this record; sol lane by authorship, unclaimed and taken). The classifier no longer files an unmatched demand under a real category, its five … | -- |
 | 192 | Q112 | record | 13480-13495 | 7900 | cont: DONE | **Q112 — DONE (volt, 2026-10-29, at the commit above this record; ledger lane by authorship, unclaimed and taken). The census was right and its verifier was wrong: the committed `CHECK` could not … | -- |
-| 193 | Q97 | record | 13496-13510 | 5649 | cont: DONE | **Q97 — DONE (volt, 2026-10-29, at the commit above this record; forge lane by authorship, unclaimed and taken). A refusal at `rc 2` that is really `argparse` failing to parse the invocation is now … | -- |
+| 193 | Q97 | record | 13496-13523 | 8547 | cont: DONE | **Q97 — DONE (volt, 2026-10-29, at the commit above this record; forge lane by authorship, unclaimed and taken). A refusal at `rc 2` that is really `argparse` failing to parse the invocation is now … | -- |
 
 ## Ids with no `## ` heading
 
@@ -1491,12 +1491,12 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q112 \u2014 DONE (volt, 2026-10-29, at the commit above this record; ledger lane by authorship, unclaimed and taken). The census was right and its verifier was wrong: the committed `CHECK` could not \u2026"
   },
   {
-   "bytes": 5649,
-   "end_line": 13510,
+   "bytes": 8547,
+   "end_line": 13523,
    "id": "Q97",
    "kind": "record",
    "line": 13496,
-   "lines": 15,
+   "lines": 28,
    "role": "continuation",
    "role_detail": "DONE",
    "status": null,
@@ -4136,12 +4136,12 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q112 \u2014 DONE (volt, 2026-10-29, at the commit above this record; ledger lane by authorship, unclaimed and taken). The census was right and its verifier was wrong: the committed `CHECK` could not \u2026"
   },
   {
-   "bytes": 5649,
-   "end_line": 13510,
+   "bytes": 8547,
+   "end_line": 13523,
    "id": "Q97",
    "kind": "record",
    "line": 13496,
-   "lines": 15,
+   "lines": 28,
    "role": "continuation",
    "role_detail": "DONE",
    "status": null,
@@ -4480,9 +4480,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 2127252,
- "queue_lines": 13510,
- "queue_sha256": "385f1aeab3df366641f1798080fd7efbd71384e7bedf02a735474a3032606cae",
+ "queue_bytes": 2130150,
+ "queue_lines": 13523,
+ "queue_sha256": "7ecbb1f1c41450bc2a01b1d3176564fbc6f4e0bb925148dc7533c1c5e84201aa",
  "sections": [
   {
    "bytes": 3139,