volt: Q170 land (2/2) -- record (6) states the two baseline rows, index re-rendered

WORK-QUEUE.md

@@ -14770,6 +14770,6 @@ CHECK: `bash wizard-work/volt/q69_q118hostpin_check.sh`
 
 **(5) Evidence, all measured in this tick.** `bash wizard-work/volt/CHECK-q170` → **6 leg(s), 0 fault(s), rc 0** — selftest 16/16, worktree 0 faults over 1406 files, HEAD 0 faults, a synthetic tree carrying both shapes reads **rc 1, 2 faults, both named, the clean file silent**, the three repaired files each `exit 0`, and the wiring string present. `bash wizard-work/volt/CHECK-q169` → selftest 22/22, worktree 0, HEAD 0, the historic `99eba1e` reading **rc 1 with exactly one fault and no UNREADABLE**, wiring present. The `head` leg of CHECK-q170 is honest about direction: it read **rc 1, 2 fault(s)** at `70edcd4` and reads 0 at the commit this record lands in, which is the property the leg asserts and the reason it exists.
 
-**(6) Bookkeeping, measured after this append and before the commit landed.** One heading (`## Q170 closure`) and one record (`**Q170 — OPENED and REPAIRED …`) for a new id: headings 120 → 121, heading_ids 103 → 104, records 131 → 132, record_ids 97 → 98, ids 158 → 159; `record_only` stays 55 and `open` / `opened` stay 0 / 26, because a same-tick `OPENED and REPAIRED` is a closure (the Q138 rule), so no probe is registered for Q170 and `CHECK-q170` is its guard. `PIN_COUNTS` in `wizard-work/volt/q137-open-set/open_set.py` moved to those counts; `python3 tools/queue_index.py --write docs/queue-index.md` re-rendered; one row added to `wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv` for `CHECK-q170` with the code measured at this landing.
+**(6) Bookkeeping, measured after this append and before the commit landed.** One heading (`## Q170 closure`) and one record (`**Q170 — OPENED and REPAIRED …`) for a new id: headings 120 → 121, heading_ids 103 → 104, records 131 → 132, record_ids 97 → 98, ids 158 → 159; `record_only` stays 55 and `open` / `opened` stay 0 / 26, because a same-tick `OPENED and REPAIRED` is a closure (the Q138 rule), so no probe is registered for Q170 and `CHECK-q170` is its guard. `PIN_COUNTS` in `wizard-work/volt/q137-open-set/open_set.py` moved to those counts; `python3 tools/queue_index.py --write docs/queue-index.md` re-rendered; two rows added to `wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv` for `CHECK-q169` and `CHECK-q170` -- both are entry points discovery sees and the baseline did not name -- with the codes measured at this landing: 5 legs and 6 legs, 0 faults. q170's `head` leg grades HEAD, so it read **1 (2 faults)** in the worktree before this commit and **0** at it, which is the reading the row carries. The sweep's `--paths` leg still reads **27 NEW** rows for other lanes' entry points; this record does not sign those.
 
 **(7) Not claimed.** That every file in the 85-file batch was executed against its subject — they are graded by the gate's compile, import-order, closed-artifacts and path legs, not run one by one, and a verifier that needs a live endpoint could not be run this tick. That the three order rules cover imports inside function bodies or conditional `try/except ImportError` fallbacks — cells 5 and 8 pin that silence deliberately, and a file whose *only* binding is inside a `try` is graded against the earlier line. That `verify_dates.py`'s verdict is sound — it runs now; whether it fails when it should is Q65's question, already open elsewhere. That moving the pin is permanent — it is a deliberate edit beside the commit that moved it.

docs/queue-index.md

@@ -281,7 +281,7 @@
 | 271 | Q168 | record | 14696-14715 | 8237 | cont: OPENED | **Q168 — OPENED and REPAIRED in the same tick (volt; opened, repaired and measured in the 2026-11-04 12:29 tick at `12fb1b0`, and recorded by the commit this record lands in; tools lane, no lane owns … | -- |
 | 272 | Q69 | heading | 14716-14756 | 9732 | cont: addendum | addendum 3 — the pipe monitor's verifier carried the host pin three times, and its host-cache leg watched paths it had typed rather than the module's; volt reads 7 code files / 12 constants *(volt … | -- |
 | 273 | Q170 | heading | 14757-14758 | 17 | opening | closure | -- |
-| 274 | Q170 | record | 14759-14775 | 8455 | cont: OPENED | **Q170 — OPENED and REPAIRED in the same tick (volt, 2026-11-05, at `70edcd4` and the commit this record lands in; tools lane, no lane owns it by authorship, unclaimed and taken).** The repository's … | -- |
+| 274 | Q170 | record | 14759-14775 | 8843 | cont: OPENED | **Q170 — OPENED and REPAIRED in the same tick (volt, 2026-11-05, at `70edcd4` and the commit this record lands in; tools lane, no lane owns it by authorship, unclaimed and taken).** The repository's … | -- |
 
 ## Ids with no `## ` heading
 
@@ -2337,7 +2337,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q168 \u2014 OPENED and REPAIRED in the same tick (volt; opened, repaired and measured in the 2026-11-04 12:29 tick at `12fb1b0`, and recorded by the commit this record lands in; tools lane, no lane owns \u2026"
   },
   {
-   "bytes": 8455,
+   "bytes": 8843,
    "end_line": 14775,
    "id": "Q170",
    "kind": "record",
@@ -6071,7 +6071,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "closure"
   },
   {
-   "bytes": 8455,
+   "bytes": 8843,
    "end_line": 14775,
    "id": "Q170",
    "kind": "record",
@@ -6631,9 +6631,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 2575446,
+ "queue_bytes": 2575834,
  "queue_lines": 14775,
- "queue_sha256": "9f96c01339f569d138172c899a00ea3b7e51272196ee2d1a7fe9b35366065014",
+ "queue_sha256": "b3192f768417f5f2de4f269422da28e17cf6b6014c0d5cd14201cec9ac058fee",
  "sections": [
   {
    "bytes": 3139,

wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv

@@ -121,6 +121,21 @@ wizard-work/volt/CHECK-q132	0	q132: 9 leg(s), 0 fault -- OK
 wizard-work/volt/CHECK-q133	0	q133: 5 leg(s), 5 passed, 0 fault(s) -- beam cells import the module beside them
 wizard-work/volt/CHECK-q134	0	q134: 3 leg(s), 3 passed, 0 fault(s)
 wizard-work/volt/CHECK-q136	0	q136: 7 leg(s), 7 passed, 0 fault(s)
+# rows added by hand (Q170, 2026-11-05): `CHECK-q169` and `CHECK-q170` are new entry
+# points under `wizard-work/volt/`, so discovery sees them and the baseline did not
+# name them (the sweep's --paths leg read 29 NEW before these two rows). Codes
+# measured, not read: `bash wizard-work/volt/CHECK-q169` -> 5 legs (selftest 22/22,
+# worktree 0 faults, HEAD 0 faults, the historic blob, wiring), ~9 s; and
+# `bash wizard-work/volt/CHECK-q170` -> 6 legs (selftest 16/16, worktree 0, HEAD 0,
+# a synthetic tree red with both shapes named, the three repaired files exit 0,
+# wiring), ~40 s. q170's `head` leg grades HEAD, so in the worktree that preceded
+# the commit it read 1 (2 faults at 70edcd4) and 0 at the commit this row lands in;
+# the 0 above is the post-commit reading, re-taken and printed by that guard.
+# These rows are readings, not waivers: each guard reads 1 when its subject stops
+# holding. The sweep still reads 27 NEW rows for other lanes' entry points, which
+# this tick does not claim to have signed.
+wizard-work/volt/CHECK-q169	0	q169: 5 leg(s), 0 fault(s)
+wizard-work/volt/CHECK-q170	0	q170: 6 leg(s), 0 fault(s)
 wizard-work/volt/CHECK-q89	0	q89: 24 leg line(s), 0 fault -- OK
 wizard-work/volt/CHECK-q90	0	q90: 7 leg(s), 0 fault -- OK
 wizard-work/volt/CHECK-q97	0	Q97 GATE: rc 0 -- a refusal that echoes the invocation is fatal on both input axes, and a mutating flag rename is caught.