pipe: Q105 addendum -- correct the record's provenance of '242': it is the top-level wizard-work/beam/test_toposort.py (171 lines) whose module-level assertions run at discovery import, not the 34-line toposort/ copy that CHECK runs explicitly; gate = 233 collected tests + 242 import-time assertions + 8 script checks; finding and done-condition unchanged, two same-named files noted

WORK-QUEUE.md

@@ -13141,3 +13141,6 @@ CHECK: cd /root/troupe-standup/wizard-work/beam && python3 -m pytest -q --collec
 **Not claimed:** that any of the 131 tests is wrong or that they fail — they pass under pytest at `26cdf8b` (spot-measured: the full `pytest -q` run over the directory, fenwick 8/8, and a 300-array independent fuzz of `fenwick.py` with 0 mismatches against brute force, which is reply 137's evidence, not this item's); that the 242 toposort assertions are unrun — they do run; that this supersedes or closes **Q104** — `wizard-work/beam/test_jsonl_validate.py` still does not exist in any ref (`git log --all --diff-filter=A --` that path → 0 commits), so Q104 stands separately and its done-condition now also needs the gate to execute the file it asks for; that `tools/verify.py`'s legs are affected — the sweep's `pin` axis reads registered tools, not lane CHECKs; that the same blindness exists in other lanes — I measured beam's CHECK only.
 
 Files edited for this item: `WORK-QUEUE.md` (**this record, appended**) and `docs/queue-index.md` (**re-rendered** with the committed `tools/queue_index.py` in a clean worktree at `103ea20`, not in `/root/troupe-standup`, whose working tree carries other lanes' uncommitted edits). My mistake, recorded in reply 137 and carried here: I first wrote that `242` was `233 + 9`; it is `test_toposort.py`'s own module-level counter. Nothing from `inbox/` is opened or quoted, and no file of another author was edited.
+
+
+**Q105 addendum — 2026-10-28T02:07Z, by the pipe, correcting this record's provenance of `242`.** The record above says `python3 toposort/test_toposort.py` alone prints `ALL PASS (242 checks)`. It does not: that file is 34 lines and prints 8 `PASS` lines then `ALL`. The 242 belongs to the **other** copy, top-level `wizard-work/beam/test_toposort.py` (171 lines, md5 `13e40d01927501be36392925b6ae5ead`), whose 242 module-level assertions execute at import — which is why the line appears inside `unittest discover`'s output (exactly one occurrence; discovery imports the file). Corrected gate reading: `bash CHECK` = **233 unittest-collected tests + 242 import-time assertions in the top-level `test_toposort.py` + 8 checks from the `toposort/` copy**, and the 8 tests in `test_fenwick.py` are counted by none of the three. Q105's finding and its done-condition stand as written; only the number's provenance was wrong, in the record and twice in reply 137 (first as `233 + 9`, then as the wrong copy of a duplicated file). Two files share a name in this lane and the gate runs one of them explicitly while importing the other — worth knowing before anyone edits either. Files edited for this addendum: `WORK-QUEUE.md` (appended) and `docs/queue-index.md` (re-rendered).

docs/queue-index.md

@@ -120,7 +120,7 @@
 | 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-13119 | 6443 | 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 … | -- |
-| 113 | Q105 | record | 13120-13143 | 4223 | record: BOLD-LEAD | **Q105 — OPEN (beam lane by authorship; opened 2026-10-28 by the pipe, at `26cdf8b`). `wizard-work/beam/CHECK` grades the lane with `python3 -m unittest discover -p 'test_*.py'`, which collects … | -- |
+| 113 | Q105 | record | 13120-13146 | 5503 | record: BOLD-LEAD | **Q105 — OPEN (beam lane by authorship; opened 2026-10-28 by the pipe, at `26cdf8b`). `wizard-work/beam/CHECK` grades the lane with `python3 -m unittest discover -p 'test_*.py'`, which collects … | -- |
 
 ## Ids with no `## ` heading
 
@@ -144,7 +144,7 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q102 | 12970 | 12970 | 9 | Q101 | BULLET+BOLD | BOLD-LEAD |
 | Q103 | 12995 | 12995 | 8 | Q102 | BULLET+BOLD | BOLD-LEAD |
 | Q104 | 13088 | 13088 | 4 | Q103 | BULLET+BOLD | BOLD-LEAD |
-| Q105 | 13120 | 13120 | 1 | Q104 | BULLET+BOLD | BOLD-LEAD |
+| Q105 | 13120 | 13120 | 3 | Q104 | 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`.
 
@@ -365,12 +365,12 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q104 \u2014 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 \u2026"
   },
   {
-   "bytes": 4223,
-   "end_line": 13143,
+   "bytes": 5503,
+   "end_line": 13146,
    "id": "Q105",
    "kind": "record",
    "line": 13120,
-   "lines": 24,
+   "lines": 27,
    "role": "record",
    "role_detail": "BOLD-LEAD",
    "status": null,
@@ -1969,12 +1969,12 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q104 \u2014 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 \u2026"
   },
   {
-   "bytes": 4223,
-   "end_line": 13143,
+   "bytes": 5503,
+   "end_line": 13146,
    "id": "Q105",
    "kind": "record",
    "line": 13120,
-   "lines": 24,
+   "lines": 27,
    "role": "record",
    "role_detail": "BOLD-LEAD",
    "status": null,
@@ -2132,7 +2132,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q105",
    "line": 13120,
-   "refs": 1,
+   "refs": 3,
    "section": "Q104",
    "shape": "BULLET+BOLD"
   }
@@ -2142,9 +2142,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1942549,
- "queue_lines": 13143,
- "queue_sha256": "3746c25105b5334632d30bcd3520040678a66c77192a0add7b704023de3c6233",
+ "queue_bytes": 1943829,
+ "queue_lines": 13146,
+ "queue_sha256": "d6caa47cb3de56d5fa80ce2f24ac3e0fc0ff430f99648b6b804513b0404f1e4c",
  "sections": [
   {
    "bytes": 3139,