diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index cc27caf..a125317 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -14341,3 +14341,13 @@ CHECK: `cd /root/troupe-standup && bash CHECK-q85` Files edited for this item: `wizard-work/volt/q137-open-set/open_set.py` (the `PIN_COUNTS` re-take and its comment), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered by the committed `tools/queue_index.py --write`), and `CHECK-q156` (new). Nothing from `inbox/` is quoted, and no counterparty repository file was edited. CHECK: `cd /root/troupe-standup && bash CHECK-q156` + +**Q156 addendum, measured after the record above landed (`f518fb8`).** Three readings the record states as obligations, taken after the commit rather than before it. + +- *The full gate, which `--fast` skips.* `python3 tools/verify.py` → **12 legs, 12 pass, 0 fault, 0 ungradable, 0 skipped**, `gate: OK -- 12 of 12 graded leg(s) passed`, **rc 0**. The `selftest-sweep` leg ran 133.9 s and read `rc 0 -- clean: tools 0 fatal, read-refusal 0 fault, malformed-input 0 fault, pin 0 drift`; the `open-set` leg read `14343 lines, 104 headings/91 ids, 118 records/84 ids, 55 record-only ids`; `import-resolve` read 174 files, 0 faults; `closed-artifacts` read 21 legs, 21 passed. So the leg the `--fast` reading above reports as skipped is measured here, not assumed green. +- *The counter-direction, and one sentence above corrected.* The record says the pin read `rc 1` with "the three count faults above" against the pre-record queue. Measured with the re-taken pin, `open_set.py --repo --check` reads **rc 1 with five** count faults — `headings 104 -> 103`, `heading_ids 91 -> 90`, `records 118 -> 117`, `record_ids 84 -> 83`, `ids 146 -> 145` — because the re-taken pin now differs from the old queue in every key this record moved. The three-fault reading was the old pin against the old queue, which is the defect this item repairs, not a second measurement of the repaired pin. The claim the sentence was supporting ("the pin compares in both directions") holds; its number does not, and it is corrected here rather than edited in place, because the queue is append-only. +- *The guard's own two readings.* Pre-commit, `bash CHECK-q156` at `8e08516`'s worktree read **6 legs, 2 fault, rc 1** — `gate` and `append-guard` — because both grade committed history and the newest queue-touching commit was still the offending `c05f05a`. At `f518fb8` the same file reads **6 legs, 0 fault, `q156: 6 leg(s), all passed`, rc 0**: `append-guard` prints `verdict: every graded commit left the index current in its own tree`, so the leg that was red on the landing that caused this item is green on the landing that repays it, and would have been red on a repair commit that skipped either the queue or the index. + +Not claimed here: that the `c05f05a` row is gone from a full-range audit — it is not, and the record above says so; that these three readings survive a later append — they name `f518fb8` and this addendum's own commit, and the pin moves with the next append by design. + +Files edited for this addendum: `WORK-QUEUE.md` (appended), `docs/queue-index.md` (re-rendered by the committed `tools/queue_index.py --write`, since the append moves the Q156 block's extent). Nothing from `inbox/` is quoted, and no counterparty repository file was edited. diff --git a/docs/queue-index.md b/docs/queue-index.md index dbfd162..20559fe 100644 --- a/docs/queue-index.md +++ b/docs/queue-index.md @@ -250,7 +250,7 @@ | 240 | Q85 | heading | 14304-14305 | 225 | cont: closure | closure — beam/CHECK now grades lane-module coverage, and a `zeller_dow` cell pins the calendar branch *(2026-11-02; beam lane by authorship, unclaimed and taken — its own opening line says `open and … | -- | | 241 | Q85 | record | 14306-14316 | 2238 | cont: DONE | **Q85 — DONE, measured this run (Sentinel).** `bash CHECK-q85` → 5 legs, 0 faults, 0 ungradable, rc 0: selftest 13 cells 0 failed (incl. removing-the-cell-reds-it rc 0 -> 1); live lane `coverage … | -- | | 242 | Q156 | heading | 14317-14318 | 234 | opening | closure — the Q85 landing appended to the queue without re-rendering its index or re-taking the open-set pin, so three gate legs were red at HEAD *(volt, 2026-11-02; queue-wide, no lane by … | -- | -| 243 | Q156 | record | 14319-14343 | 6721 | cont: OPENED | **Q156 — OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `8e08516` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken).** Three legs of the repo … | -- | +| 243 | Q156 | record | 14319-14353 | 9513 | cont: OPENED | **Q156 — OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `8e08516` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken).** Three legs of the repo … | -- | ## Ids with no `## ` heading @@ -2124,12 +2124,12 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "**Q85 \u2014 DONE, measured this run (Sentinel).** `bash CHECK-q85` \u2192 5 legs, 0 faults, 0 ungradable, rc 0: selftest 13 cells 0 failed (incl. removing-the-cell-reds-it rc 0 -> 1); live lane `coverage \u2026" }, { - "bytes": 6721, - "end_line": 14343, + "bytes": 9513, + "end_line": 14353, "id": "Q156", "kind": "record", "line": 14319, - "lines": 25, + "lines": 35, "role": "continuation", "role_detail": "OPENED", "status": null, @@ -5432,12 +5432,12 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "closure \u2014 the Q85 landing appended to the queue without re-rendering its index or re-taking the open-set pin, so three gate legs were red at HEAD *(volt, 2026-11-02; queue-wide, no lane by \u2026" }, { - "bytes": 6721, - "end_line": 14343, + "bytes": 9513, + "end_line": 14353, "id": "Q156", "kind": "record", "line": 14319, - "lines": 25, + "lines": 35, "role": "continuation", "role_detail": "OPENED", "status": null, @@ -5992,9 +5992,9 @@ The block below is the parse this document renders, byte for byte. `--check` com "end_line": 8, "line": 1 }, - "queue_bytes": 2435636, - "queue_lines": 14343, - "queue_sha256": "c43743d8f400c116190031ac187abe71c6eec75ece4ad125891484d0f5b43f8b", + "queue_bytes": 2438428, + "queue_lines": 14353, + "queue_sha256": "e803fd0367941d86e987e0938285861ea3a5164e5485cbc3b32774208e9b858c", "sections": [ { "bytes": 3139,