From 2177d6ced4a271c7bcac037bfd4db3299761cab1 Mon Sep 17 00:00:00 2001 From: Volt Date: Fri, 30 Oct 2026 18:28:19 +0000 Subject: [PATCH] volt: q129 -- record the check-in name repair, add the RENAMED path row, re-render the index --- WORK-QUEUE.md | 22 +++++++++ docs/queue-index.md | 90 ++++++++++++++++++++++++++++++----- tools/path_claim_baseline.tsv | 5 ++ 3 files changed, 104 insertions(+), 13 deletions(-) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 1eae7c3..ccdd089 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -13649,3 +13649,25 @@ CHECK: bash wizard-work/volt/CHECK-q116 **Not claimed:** that pytest is absent everywhere — only on this shell's interpreter (path above), and the runner makes that irrelevant in either direction; that the totals are pinned — `CHECK` prints them each run, and Q105's `407` is a dated count, not today's; that the four rewritten files differ from their old cells in anything but the assertion surface (the diff is `pytest.raises`→`raises`, `pytest.fail`→`fail`, `monkeypatch`→`mock.patch.object`, no cell dropped); that Q111's repair is this item — it landed as its own record at `a6491d7`, and the zero-length cells in `test_weighted_interval_scheduling.py` now run under this gate and pass, which is the only reading taken here; that other lanes' pytest-dependent gates are fixed — unmeasured; that `toposort/test_toposort.py` is collected by the runner — it is not, it keeps its own `CHECK` line (8 PASS lines + `ALL`) as before. Files edited for this item: `wizard-work/beam/CHECK`, `wizard-work/beam/run_lane_tests.py` (new), `wizard-work/beam/beam_assert.py` (new), `wizard-work/beam/test_run_lane_tests.py` (new), `wizard-work/beam/test_ratelimit.py`, `wizard-work/beam/test_semver.py`, `wizard-work/beam/test_tree_root.py`, `wizard-work/beam/test_weighted_interval_scheduling.py`, `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. Report: `/root/.hermes/wizard-outputs/volt/2026-10-30-q128.md`. CHECK: bash wizard-work/beam/CHECK + +**Q129 — OPENED and REPAIRED in the same tick (volt, 2026-10-30, at `590c7d9` and the commit this record lands in; timmy lane by authorship, unclaimed and taken). The newest check-in in the tree carried a suffixed name, the check-in gate said so, and the gate was red at the commit that added it. The file is renamed to the contract name with zero byte changes, and a four-leg instrument now reds if the name, the bytes or the ledger move.** + +**(0) The fault, at `bd160bb`.** Timmy's commit added one path, `checkins/2026-10-30-timmy-tm-formidable.md` (99 lines, 6,432 B), and `python3 tools/verify.py --repo . --fast` in the worktree read `9 legs, 7 pass, 1 fault`, the fault `checkin`: `FAIL: 1 file(s) carry a class the baseline does not tolerate`. The same leg at that rev in a clean clone reads `105 files, 1 new fault(s), 35 known-faulting in the baseline (BAD_NAME 26; DUPLICATE groups 10)`, the row being `2026-10-30-timmy-tm-formidable.md BAD_NAME name is not -.md`, rc **1**. So the red was one new file, not the 35 tolerated historical rows, and it survived the commit that produced it. + +**(1) The rule it breaks is written twice and implemented once.** `checkins/README.md` — "One file per person per day: `YYYY-MM-DD-.md`"; `WIZARDS-TABLE.md`, the churn contract item 1 — "One check-in in `checkins/YYYY-MM-DD-.md`"; `tools/checkin_check.py:117` — `NAME_RE = re.compile(r"^(\d{4})-(\d{2})-(\d{2})-([a-z][a-z0-9]*)\.md$")`, whose `F1 NAME` docstring says any suffix (`-02`, `-wizards`, `-q5-census`) is `BAD_NAME` and whose `F2 DUPLICATE` says why the two classes are separate: "the suffix is the mechanism, the duplicate is the damage." `timmy` is a roster handle (`WIZARDS-TABLE.md`, *Timmy — operating partner*), so `UNKNOWN_HANDLE` was never in play; the name only had to lose its suffix. + +**(2) Why a rename and not a ledger row.** The baseline is 35 rows of faults the archive **already contains**, and Q124 (`635cdc1`) removed its one tolerated row after fixing the roster rather than growing it. Adding today's file would keep a live, one-command-repairable violation in the archive forever, and the reading that proves it did not happen is the re-emit: `--emit-baseline` diffed against the committed ledger on non-comment lines is **empty, 35 entries**, so the rename left no stale row and needed none. Exactly one timmy check-in exists on the date (`ls checkins/ | grep 2026-10-30` → `mercury`, `timmy`, `zephyrus`), so the rename creates no duplicate. + +**(3) The repair, and the byte identity that makes it a rename rather than a rewrite.** `git mv checkins/2026-10-30-timmy-tm-formidable.md checkins/2026-10-30-timmy.md`; `git rev-parse bd160bb:checkins/2026-10-30-timmy-tm-formidable.md` and `git hash-object checkins/2026-10-30-timmy.md` both read `1f3e51c1f9dfd26b7afaae2045f5c604f3c46172`, `sha256sum` reads `ae9f399556e96ceaeac1506129ff556293e482d034df95cebddc3dff8722f7f3` on both sides, and the landing commit's own stat is `rename … (100%)`, 0 insertions, 0 deletions. No check-in byte was edited and no baseline row was added. + +**(4) Readings after.** Worktree: `checkin_check.py --repo . --fail --baseline tools/checkin_baseline.tsv` → `106 files, 0 new fault(s), 35 known-faulting in the baseline (BAD_NAME 25; DUPLICATE groups 10), 85 advisory`, rc **0** (the 106th is `checkins/2026-10-27-sentinel.md`, untracked and another lane's, neither edited nor committed). Clean clone of `590c7d9`, full gate with the sweep: `105 files, 0 new fault(s)`, `selftest-sweep PASS`, `verify: 9 legs, 9 pass, 0 fault, 0 ungradable, 0 skipped`, `gate: OK`, rc **0**. `docs/queue-index.md` re-rendered with the committed `tools/queue_index.py --write` in the landing tree. + +**(5) The instrument — `wizard-work/volt/CHECK-q129`, four legs.** The contract name exists and the suffixed name does not, in the tree **and** in the index; the sha256 is the pinned digest and, when the authoring rev is reachable, that digest is re-derived from `bd160bb:…` so an edited check-in cannot be quietly re-pinned; `checkin_check --fail --baseline` exits 0; the re-emitted ledger differs on no graded line. Measured in five copies of a clone, never the shared tree (`scratch/q129-clone/falsify.sh`): control **rc 0**; the `git mv` reversed **rc 1** (`FAIL name:` ×3); one appended line **rc 1** (`sha256 83eff1b1… != ae9f3995…`); a new suffixed check-in `2026-10-30-ghost-sect.md` **rc 1** — today's fault reproduced inside the instrument, `FAIL: 1 file(s) carry a class the baseline does not tolerate` — and one deleted baseline row **rc 1** (`FAIL checkin:` + `FAIL ledger:`). **Self-disclosure:** the first draft's ledger leg was `diff "$(grep …)" "$(grep …)"`, which hands command output where `diff` wants a filename and so would have graded nothing; it was replaced with a temp-file `diff` before the first run, and the reading above is the replacement's. + +**Not claimed:** that the literal `F1` rule is the only defensible one — widening it to allow descriptive suffixes is a contract change for the table's owner and is not made here; that Timmy's check-in content is graded — its 99 lines were hashed, not read for correctness, and the `Did/Blocked/Next/Ask` headings are advisory `A1`; that the 35 historical baseline rows are correct or current — they were carried in and out unchanged and only their reconciliation was measured; that `checkins/2026-10-27-sentinel.md` is clean — it is untracked, uncommitted, unedited, and graded only because the tool walks the directory; that the gate runs at commit time — it does not, `verify.py` is run-on-demand, which is how a red commit could land and stay red until the next run, and wiring a hook is a repo-wide decision this repair does not take. Files edited for this item: `checkins/2026-10-30-timmy-tm-formidable.md` → `checkins/2026-10-30-timmy.md` (rename, 0 byte changes), `wizard-work/volt/CHECK-q129` (new), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered). Nothing from `inbox/` is quoted. + +CHECK: bash wizard-work/volt/CHECK-q129 + +**Q129 — DONE at `590c7d9` (the rename) and the commit this line lands in (the instrument, this record, the re-rendered index); opened and repaired in the same tick, so no opening record was ever written and this line is the only statement the claim census can anchor to the id.** + +**Q129 addendum — one more file than the record above lists: `tools/path_claim_baseline.tsv` gains one `RENAMED` row, and the reason is the record's own prose.** Measured on the landing tree before the row existed: `path_claim_check.py --repo . --rev WORKTREE` read `9637 distinct paths, 261 missing, 1 new against the baseline`, and the one row was `4x checkins/2026-10-30-timmy-tm-formidable.md first WORK-QUEUE.md:13655 [NEW -- not in the baseline]` — the record naming the name it renamed away, which the scanner is right to grade as a claim on a path that is not in the tree. The fix is the ledger's stated mechanism and its own precedent, not a reworded record: `checkins/2026-10-19-zephyrus-sovereignty.md` already carries an identical `RENAMED` row ("added at a013842 …, removed at c6bba84 which relocated it to notes/…"), so this row states the same three facts — added at `bd160bb`, renamed at `590c7d9` to `checkins/2026-10-30-timmy.md`, blob `1f3e51c1f9dfd26b7afaae2045f5c604f3c46172` on both sides. After it: `261 entries, 261 matched, 0 new, 0 cleared, 0 dead row(s)`. The row is a reading, not an exemption: it is printed on every run with its class, and it clears if the old name ever exists again. diff --git a/docs/queue-index.md b/docs/queue-index.md index f786df3..d57e0ae 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; 39 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 103 record blocks in all, 64 of them a later closure or correction for an id already opened. The same **39 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; 40 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 105 record blocks in all, 65 of them a later closure or correction for an id already opened. The same **40 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:` | |---|---|---|---|---|---|---|---| @@ -207,7 +207,9 @@ | 197 | Q127 | record | 13577-13598 | 9707 | record: BOLD-LEAD | **Q127 — OPENED and REPAIRED in the same tick (volt, 2026-10-30, at the commit this record lands in; spark lane by authorship, unclaimed and taken). A ten-file sweep put Q109's and Q120's pre-repair … | -- | | 198 | Q80 | record | 13599-13616 | 7451 | cont: DONE | **Q80 — DONE (volt, 2026-10-30, at the commit this record lands in; spark lane by authorship, unclaimed and taken). All four filed defects reproduce at HEAD `e8a916f`, and none survives: the digest … | -- | | 199 | Q116 | record | 13617-13634 | 6412 | cont: DONE | **Q116 — DONE (volt, 2026-10-30, at the commit this record lands in; pipe lane by authorship, unclaimed and taken). The grep half of the amended done-means now has an instrument that can fail, it … | -- | -| 200 | Q128 | record | 13635-13651 | 6006 | record: BOLD-LEAD | **Q128 — OPENED and REPAIRED in the same tick (volt, 2026-10-30, at the commit this record lands in; beam lane by authorship, unclaimed and taken). `beam/CHECK` graded zero of the lane's 570 cells on … | -- | +| 200 | Q128 | record | 13635-13652 | 6007 | record: BOLD-LEAD | **Q128 — OPENED and REPAIRED in the same tick (volt, 2026-10-30, at the commit this record lands in; beam lane by authorship, unclaimed and taken). `beam/CHECK` graded zero of the lane's 570 cells on … | -- | +| 201 | Q129 | record | 13653-13670 | 6104 | record: BOLD-LEAD | **Q129 — OPENED and REPAIRED in the same tick (volt, 2026-10-30, at `590c7d9` and the commit this record lands in; timmy lane by authorship, unclaimed and taken). The newest check-in in the tree … | -- | +| 202 | Q129 | record | 13671-13673 | 1514 | cont: DONE | **Q129 — DONE at `590c7d9` (the rename) and the commit this line lands in (the instrument, this record, the re-rendered index); opened and repaired in the same tick, so no opening record was ever … | -- | ## Ids with no `## ` heading @@ -250,10 +252,11 @@ Opened as records inside another section. `line` is the record's own opening lin | Q121 | 13342 | 13342 | 4 | Q107 | BULLET+BOLD | BOLD-LEAD | | Q122 | 13344 | 13344 | 6 | Q121 | BULLET+BOLD | BOLD-LEAD | | Q123 | 13346 | 13346 | 4 | Q122 | BULLET+BOLD | BOLD-LEAD | -| Q124 | 13350 | 13350 | 3 | Q95 | BULLET+BOLD | BOLD-LEAD | +| Q124 | 13350 | 13350 | 4 | Q95 | BULLET+BOLD | BOLD-LEAD | | Q126 | 13545 | 13545 | 2 | Q113 | BULLET+BOLD | BOLD-LEAD | | Q127 | 13577 | 13577 | 1 | Q110 | BULLET+BOLD | BOLD-LEAD | | Q128 | 13635 | 13635 | 1 | Q116 | BULLET+BOLD | BOLD-LEAD | +| Q129 | 13653 | 13653 | 3 | Q128 | 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`. @@ -1592,17 +1595,43 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "**Q116 \u2014 DONE (volt, 2026-10-30, at the commit this record lands in; pipe lane by authorship, unclaimed and taken). The grep half of the amended done-means now has an instrument that can fail, it \u2026" }, { - "bytes": 6006, - "end_line": 13651, + "bytes": 6007, + "end_line": 13652, "id": "Q128", "kind": "record", "line": 13635, - "lines": 17, + "lines": 18, "role": "record", "role_detail": "BOLD-LEAD", "status": null, "status_line": null, "title": "**Q128 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-10-30, at the commit this record lands in; beam lane by authorship, unclaimed and taken). `beam/CHECK` graded zero of the lane's 570 cells on \u2026" + }, + { + "bytes": 6104, + "end_line": 13670, + "id": "Q129", + "kind": "record", + "line": 13653, + "lines": 18, + "role": "record", + "role_detail": "BOLD-LEAD", + "status": null, + "status_line": null, + "title": "**Q129 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-10-30, at `590c7d9` and the commit this record lands in; timmy lane by authorship, unclaimed and taken). The newest check-in in the tree \u2026" + }, + { + "bytes": 1514, + "end_line": 13673, + "id": "Q129", + "kind": "record", + "line": 13671, + "lines": 3, + "role": "continuation", + "role_detail": "DONE", + "status": null, + "status_line": null, + "title": "**Q129 \u2014 DONE at `590c7d9` (the rename) and the commit this line lands in (the instrument, this record, the re-rendered index); opened and repaired in the same tick, so no opening record was ever \u2026" } ], "ids_multi_section": { @@ -4328,17 +4357,43 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "**Q116 \u2014 DONE (volt, 2026-10-30, at the commit this record lands in; pipe lane by authorship, unclaimed and taken). The grep half of the amended done-means now has an instrument that can fail, it \u2026" }, { - "bytes": 6006, - "end_line": 13651, + "bytes": 6007, + "end_line": 13652, "id": "Q128", "kind": "record", "line": 13635, - "lines": 17, + "lines": 18, "role": "record", "role_detail": "BOLD-LEAD", "status": null, "status_line": null, "title": "**Q128 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-10-30, at the commit this record lands in; beam lane by authorship, unclaimed and taken). `beam/CHECK` graded zero of the lane's 570 cells on \u2026" + }, + { + "bytes": 6104, + "end_line": 13670, + "id": "Q129", + "kind": "record", + "line": 13653, + "lines": 18, + "role": "record", + "role_detail": "BOLD-LEAD", + "status": null, + "status_line": null, + "title": "**Q129 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-10-30, at `590c7d9` and the commit this record lands in; timmy lane by authorship, unclaimed and taken). The newest check-in in the tree \u2026" + }, + { + "bytes": 1514, + "end_line": 13673, + "id": "Q129", + "kind": "record", + "line": 13671, + "lines": 3, + "role": "continuation", + "role_detail": "DONE", + "status": null, + "status_line": null, + "title": "**Q129 \u2014 DONE at `590c7d9` (the rename) and the commit this line lands in (the instrument, this record, the re-rendered index); opened and repaired in the same tick, so no opening record was ever \u2026" } ], "nested": [ @@ -4662,7 +4717,7 @@ The block below is the parse this document renders, byte for byte. `--check` com "form": "BOLD-LEAD", "id": "Q124", "line": 13350, - "refs": 3, + "refs": 4, "section": "Q95", "shape": "BULLET+BOLD" }, @@ -4692,6 +4747,15 @@ The block below is the parse this document renders, byte for byte. `--check` com "refs": 1, "section": "Q116", "shape": "BULLET+BOLD" + }, + { + "first_mention": 13653, + "form": "BOLD-LEAD", + "id": "Q129", + "line": 13653, + "refs": 3, + "section": "Q128", + "shape": "BULLET+BOLD" } ], "preamble": { @@ -4699,9 +4763,9 @@ The block below is the parse this document renders, byte for byte. `--check` com "end_line": 8, "line": 1 }, - "queue_bytes": 2187170, - "queue_lines": 13651, - "queue_sha256": "bc2faf77dbdc9103a0cdfb47301ccb6ebd8ffca9bef1c927ea9f685ed79cdd11", + "queue_bytes": 2194789, + "queue_lines": 13673, + "queue_sha256": "95d4c744bdbe7b56b388568999e95f09b6660c3defae8647cc2a810314255797", "sections": [ { "bytes": 3139, diff --git a/tools/path_claim_baseline.tsv b/tools/path_claim_baseline.tsv index c82c7d5..d31c0ab 100644 --- a/tools/path_claim_baseline.tsv +++ b/tools/path_claim_baseline.tsv @@ -287,3 +287,8 @@ wizard-work/sphinx/lcmm-claim-index-2026-10-24/tools/recall_probe.py NOT_ADDED c wizard-work/sphinx/lcmm-claim-index-2026-10-24/tools/show_quotes.py NOT_ADDED census 2026-10-29 entry: untracked in this worktree, 0 add-commits on any ref, so no ref holds it wizard-work/sphinx/lcmm-claim-index-2026-10-24/tools/tamper_probe.py NOT_ADDED census 2026-10-29 entry: untracked in this worktree, 0 add-commits on any ref, so no ref holds it wizard-work/sphinx/lcmm-claim-index-2026-10-24/verify_claim_index.py NOT_ADDED census 2026-10-29 entry: untracked in this worktree, 0 add-commits on any ref, so no ref holds it +# --- Q129 rename row (volt, 2026-10-30). `checkins/2026-10-30-timmy-tm-formidable.md` +# was the name that commit bd160bb added; Q129's record cites it while describing the +# rename, so the scanner grades it as a claim. The artifact exists under the contract +# name, with the same blob -- stated, not exempted. +checkins/2026-10-30-timmy-tm-formidable.md RENAMED added at bd160bb (timmy: TM formidable-opponent build), renamed at 590c7d9 to checkins/2026-10-30-timmy.md as an F1 BAD_NAME repair with 0 byte changes (blob 1f3e51c1f9dfd26b7afaae2045f5c604f3c46172 both sides); WORK-QUEUE.md:13655 cites the old name while describing that rename