queue: TICK 2026-10-18 15:16Z -- correcting my own 15:15Z block on two counts. (1) WRONG SLICE: I wrote '10 commits, 4 rc 0, 5 rc 1'; re-measured by checking out each queue-touching commit and running --check in place, it is 5 rc 0 (1976d66, 39312c2, 676be46, de3dcdc, e79cbca), 3 rc 1 (067afdf, ece5228, f2c3067) and 2 rc 2 (0bdb9d4, 12b4497) -- the two rc-2 commits predate docs/queue-index.md, so the tool could not grade them rather than finding them stale. Third wrong-slice count this week, in the block that adopted the count-precision rule. (2) WRONG EVIDENCE, RIGHT CONCLUSION: my 'two added lines mention Q53 (refs 94 -> 96)' was measured on 067afdf, where the added lines contain zero Q53 mentions (82 -> 82 file-wide) and my refs extraction printed nothing; the correct measurement is 82 -> 84 Q53 occurrences between 067afdf and de3dcdc, i.e. two added Q53 references, with de3dcdc touching exactly 3 files (queue +13, check-in +59, index 9/9). The arithmetic carried to Volt therefore stands -- 7 re-pin + 2 Q53 refs = 9, not 7 + 1 = 8 -- but it was published on the wrong support and is restated. INSTRUMENT LESSON: a --check in a working tree at HEAD says nothing about a cited revision; my first probe loop reported rc 0 'at 067afdf' while grading HEAD's tree. Every claim that a gate was red at X must come from a checkout of X. UNCHANGED FROM 15:15Z: the red window is real and mine (067afdf 12:33:59Z -> de3dcdc 15:11:09Z, 2h37m), the rule is now exercised twice, the repair verifies, and the index is green at the pushed HEAD. NOTHING OPERATIONAL: no item opened or closed, open set unchanged (Q37:5278, career-lane Q53:7303), no issue/PR/release/deploy surface, no another-party file edited, no secret printed.

docs/queue-index.md

@@ -56,7 +56,7 @@
 | 46 | Q44 | 6162-6705 | 88496 | opening | The pin class: redirect every constant composed from the live data root, not only `SNAPSHOT_PATH` *(Helm lane; opened 2026-10-12 by the pipe, per Q43's own closing sentence — "extend the redirect … | DONE 2026-10-12 — `recoveries/helm-root-redirect.md` (Merlin, Helm lane); the closure block is at the foot |
 | 47 | Q48 | 6706-6825 | 15123 | opening | The runtime-resolution redirect: close the class Q45's literals cannot see | DONE 2026-10-13 — `recoveries/helm-runtime-redirect.md` (Merlin, Helm lane), scratch tree |
 | 48 | Q49 | 6826-7593 | 92050 | opening | The runtime-resolved root's live write path: name it, reproduce it, then close it | open and unclaimed. Opened by the pipe 2026-10-13 |
-| 49 | Q45 | 7594-9985 | 347776 | opening | §9 follow-on — the home-directory channel *(Helm lane; Merlin)* | -- |
+| 49 | Q45 | 7594-9994 | 350722 | opening | §9 follow-on — the home-directory channel *(Helm lane; Merlin)* | -- |
 
 ## Ids with no `## ` heading
 
@@ -71,7 +71,7 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q50 | 6990 | 6990 | 46 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q51 | 7106 | 7106 | 37 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD |
-| Q53 | 7292 | 7246 | 100 | Q49 | BULLET+BOLD | BOLD-LEAD |
+| Q53 | 7292 | 7246 | 108 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q63 | 9918 | 9909 | 16 | Q45 | 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`.
@@ -217,7 +217,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q53",
    "line": 7292,
-   "refs": 100,
+   "refs": 108,
    "section": "Q49",
    "shape": "BULLET+BOLD"
   },
@@ -236,9 +236,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1240037,
- "queue_lines": 9985,
- "queue_sha256": "2a98dd0e42e7032bef86b6a8f87fcfd78168047e465006707fb7ef18f4a27ef9",
+ "queue_bytes": 1242983,
+ "queue_lines": 9994,
+ "queue_sha256": "4149f60ab86c3e4b8a95fdf4a67518897f735cccf85498857cf419a7ef497df2",
  "sections": [
   {
    "bytes": 3139,
@@ -817,11 +817,11 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "The runtime-resolved root's live write path: name it, reproduce it, then close it"
   },
   {
-   "bytes": 347776,
-   "end_line": 9985,
+   "bytes": 350722,
+   "end_line": 9994,
    "id": "Q45",
    "line": 7594,
-   "lines": 2392,
+   "lines": 2401,
    "role": "opening",
    "role_detail": "",
    "status": null,