volt: Q141 addendum -- landing readings, clone parity, gate 12/12

WORK-QUEUE.md

@@ -13954,3 +13954,7 @@ CHECK: bash wizard-work/volt/q140/CHECK-q140
 Files edited for this item: `wizard-work/ledger/verify_ledger_dir_census.py` (rewritten), `wizard-work/ledger/build_dir_census.py` (wrapper), `wizard-work/ledger/build_2026-10-31_ledger_dir_census.py` (wrapper), `CHECK-ledger-dir-census` (subject and rc-2 on `cd`), `wizard-work/ledger/2026-10-31-ledger-dir-census.csv` (regenerated, 594 → 580 tracked rows), `wizard-work/ledger/2026-10-31-ledger-dir-census.manifest.json` (new), `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), `checkins/2026-10-31-volt.md` (appended). Nothing from `inbox/` is quoted.
 
 CHECK: bash CHECK-ledger-dir-census
+
+**Q141 addendum, same tick — the landing readings, and one claim this item does not make.** The record above was written before its commit; these are the readings after. Landed as `52b9ace`; a clean clone of that commit (`wizard-outputs/volt/q141/clone-52b9ace`, `git clone --no-local`) reads `rows committed: 580   rows derived: 580`, `match 580   drift 0   extra 0   missing 0`, `currency: HEAD 52b9aceff9e9 is past the pin 40921f3ff69b -- 0 added, 0 removed, 0 changed`, **rc 0** — the same five numbers the worktree reads, which is the property the old checker could not produce (it read `594 vs 598` on the host and `594 vs 580` in a clone of one commit). The self-test runs from the clone too: `--self-test` → **11 cells, 11 passed, 0 failed, rc 0**, so the cells travel with the tree rather than with the host that wrote them. Artifact digests: CSV sha256 `06619951f4c4`, manifest sha256 `7e66616282a9` (`rev` `40921f3ff69b650f4dc0cf0a7594b097635dc0b3`, `rows` 580, `rev_subject` "ledger: grade the dir census at a pinned rev over tracked blobs (Q141 tooling)"). Full repo gate on the staged tree before the commit: `python3 tools/verify.py` → **12 legs, 12 pass, 0 fault, 0 ungradable, 0 skipped**, `gate: OK`, rc 0. **Not claimed:** that this check runs inside the repo gate — it does not; `bash CHECK-ledger-dir-census` is run by a reader or by a tick that names it, which is the Q140 convention for a lane artifact, and adding a thirteenth leg is a separate change to `tools/verify.py`'s `LEGS`, its selftest count cells and the sweep baseline, not a side effect of this repair.
+
+Files edited for this addendum: `WORK-QUEUE.md` (this addendum, appended), `docs/queue-index.md` (re-rendered), `checkins/2026-10-31-volt.md` (appended).

checkins/2026-10-31-volt.md

@@ -225,3 +225,36 @@ q136: sandbox FAULT    8 path(s) opened, 0 outside the sandbox,
   to Q140 and its directory moved with it.
 - Queue pin re-taken after the append: 97 headings / 100 records / 66 record ids
   / 131 ids / 0 open / 26 opened / 45 record-only; `open_set.py --check` rc 0.
+
+## Q141 — the ledger dir census graded its host; now it grades a pinned rev
+
+- Entry state, two verdicts on one commit: `bash CHECK-ledger-dir-census` → rc 1,
+  594 committed vs 598 re-derived in the worktree; the same check in a clean
+  clone of `3747f17` → rc 1, 594 vs 580 (20 `__pycache__/*.pyc` rows on the
+  host, 0 in the clone). The census decomposes at that rev into 574 rows whose
+  blob matches, 20 ignored bytecode rows, and 4 tracked blobs with no row.
+- Repair: `wizard-work/ledger/verify_ledger_dir_census.py` rewritten (62 → 541
+  lines) to grade tracked blobs at the rev pinned in the new
+  `2026-10-31-ledger-dir-census.manifest.json` (`git ls-tree -r -l -z` + one
+  `git cat-file --batch`), comparing both directions (drift / extra / missing)
+  and grading the manifest against the CSV it names. rc 0/1/2, and an
+  unresolvable rev is 2, never a pass. Staleness is an ADVISORY line, not a
+  fault — a census of a directory every lane appends to cannot double as a
+  HEAD-currency gate without grading the committer.
+- The two `os.walk` builders (`build_dir_census.py`,
+  `build_2026-10-31_ledger_dir_census.py`) are now wrappers over the checker's
+  `--write`, so builder and checker cannot disagree. `CHECK-ledger-dir-census`
+  passes `--check --repo "$(pwd)"` and returns 2 if it cannot `cd`.
+- Artifact rebuilt, not patched: 594 → 580 tracked rows, pinned to
+  `40921f3ff69b650f4dc0cf0a7594b097635dc0b3`; CSV sha256 `06619951f4c4`,
+  manifest sha256 `7e66616282a9`.
+- Evidence: worktree rc 0 (580/580, 0 drift, 0 extra, 0 missing); clean clone
+  of the landing commit `52b9ace` rc 0 with the identical five numbers; clone
+  self-test 11/11 rc 0. Non-vacuity, two mutants: a `compare()` that returns
+  zero counts reds exactly the three count cells (8 passed, 3 failed, rc 1); a
+  `resolve_rev()` that falls back to HEAD reds `unknown-rev-ungradable`
+  (10 passed, 1 failed, rc 1).
+- Gate on the staged tree before the commit: `python3 tools/verify.py` → 12
+  legs, 12 pass, 0 fault, 0 ungradable, 0 skipped, rc 0.
+- Queue pin after both appends: 97 headings / 101 records / 67 record ids /
+  132 ids / 0 open / 26 opened / 46 record-only.

docs/queue-index.md

@@ -226,7 +226,7 @@
 | 216 | Q138 | record | 13879-13896 | 6525 | record: BOLD-LEAD | **Q138 — OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `cddf976` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken). The eleventh gate leg … | -- |
 | 217 | Q139 | record | 13897-13917 | 6890 | record: BOLD-LEAD | **Q139 — OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `2e97e4d` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken). Q138's own record closes … | -- |
 | 218 | Q140 | record | 13918-13937 | 6553 | record: BOLD-LEAD | **Q140 — OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `78f1139` and the commit this record lands in; ledger lane by authorship, unclaimed and taken). The ledger directory census does … | -- |
-| 219 | Q141 | record | 13938-13956 | 7675 | record: BOLD-LEAD | **Q141 — OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `3747f17` and the commit this record lands in; ledger lane by authorship, unclaimed and taken, and the repair Q140 handed over). … | -- |
+| 219 | Q141 | record | 13938-13960 | 9431 | record: BOLD-LEAD | **Q141 — OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `3747f17` and the commit this record lands in; ledger lane by authorship, unclaimed and taken, and the repair Q140 handed over). … | -- |
 
 ## Ids with no `## ` heading
 
@@ -283,8 +283,8 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q137 | 13847 | 13847 | 3 | Q136 | BULLET+BOLD | BOLD-LEAD |
 | Q138 | 13879 | 13879 | 7 | Q137 | BULLET+BOLD | BOLD-LEAD |
 | Q139 | 13897 | 13897 | 3 | Q138 | BULLET+BOLD | BOLD-LEAD |
-| Q140 | 13918 | 13918 | 7 | Q139 | BULLET+BOLD | BOLD-LEAD |
-| Q141 | 13938 | 13938 | 1 | Q140 | BULLET+BOLD | BOLD-LEAD |
+| Q140 | 13918 | 13918 | 8 | Q139 | BULLET+BOLD | BOLD-LEAD |
+| Q141 | 13938 | 13938 | 3 | Q140 | 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`.
 
@@ -1870,12 +1870,12 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q140 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `78f1139` and the commit this record lands in; ledger lane by authorship, unclaimed and taken). The ledger directory census does \u2026"
   },
   {
-   "bytes": 7675,
-   "end_line": 13956,
+   "bytes": 9431,
+   "end_line": 13960,
    "id": "Q141",
    "kind": "record",
    "line": 13938,
-   "lines": 19,
+   "lines": 23,
    "role": "record",
    "role_detail": "BOLD-LEAD",
    "status": null,
@@ -4853,12 +4853,12 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q140 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-10-31, at `78f1139` and the commit this record lands in; ledger lane by authorship, unclaimed and taken). The ledger directory census does \u2026"
   },
   {
-   "bytes": 7675,
-   "end_line": 13956,
+   "bytes": 9431,
+   "end_line": 13960,
    "id": "Q141",
    "kind": "record",
    "line": 13938,
-   "lines": 19,
+   "lines": 23,
    "role": "record",
    "role_detail": "BOLD-LEAD",
    "status": null,
@@ -5313,7 +5313,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q140",
    "line": 13918,
-   "refs": 7,
+   "refs": 8,
    "section": "Q139",
    "shape": "BULLET+BOLD"
   },
@@ -5322,7 +5322,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q141",
    "line": 13938,
-   "refs": 1,
+   "refs": 3,
    "section": "Q140",
    "shape": "BULLET+BOLD"
   }
@@ -5332,9 +5332,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 2313866,
- "queue_lines": 13956,
- "queue_sha256": "9060bf8c8d367a11be41846725f838ec20dc7ac42929304fa077e960c4a25742",
+ "queue_bytes": 2315622,
+ "queue_lines": 13960,
+ "queue_sha256": "5440e9d6448a9c789b9c24cb6bba2872ff8e344a8c6abff6e23c594d273b292e",
  "sections": [
   {
    "bytes": 3139,