queue: land the Q165/Q166 records with their index render, and sign the two

guards that landed unsigned

WORK-QUEUE.md carried the Q165 and Q166 records uncommitted while the pin,
the path-claim baseline and the entry baseline had already moved -- the
defect Q154 filed against another lane, in this lane's own worktree. The
index had been rendered before the Q165 record's final paragraph, so
`queue_index.py --check` read STALE at line 271 and the repo gate's
index-current leg read FAULT.

- docs/queue-index.md re-rendered by `tools/queue_index.py --repo . --write`
  (315,689 bytes; 263 items, 114 sections, 149 record blocks, 101 ids).
- CHECK-q159 and its module wizard-work/volt/q143-check-sweep/block_rows.py
  land with the record that names them, so the sweep's MISSING row is signed.
- check_entry_baseline.tsv: CHECK-q164 and CHECK-q166 were tracked guards with
  no signed row, so `check_sweep.py --paths` read both as NEW; their codes were
  measured here (q164 7 legs in 55.1 s, q166 4 legs) and signed. CHECK-q159's
  tally string was re-measured (5 legs -> 6).

Measured before this commit, at this worktree: verify.py --fast 12 legs,
11 pass, 0 fault, 1 skipped, gate OK, rc 0; check_sweep.py --paths 159 entry
points, 147 baseline paths, 12 faults -- 14 before the two rows, and the 12
that remain are other lanes' NEW rows, named in the report.

tools/path_claim_baseline.tsv

@@ -297,4 +297,10 @@ verify_wordcount_test.py	EXAMPLE	quoted at WORK-QUEUE.md:14386 (Q157 record) as
 wizard-work/null/.hermes-tmp.RqZp3z	EXAMPLE	quoted at WORK-QUEUE.md:14386 (Q157 record) beside the row above, for the same reason: a temporary file the 2026-10-28 snapshot froze and the tree no longer carries; 0 add-commits on any ref, so it was never a tracked path this archive lost
 wizard-work/volt/q157-newentry/newentry_readings.tsv	NOT_ADDED	cited at WORK-QUEUE.md:14361 (Q157 record) as one of the four paths the live untracked set had added since the 4a640e1 pin -- the record is describing drift, and this file is part of that drift; it is untracked in this worktree, 0 add-commits on any ref, and is the measurement a prior volt tick took of the 18 unnamed entry points (check_sweep.py --paths), left for its own item
 wizard-work/volt/q157-newentry/newentry_take.py	NOT_ADDED	cited at WORK-QUEUE.md:14361 beside the row above and for the same reason: the runner that took that measurement; untracked in this worktree, 0 add-commits on any ref
-wizard-work/beam/_run_regex.py	NOT_ADDED	cited at WORK-QUEUE.md:14553 (Q164 record) as the untracked file whose presence moved the beam coverage census -- 159 B, mtime 2026-11-03 10:50, a six-line hand runner over test_regex_match of the same shape as _run_tests.py -- and it is the item that it must NOT be graded: it is untracked in this worktree, git log --all --diff-filter=A -- wizard-work/beam/_run_regex.py -> 0 commits, and check_coverage.py now names it in a note instead of counting it. Tracking it would make it a lane module with no reader, which is the verdict this item removes
+# CLEARED 2026-11-03 (Q165): wizard-work/beam/_run_regex.py was a NOT_ADDED row
+# here, cited at WORK-QUEUE.md:14553 (Q164 record) as the untracked six-line hand
+# runner whose presence moved the beam coverage census. `2829ff0` committed it, so
+# the path is now in the tree, the census names it as an EXEMPT waiver with its
+# reason stated, and the tool reads the row as CLEARED. Removed from the graded
+# ledger and kept here as the reading rather than deleted silently.
+wizard-work/beam/zz_q164_scratch_probe.py	NOT_ADDED	cited at WORK-QUEUE.md:14583 (Q165 record) as the two-line scratch probe a previous tick's CHECK-q164 scratch leg left behind and this tick removed; git log --all --diff-filter=A -- wizard-work/beam/zz_q164_scratch_probe.py -> 0 commits, and it is named in that record as removed precisely so a reader can check the tree holds none of it