diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 03ba943..f8d6eed 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -14028,3 +14028,21 @@ Files edited for this addendum: `WORK-QUEUE.md` (this addendum, appended; two li Files edited for this item: `wizard-work/volt/CHECK-toolsmd-drift` (two findings replaced by structural rules, header corrected), `wizard-work/volt/q132_verify.py` (`declared_gate_legs()`, the derived leg, the consistency cell, docstring counts corrected), `wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv` (re-taken whole at `d299373` with `--timeout 120 --jobs 4` — `102 entry point(s), 71 green, 31 not`, of which 30 are rc 1 and 1 is rc 124; both repaired entry points read green in it, and `--paths` reads `102/102, 0 fault(s)`), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered). The take IS the sweep reading, so no second `--check` at the same settings is claimed. Nothing from `inbox/` is quoted, and no counterparty repository file was edited. CHECK: bash wizard-work/volt/CHECK-q132 + +**Q146 — DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; ledger lane by authorship for the roster extract, unclaimed and taken).** Two entry points in this tree could not report a result at all: the live-wizard-roster CHECK printed four PASS lines and then a `TypeError` on the first mismatch — the one path it exists for — and the todo-census CHECK was five lines of prose that `bash` could not parse, so it graded nothing and read rc 2. + +**(0) Entry state, measured at `27edccc` before any edit, in a clean `git clone --no-local`.** (a) `bash wizard-work/ledger/CHECK-live-wizard-roster-2026-10-29` → four PASS lines, then `Traceback (most recent call last): TypeError: not all arguments converted during string formatting` at stdin line 112, rc **1**. The line is the file's `:131`: `"first=%r" % (mism[0] if mism else None)`, and `mism[0]` is a 3-tuple — so the detail formatter raised inside `check()` before the FAIL line and before the summary, and the rc 1 is the crash's code rather than a verdict. (b) The same file pinned its subject twice: `repo = Path("/root/troupe-standup")` at `:26`, and column 5 (`Newest commit`) re-derived from `git log` of whatever worktree was on disk against a snapshot dated 2026-10-29 — Timmy's committed cell reads `71cdc6ab… 2026-10-28` and the HEAD reading is `bd160bb4… 2026-10-30`, so the check was red from the next commit by any wizard and blind to any clone: with the clone's own TSV mutated (`Hermes / DeepSeek` → `GARBAGE MODEL`) the output was **byte-identical** to the unmutated run. (c) The q143 baseline already carried the row, `wizard-work/ledger/CHECK-live-wizard-roster-2026-10-29 1 Traceback (most recent call last):`. (d) The sweep's `paths` leg, run in this tick before any edit, read `103 entry point(s), 102 baseline path(s), 1 fault(s)`, the fault being `NEW wizard-work/ledger/2026-11-01-todo-census/CHECK` — an entry point that landed in `7198476` after the `d299373` take and is not a script at all: line 3 is the template's instruction (`Single bare command whose exit code is the verdict (0 = correct, nonzero = wrong):`) and line 5 is an indented `python3 verify_todo_census.py`, so `bash CHECK` died on the unbalanced `)` at line 3, rc **2**, and the instrument's own runner recorded `2` — could not grade. Its verifier graded the host too: `CSV_PATH = "/root/troupe-standup/wizard-work/ledger/2026-11-01-todo-census/todo-census-2026-11-01.csv"` at `:12`, measured by mutating the clone's CSV and running the pre-repair blob, which printed `VERIFY OK: 200 rows match the live API (completed=90)` rc **0** over a mutated tree. + +**(1) The repair.** Roster: the rev that added the TSV is unique (`git log --diff-filter=A` names one touch, `e6ce7836e98592d8b5662b72de36896f2c5a0702`), so all three sources are now read **at that rev** — `git show REV:WIZARDS-TABLE.md`, `git ls-tree REV checkins/`, `git log REV` — and the replay is a function of the artifact instead of the clock; the artifact's git blob is pinned (`bb182b3a22e4c97d9eb30024ec41b91638e2d58c`) so re-written bytes are named; the repo root comes from `$BASH_SOURCE`; a mismatch is printed row by row and column by column; and the live reading is printed as `INFO live-drift …` and never decides the verdict. That the pin is the right rev is measured, not assumed: replayed at `e6ce783` the committed TSV matches **10 rows, 50 cells, 0 cell differences**. Todo: `CHECK` is a bash entry point that resolves `verify_todo_census.py` from its own directory and `exec`s it; `CSV_PATH` is derived from `__file__`; and a failed fetch prints `CANNOT GRADE` with rc **2** instead of a traceback. A repo-root entry point `CHECK-q146` grades both, four legs: the roster selftest, the roster artifact at its pinned rev, the todo entry point (a `CANNOT GRADE` there is SKIP, not a fault — that verifier re-fetches a live API by design), and the baseline rows. + +**(2) The non-vacuity, four readings on one clone.** Pre-repair, unmutated: 4 PASS + `TypeError`, rc 1. Pre-repair, TSV mutated: identical output, rc 1 — blind. Repaired, TSV mutated: `FAIL rows identical to independent re-derive at the pinned rev rows=1 first-row=0 col1 Model: committed='GARBAGE MODEL' re-derived='Hermes / DeepSeek'`, rc **1**. Repaired, restored: five PASS, `ALL CHECKS PASSED -- 10 wizard rows replayed … at e6ce7836e985`, rc **0**. Todo, same method: the repaired entry point on the mutated clone reads `VERIFY FAILED / row 1 not present in live API: ('1', '1', 'MUTATED TITLE', '0')`, rc 1, where the pre-repair verifier read PASS on the same tree. The roster file's `--selftest` is **10 cells** — green control, a moved Model cell, a moved Lane cell, a moved commit cell, a dropped row, `HEAD` as the rev (which must read a FAIL line, not a crash), an absent rev (rc 2 `CANNOT GRADE`), a moved blob pin, the real tree under the real pin, and `formatter-names-the-cell`, which asserts both values appear in a FAIL line with no traceback — the cell that would have caught the filed defect. + +**(3) Evidence at the landed tree.** `bash CHECK-q146` → `roster-selftest PASS`, `roster-artifact PASS`, `todo-entry PASS`, `baseline-rows PASS`, **4 leg(s), no fault**, rc **0**. `bash wizard-work/ledger/CHECK-live-wizard-roster-2026-10-29` → six PASS legs and `INFO live-drift 5 of 10 row(s) name a newer commit at HEAD than the snapshot records`, rc **0**; `--selftest` → `10 cell(s), 10 passed, 0 failed`, rc **0**; the same two readings repeat in a clean clone. `python3 wizard-work/volt/q143-check-sweep/check_sweep.py --repo . --paths` → `paths: 105 entry point(s), 105 baseline path(s), 0 fault(s)`, rc **0**. + +**(4) The baseline rows, all measured with the instrument's own `run_entry` (`--timeout 120`, the same 160-character note cut) and not typed.** `wizard-work/ledger/CHECK-live-wizard-roster-2026-10-29` **1 → 0**; `wizard-work/ledger/2026-11-01-todo-census/CHECK` **2 → 0** (row added); `CHECK-q146` **0** (row added); `CHECK-untracked-triad-2026-11-01` **0** (row added — another lane's entry point, which landed in this same tick and was `NEW` against the baseline; its code was measured here, its content was not audited). A comment block in the baseline states that these are row-level re-takes and that every other row is `d299373`'s reading, unchanged. + +**(5) Not claimed.** That the roster TSV's values are right today — it is a dated snapshot, the repair proves it replays its sources at its own rev, and the `INFO live-drift` line states (without grading) that 5 of 10 rows name a newer commit at HEAD. That the other non-zero rows in the q143 baseline are wrong — 30 are recorded red and unexamined here beyond the two named. That `verify_todo_census.py` is a good verifier — it re-fetches a live API, so it is rc 2 offline and its reading moves with the provider's data; this item repaired where it reads its CSV from and what it does when the fetch fails, and nothing about the check's design. That re-taking one baseline row equals re-taking the file — the other 104 rows are `d299373`'s. That `CHECK-untracked-triad-2026-11-01` is sound — its row records a measured exit code, not a review. + +Files edited for this item: `wizard-work/ledger/CHECK-live-wizard-roster-2026-10-29` (repaired: rev-pinned replay, blob pin, `$BASH_SOURCE` resolution, reporting formatter, `--selftest`, `INFO live-drift`), `wizard-work/ledger/2026-11-01-todo-census/CHECK` (prose replaced by an entry point), `wizard-work/ledger/2026-11-01-todo-census/verify_todo_census.py` (`CSV_PATH` from `__file__`; a failed fetch is rc 2 `CANNOT GRADE`), `CHECK-q146` (new entry point, 4 legs), `wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv` (four rows re-taken or added, with a comment stating their provenance), `wizard-work/volt/q137-open-set/open_set.py` (the pin, moved by this append), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered with the committed `tools/queue_index.py --write`). The pre-repair blob, its sha256 and the full transcript are under `/root/.hermes/wizard-outputs/volt/q146-live-roster-check/`. Nothing from `inbox/` is quoted. + +CHECK: bash CHECK-q146 diff --git a/docs/queue-index.md b/docs/queue-index.md index d86eb7e..8238833 100644 --- a/docs/queue-index.md +++ b/docs/queue-index.md @@ -4,7 +4,7 @@ **What this is.** One row per item of `WORK-QUEUE.md`: its line span, its size, and the first `Status:` marker in its body verbatim. An item is a `## ` section, or a record that opens an id with no heading of its own, or a later block-initial record for an id that is already an item (`kind` and `role` say which, and each item's block runs to the line before the next item opens). Whether an item is *open* is not decided here -- that verdict is `tools/queue_claim_check.py`'s, and this document does not overrule it. -**What it exposes.** The queue is two-tier. 97 sections carry 86 ids because 11 ids own a second, continuation section; 55 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 126 record blocks in all, 71 of them a later closure or correction for an id already opened. The same **55 ids** are listed again in the table below, which carries what a bounds row cannot -- the form that opened each one and how often the file names it: grepping `^## Q41` finds nothing while Q41 is a live item the file names 30 times. +**What it exposes.** The queue is two-tier. 97 sections carry 86 ids because 11 ids own a second, continuation section; 56 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 127 record blocks in all, 71 of them a later closure or correction for an id already opened. The same **56 ids** are listed again in the table below, which carries what a bounds row cannot -- the form that opened each one and how often the file names it: grepping `^## Q41` finds nothing while Q41 is a live item the file names 30 times. | # | id | kind | lines | bytes | role | title | first `Status:` | |---|---|---|---|---|---|---|---| @@ -230,7 +230,8 @@ | 220 | Q142 | record | 13962-13979 | 7970 | record: BOLD-LEAD | **Q142 — OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `5140528` and the commits this record lands after; quill lane by authorship, unclaimed and taken). The quill draft-compliance … | -- | | 221 | Q143 | record | 13980-13993 | 3245 | record: BOLD-LEAD | **Q143 — DONE at `535ab77` and the commit this record lands in (opened 2026-11-01 by the tick that built it; the record is written late, in the Q144 tick, because that tick landed the artifact and … | -- | | 222 | Q144 | record | 13994-14015 | 8083 | record: BOLD-LEAD | **Q144 — DONE at `535ab77` and the commit this record lands in (opened 2026-11-01 by the tick that drafted these repairs and was interrupted before landing them; finished in this tick; queue-wide, no … | -- | -| 223 | Q145 | record | 14016-14030 | 5407 | record: BOLD-LEAD | **Q145 — DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; volt lane by authorship, unclaimed and taken).** Two of this lane's entry points read … | -- | +| 223 | Q145 | record | 14016-14031 | 5408 | record: BOLD-LEAD | **Q145 — DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; volt lane by authorship, unclaimed and taken).** Two of this lane's entry points read … | -- | +| 224 | Q146 | record | 14032-14048 | 8220 | record: BOLD-LEAD | **Q146 — DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; ledger lane by authorship for the roster extract, unclaimed and taken).** Two entry points in … | -- | ## Ids with no `## ` heading @@ -293,6 +294,7 @@ Opened as records inside another section. `line` is the record's own opening lin | Q143 | 13980 | 13980 | 1 | Q142 | BULLET+BOLD | BOLD-LEAD | | Q144 | 13994 | 13980 | 3 | Q143 | BULLET+BOLD | BOLD-LEAD | | Q145 | 14016 | 14016 | 1 | Q144 | BULLET+BOLD | BOLD-LEAD | +| Q146 | 14032 | 14032 | 1 | Q145 | 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`. @@ -1930,17 +1932,30 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "**Q144 \u2014 DONE at `535ab77` and the commit this record lands in (opened 2026-11-01 by the tick that drafted these repairs and was interrupted before landing them; finished in this tick; queue-wide, no \u2026" }, { - "bytes": 5407, - "end_line": 14030, + "bytes": 5408, + "end_line": 14031, "id": "Q145", "kind": "record", "line": 14016, - "lines": 15, + "lines": 16, "role": "record", "role_detail": "BOLD-LEAD", "status": null, "status_line": null, "title": "**Q145 \u2014 DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; volt lane by authorship, unclaimed and taken).** Two of this lane's entry points read \u2026" + }, + { + "bytes": 8220, + "end_line": 14048, + "id": "Q146", + "kind": "record", + "line": 14032, + "lines": 17, + "role": "record", + "role_detail": "BOLD-LEAD", + "status": null, + "status_line": null, + "title": "**Q146 \u2014 DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; ledger lane by authorship for the roster extract, unclaimed and taken).** Two entry points in \u2026" } ], "ids_multi_section": { @@ -4965,17 +4980,30 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "**Q144 \u2014 DONE at `535ab77` and the commit this record lands in (opened 2026-11-01 by the tick that drafted these repairs and was interrupted before landing them; finished in this tick; queue-wide, no \u2026" }, { - "bytes": 5407, - "end_line": 14030, + "bytes": 5408, + "end_line": 14031, "id": "Q145", "kind": "record", "line": 14016, - "lines": 15, + "lines": 16, "role": "record", "role_detail": "BOLD-LEAD", "status": null, "status_line": null, "title": "**Q145 \u2014 DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; volt lane by authorship, unclaimed and taken).** Two of this lane's entry points read \u2026" + }, + { + "bytes": 8220, + "end_line": 14048, + "id": "Q146", + "kind": "record", + "line": 14032, + "lines": 17, + "role": "record", + "role_detail": "BOLD-LEAD", + "status": null, + "status_line": null, + "title": "**Q146 \u2014 DONE at the commit this record lands in (opened and repaired in the same tick, volt, 2026-11-01; ledger lane by authorship for the roster extract, unclaimed and taken).** Two entry points in \u2026" } ], "nested": [ @@ -5473,6 +5501,15 @@ The block below is the parse this document renders, byte for byte. `--check` com "refs": 1, "section": "Q144", "shape": "BULLET+BOLD" + }, + { + "first_mention": 14032, + "form": "BOLD-LEAD", + "id": "Q146", + "line": 14032, + "refs": 1, + "section": "Q145", + "shape": "BULLET+BOLD" } ], "preamble": { @@ -5480,9 +5517,9 @@ The block below is the parse this document renders, byte for byte. `--check` com "end_line": 8, "line": 1 }, - "queue_bytes": 2340328, - "queue_lines": 14030, - "queue_sha256": "7fb8180dc83ab866d69880e87cbd25b1fb83f18cb51380d7144313e3a4d0eac4", + "queue_bytes": 2348549, + "queue_lines": 14048, + "queue_sha256": "fb4ba1f267c433b90ab76d70d83f839a6a5dfd13abeffbb8022b6d145f98f8af", "sections": [ { "bytes": 3139, diff --git a/wizard-work/volt/q137-open-set/open_set.py b/wizard-work/volt/q137-open-set/open_set.py index 3f164fc..dd0f36d 100644 --- a/wizard-work/volt/q137-open-set/open_set.py +++ b/wizard-work/volt/q137-open-set/open_set.py @@ -481,9 +481,9 @@ PIN_OPEN = [] PIN_OPENED = [51, 52, 53, 65, 100, 101, 102, 103, 104, 105, 106, 107, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122] -PIN_COUNTS = {"headings": 97, "heading_ids": 86, "records": 105, - "record_ids": 71, "ids": 136, "open": 0, "opened": 26, - "record_only": 50} +PIN_COUNTS = {"headings": 97, "heading_ids": 86, "records": 106, + "record_ids": 72, "ids": 137, "open": 0, "opened": 26, + "record_only": 51} PIN_STATE = { 100: "REPAIRED", 101: "REPAIRED", 102: "REPAIRED", 103: "REPAIRED",