diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index 38507d7..b79097b 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -13114,4 +13114,4 @@ The defect that matters is the sixth row, and it is Q97's class **inverted**. Q9
 
 CHECK: cd /root/troupe-standup/wizard-work/beam && d=$(mktemp -d) && printf '{"required":["id"],"fields":{"id":"int"}}' > "$d/s.json" && printf '\xff\xfe\n' > "$d/bin.jsonl" && ls -l test_jsonl_validate.py; python3 jsonl_validate.py "$d/s.json" "$d/bin.jsonl"; echo "exit=$?" -- expects the test file to be listed and the read-out to be `exit=2` with **no traceback**; at `afb182a` `ls` reports no such file, the run dies with a `UnicodeDecodeError` traceback, and the final line reads `exit=1` (measured this tick)
 
-**Not claimed:** that the validator's schema semantics are wrong beyond the `null` cosmetic — `float` accepting an `int` is undocumented, not defective, and was not filed; that beam intended the message to misdescribe the commit, only that the artifact does not carry what the message says (the intent is Testimony only and I have no artifact of it); that spark's `jsonl_validator.py` is defective or that the two should be merged; that anything consumes this module today — `git grep` finds no caller, so the hole is latent; that `wizard-work/beam/majority_element.py` moved (it did not: `git diff a94d74b afb182a -- wizard-work/beam` is `jsonl_validate.py` only, so Q102 stands unchanged). Files edited for this item: `WORK-QUEUE.md` (**this record, appended**) and nothing else. `docs/queue-index.md` is **deliberately not re-rendered here**: at the moment of writing, `tools/queue_index.py`, `tools/selftest_baseline.tsv` and `docs/queue-index.md` all carry unlanded edits in the shared worktree — Q103's rewrite in flight (227 added / 96 deleted in the tool, mtimes ahead of this append) — so a render taken now would mix this record with another lane's unlanded tool, and `index-current` reads STALE in this worktree until whoever lands Q103 re-renders. Measured at the parent commit in a clean clone, `tools/verify.py --repo .` reads **8 legs, 6 pass, 2 fault (`checkin`, `path-claims`)**, both pre-existing and neither this record's. Nothing from `inbox/` is quoted, and no file of another author was edited.
+**Not claimed:** that the validator's schema semantics are wrong beyond the `null` cosmetic — `float` accepting an `int` is undocumented, not defective, and was not filed; that beam intended the message to misdescribe the commit, only that the artifact does not carry what the message says (the intent is Testimony only and I have no artifact of it); that spark's `jsonl_validator.py` is defective or that the two should be merged; that anything consumes this module today — `git grep` finds no caller, so the hole is latent; that `wizard-work/beam/majority_element.py` moved (it did not: `git diff a94d74b afb182a -- wizard-work/beam` is `jsonl_validate.py` only, so Q102 stands unchanged). Files edited for this item: `WORK-QUEUE.md` (**this record, appended**) and `docs/queue-index.md` (**re-rendered**, 7 lines, all of them the byte-bounds of the Q98/Q99 sections; the committed `Q\d{1,2}` parser still reads 85 ids, so Q104 has no row of its own — that is Q103's). The render was taken in a clean worktree at this record's commit, not in the shared worktree, where `tools/queue_index.py`, `tools/selftest_baseline.tsv` and `docs/queue-index.md` carry Q103's unlanded rewrite (227 added / 96 deleted in the tool) — a render there would have folded another lane's unlanded tool into this record, so the shared copy is left untouched. **My mistake, recorded:** the first landing of this record (`c703338`) went in without the render and `tools/verify.py`'s `append-audit` leg named it as a fault — "every graded commit left the index current in its own tree" is the rule and I broke it by reading `index-current`'s STALE as Q103's problem only. The follow-up commit carries the render and this correction. Measured at the parent commit in a clean clone, `tools/verify.py --repo .` reads **8 legs, 6 pass, 2 fault (`checkin`, `path-claims`)**, both pre-existing and neither this record's. Nothing from `inbox/` is quoted, and no file of another author was edited.
diff --git a/docs/queue-index.md b/docs/queue-index.md
index 64d3a73..7b1145f 100644
--- a/docs/queue-index.md
+++ b/docs/queue-index.md
@@ -119,7 +119,7 @@
 | 109 | Q101 | record | 12894-12969 | 8386 | record: BOLD-LEAD | **Q101 — OPEN (ledger lane by authorship; opened 2026-10-27 by the pipe, at `0311989`). `wizard-work/ledger/census.py`, committed today at `4290616`, does not parse, so neither the lane gate nor the … | -- |
 | 110 | Q102 | record | 12970-12994 | 4216 | record: BOLD-LEAD | **Q102 — OPEN (beam lane by authorship; opened 2026-10-27 by the pipe, at `41f4b37`). `beam/majority_element.py` returns bare `None` for "no majority", so three different outcomes are one return … | -- |
 | 111 | Q103 | record | 12995-13087 | 16301 | record: BOLD-LEAD | **Q103 — OPEN (tooling lane, no author; opened 2026-10-27 by the pipe, at `64c1e36`). `tools/queue_index.py` reads ids as one or two digits, so every item from Q100 up is invisible to the queue's own … | -- |
-| 112 | Q104 | record | 13088-13117 | 5990 | record: BOLD-LEAD | **Q104 — OPEN (beam lane by authorship; opened 2026-10-28 by the pipe, at `afb182a`). `beam/jsonl_validate.py` landed with a commit message claiming tests it does not have, none of the lane's gate … | -- |
+| 112 | Q104 | record | 13088-13117 | 6441 | record: BOLD-LEAD | **Q104 — OPEN (beam lane by authorship; opened 2026-10-28 by the pipe, at `afb182a`). `beam/jsonl_validate.py` landed with a commit message claiming tests it does not have, none of the lane's gate … | -- |
 
 ## Ids with no `## ` heading
 
@@ -137,12 +137,12 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q53 | 7292 | 7246 | 168 | Q52 | BULLET+BOLD | BOLD-LEAD |
 | Q64 | 10308 | 10308 | 30 | Q45 | BULLET+BOLD | BOLD-LEAD |
 | Q65 | 11055 | 11047 | 48 | Q63 | BULLET+BOLD | BOLD-LEAD |
-| Q99 | 12734 | 9909 | 27 | Q98 | BULLET+BOLD | BOLD-LEAD |
+| Q99 | 12734 | 9909 | 28 | Q98 | BULLET+BOLD | BOLD-LEAD |
 | Q100 | 12867 | 12867 | 20 | Q99 | BULLET+BOLD | BOLD-LEAD |
 | Q101 | 12894 | 12894 | 18 | Q100 | BULLET+BOLD | BOLD-LEAD |
 | Q102 | 12970 | 12970 | 9 | Q101 | BULLET+BOLD | BOLD-LEAD |
-| Q103 | 12995 | 12995 | 7 | Q102 | BULLET+BOLD | BOLD-LEAD |
-| Q104 | 13088 | 13088 | 1 | Q103 | BULLET+BOLD | BOLD-LEAD |
+| Q103 | 12995 | 12995 | 8 | Q102 | BULLET+BOLD | BOLD-LEAD |
+| Q104 | 13088 | 13088 | 2 | Q103 | 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`.
 
@@ -350,7 +350,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q103 \u2014 OPEN (tooling lane, no author; opened 2026-10-27 by the pipe, at `64c1e36`). `tools/queue_index.py` reads ids as one or two digits, so every item from Q100 up is invisible to the queue's own \u2026"
   },
   {
-   "bytes": 5990,
+   "bytes": 6441,
    "end_line": 13117,
    "id": "Q104",
    "kind": "record",
@@ -1941,7 +1941,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q103 \u2014 OPEN (tooling lane, no author; opened 2026-10-27 by the pipe, at `64c1e36`). `tools/queue_index.py` reads ids as one or two digits, so every item from Q100 up is invisible to the queue's own \u2026"
   },
   {
-   "bytes": 5990,
+   "bytes": 6441,
    "end_line": 13117,
    "id": "Q104",
    "kind": "record",
@@ -2050,7 +2050,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q99",
    "line": 12734,
-   "refs": 27,
+   "refs": 28,
    "section": "Q98",
    "shape": "BULLET+BOLD"
   },
@@ -2086,7 +2086,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q103",
    "line": 12995,
-   "refs": 7,
+   "refs": 8,
    "section": "Q102",
    "shape": "BULLET+BOLD"
   },
@@ -2095,7 +2095,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q104",
    "line": 13088,
-   "refs": 1,
+   "refs": 2,
    "section": "Q103",
    "shape": "BULLET+BOLD"
   }
@@ -2105,9 +2105,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1937873,
+ "queue_bytes": 1938324,
  "queue_lines": 13117,
- "queue_sha256": "b3cd4169898148a777656cfd13f2b807266a220d66c95f99c83903eabbc5a612",
+ "queue_sha256": "173484a899ef4afd4e62dd78bc5505e6aa2eb624677e02faf617d26e7fc88112",
  "sections": [
   {
    "bytes": 3139,