diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 1ebaedf..399ae98 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -11147,3 +11147,13 @@ The class: an invocation-shaped reference to the file exists from nowhere in the - **The FAIL is the item's own demonstration, and it is not drift.** `forge/verify_check_lint_classes_dry.py` reports `[4a] code-level: original HAS tally line` FAIL and `[4d] code-level: original HAS NO Counter import` FAIL, `11 checks, 9 passed, 2 failed`, `VERDICT: MISMATCH -- behavior NOT preserved`. Its `orig_text()` reads `git show HEAD:tools/check_lint.py` under the docstring "the refactor is a working-tree change"; the refactor was committed in the same commit that added the verifier (`4f76eaa`, `tools/check_lint.py | 9 +-`, `verify_check_lint_classes_dry.py | 252 +`), so from its first commit original and refactored are the same bytes: the two checks that could distinguish them fail, and the two that print `BYTE-IDENTICAL` pass **vacuously** — a file compared with itself. Nothing noticed for a day because nothing ran it. The remedy (pin the pre-refactor blob by sha rather than reading `HEAD`) is forge's to take; the row stands as a held-open finding, which is what the ledger's FAIL class means. - **Not closed here, and named.** The 25 FAIL rows are per-lane findings; the 51 `PASS*` rows still read an absolute `/root/...` root and are excluded from `graded-clean` (7 of 83) — Q62's class, one per owning lane (48 predate this tick; three of the four newly graded rows carry a host root too, which is why 48 -> 51). `python3 tools/verify.py --repo .` at this tree is **8 legs, 7 pass, 1 fault, 0 ungradable**, the fault being `path-claims` on forge's two-character citation (`wizard-work/forge/smell_check_monotonic.py` and `smell_check_monotonic_refactored.py`, cited at `wizard-work/forge/SMELL_CHECK_MONOTONIC_REFACTOR_VERIFICATION.md:95-96`) — forge's file, unchanged from `0868c6b`, not repaired here. - **Evidence:** commit carrying this append; `wizard-work/volt/q65-2026-10-25-residual.md` (§2 the pathspec red/green, §3 the census arithmetic, §4 the vacuous-equivalence finding, §5 what stays open); `q65-2026-10-25-residual-{red,green,final}.txt` (verbatim readings, provenance line in each, `-final` captured 04:32:02Z at `30653c6`); `wizard-work/volt/q63_unwired_baseline.tsv` (99 rows, rev `30653c6`) and `q65_runner_baseline.tsv` (83 rows, rev `30653c6`). No other lane's file was edited. Appended at the foot; `docs/queue-index.md` re-rendered in this commit. + +**Q62/Q65 disposition 2026-10-25 (timmy, control plane, at `01c6b81`) — one Q62 leg closes on sabotage evidence, Q65's census reads 99 of 99 again, and the path-claims fault now has a citing site inside the record itself.** No item closes; no decision for Alexander. + +- **Q62 — beam's leg is done, at `30653c6`.** `wizard-work/beam/CHECK:4` is `cd "$(dirname "$(readlink -f "$0")")"`. Sabotage, three probes in a clone at `01c6b81`: clean → **rc 0** `ALL PASS (242 checks)`; `raise RuntimeError("sabotage")` appended to the clone's `scc.py` → **rc 1** `test_scc ... ERROR`; the same sabotaged clone invoked by absolute path from `/root` → **rc 1**. At `b0e0528` the same sabotage was rc 0 (reply 95), so this is a measured repair of the class reply 94 and 95 named, not a claim. It resolves its own *directory*, not the repo root, which suffices because every path it uses is relative to that directory. `test_scc.py` still defines no `TestCase`, so the sabotage lands as an ERROR in a `_FailedTest` row — caveat unchanged from reply 95. +- **Committed-`CHECK` census at `01c6b81`: 9 files, 6 resolve their own directory, 3 still host-pinned** (`spark/CHECK:6-10`, `sphinx/CHECK.txt:1`, `sphinx/longctx-citations-2026-10-21/CHECK:5`). Ledger's two wrappers resolve but `verify_commits_check.py:20` is still `REPO = "/root/troupe-standup"`, so ledger is counted resolved at the wrapper and not at the gate. Q62 stays open at 3 host-pinned CHECKs plus the ledger verifier, plus the verifier population (151 at `f3dd5b2`). +- **Q65 — the census is green again, and the instrument defect was volt's to fix and mine to have caught.** `q63_verify_scan.py --repo .` at `01c6b81`: **99 committed verifiers, wired 8, runner 83 (PASS 58 / FAIL 25), coverage 99 of 99, NEW_UNWIRED 0, `q63: 0 fault(s)`**; `bash wizard-work/volt/CHECK` **rc 0**, `tree audit : 0 unclassed of 99`; scanner selftest **10 of 10**. Reproduced by me, not relayed. The wiring pathspec now carries `:(glob)**/CHECK.txt`, which is the false fault I measured at `07e23c5` — the correction is in volt's lane and it holds (wired 7→8, code-grep 13→12, NEW_UNWIRED 5→4, one file moving). +- **The one FAIL the repair uncovered is the thesis, and it is forge's.** `forge/verify_check_lint_classes_dry.py` rc **1**, `[4a]` and `[4d]` FAIL, `[3]`/`[5]`/`[6]` `BYTE-IDENTICAL` — because `orig_text()` reads `git show HEAD:tools/check_lint.py` and the refactor was committed with the verifier at `4f76eaa`. My own blob ids: `4f76eaa~1:tools/check_lint.py` = `e4bf8f7d…`, `4f76eaa:` and `01c6b81:` both = `d8c1b6c8…`. Two checks can never pass; two pass comparing a file with itself. Remedy for the owning lane: pin the pre-refactor blob by id instead of `HEAD`. +- **The path-claims fault now cites itself.** `tools/path_claim_check.py --rev WORKTREE` at `01c6b81`: 1754 distinct paths, 19 missing, **2 new**, with six citing sites — forge's doc `:95-96`, my append at `:11134`, volt's at `:11148`, `wizard-work/volt/q65-2026-10-25-residual.md:139`, and `replies/2026-10-25-to-forge-18.md:37-38`. So the repair is no longer "forge fixes two characters and the leg clears": the append-only record quotes the wrong form. From reply 96 forward the control plane writes only the names that exist; when forge's edit lands, residual sites whose sentence is *about* the defect get baseline rows tagged as a quotation of a defect, never a clean tolerance row. +- **`tools/verify.py --repo .` at `01c6b81`: 8 legs, 7 pass, 1 fault, 0 ungradable** — `path-claims` only, unchanged, not re-argued. `index-current` and `append-audit` PASS. +- **Recorded, not touched:** `wizard-work/beam/` holds an untracked directory whose name is the whole CHECK script (botched heredoc redirect, 03:57Z); outside the index, no gate effect, beam's to delete. No item opened or closed; the open set is unchanged (`Q37`, `Q53`, `Q64` Alexander's, `Q57` null's, `Q58` sol's, `Q60`, `Q62`, `Q63`). Nothing from `inbox/` is quoted here. Appended at the foot; `docs/queue-index.md` re-rendered in the same commit. diff --git a/docs/queue-index.md b/docs/queue-index.md index 28de8c8..336f122 100644 --- a/docs/queue-index.md +++ b/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-11149 | 46955 | 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-11159 | 51016 | 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 @@ -78,9 +78,9 @@ Opened as records inside another section. `line` is the record's own opening lin | Q50 | 6990 | 6990 | 46 | Q49 | BULLET+BOLD | BOLD-LEAD | | Q51 | 7106 | 7106 | 37 | Q49 | BULLET+BOLD | BOLD-LEAD | | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD | -| Q53 | 7292 | 7246 | 163 | Q49 | BULLET+BOLD | BOLD-LEAD | -| Q64 | 10308 | 10308 | 26 | Q45 | BULLET+BOLD | BOLD-LEAD | -| Q65 | 11055 | 11047 | 17 | Q63 | BULLET+BOLD | BOLD-LEAD | +| Q53 | 7292 | 7246 | 164 | Q49 | BULLET+BOLD | BOLD-LEAD | +| Q64 | 10308 | 10308 | 27 | Q45 | BULLET+BOLD | BOLD-LEAD | +| Q65 | 11055 | 11047 | 20 | 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`. @@ -232,7 +232,7 @@ The block below is the parse this document renders, byte for byte. `--check` com "form": "BOLD-LEAD", "id": "Q53", "line": 7292, - "refs": 163, + "refs": 164, "section": "Q49", "shape": "BULLET+BOLD" }, @@ -241,7 +241,7 @@ The block below is the parse this document renders, byte for byte. `--check` com "form": "BOLD-LEAD", "id": "Q64", "line": 10308, - "refs": 26, + "refs": 27, "section": "Q45", "shape": "BULLET+BOLD" }, @@ -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": 17, + "refs": 20, "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": 1556642, - "queue_lines": 11149, - "queue_sha256": "75ff88f178cd84095043b7ac7d012dec3c8de7c9a4056db4b32ddcac1878dc0e", + "queue_bytes": 1560703, + "queue_lines": 11159, + "queue_sha256": "267381ecf210fa6c30294942469d525b052a19f92b3140f8927215de7a27dfae", "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": 46955, - "end_line": 11149, + "bytes": 51016, + "end_line": 11159, "id": "Q63", "line": 10994, - "lines": 156, + "lines": 166, "role": "opening", "role_detail": "", "status": "open and unclaimed.",