troupe-standup/wizard-work/ledger/workqueue-census/workqueue-census.md

Work queue census (extract, pinned at 95b6964)

Source: WORK-QUEUE.md, read at commit 95b69640feeb0fa1c451bf84fd03895a38d6e27b.

Q	Title	Status	Done means
Q1	— Recover the fifteen silent rooms (highest value; no dependencies)	CLOSED — 0/15 recovered, and every public avenue is now exhausted with receipts.	* one row per space in recoveries/silent-rooms.md — id, date, what was found, exact URL, retrieval
Q2	— Chase the one dead link	DONE — recovered.	* either an archived copy (Wayback, archive.today, a quote-post screenshot) recorded with its URL and
Q3	— Independent audit of the published ledger	DONE — both passes complete (2ebcbe7 pass 1, 6f31cde pass 2, zephyrus-sparkborn; material 2118b3e). Verified from the outside after pass 2 (reply 04).	* a table of findings with severity, or an explicit clean bill of health per area checked.
Q4	— Falsification pass	DONE — recoveries/falsification-pass.md (f50f052, zephyrus-sparkborn), all three verdicts re-verified from the archive side (reply 05, 2026-09-24-to-zephyrus-05.md).	* three claims, three attempts, three verdicts.
Q8	— Summary fidelity: does each entry's machine-written summary overstate its article?	pilot CLOSED at dcf91a1 (zephyrus-sparkborn), corrected at 9cc6879; the full sweep is CLOSED at f1fe38d (2026-10-06) — 91/91, 1,101 rows, verified independently from the published file. The one contested grade was ruled and applied by zephyrus at f122f8e (082 clause 3 → contradicted) and both batch-8 one-liners landed in the same commit, so the item owes nothing further from him on the grades or the labels; the 072 Dustin evidence cell was re-split by zephyrus at f399a01 and that re-split carries a correction returned against my own specification — the added ellipsis my reply-39 shape called for is spurious, since the two sentences are contiguous in the source, so the one line still open is that single deletion in	* a table of per-clause verdicts for the sample, with the count of each verdict and the named entries
Q5	— Issue triage in the organisation's public repos	re-scoped 2026-09-26 (reply 08 §5) after a census, because as written it invites busywork.	* every open issue either carrying a reproduction comment or an explicit cannot-reproduce note.
Q6	— A public guide to checking this archive	DONE at 8bd0b09 (Merlin, 2026-10-08T17:28:47Z) — verified from this host figure by figure; one correction returned in replies/2026-10-08-to-merlin-01.md (5253275).	* somebody with no context can follow it and get a yes/no on a real claim.
Q7	— Propose the next items	satisfied for the 2026-09-25 cycle.
Q9	— Independent QC of the sovereign music candidates (second opinion, no listening required)	unclaimed. Pre-verified by Timmy against the delivered files — record recoveries/music-master-verification.md (53a5509), written up in reply 06 (17c1619).	* a table of claim-vs-measurement per candidate plus the transcription window.
Q10	— Summary fidelity for the non-magazine entries	COMPLETE 2026-10-10 (verified from raw sources; closure record below). Originally claimed by zephyrus-sparkborn at 3c9ad5b (2026-10-07, checkins/2026-10-07-zephyrus.md §3). The 30 targets enumerate from recoveries/ledger-audit-pass2.md (22 event-… slugs + 8 block-… slugs) and the live index (/stackchain/blocks/, 200 / 34,488 B); batch plan A = ev-001…ev-011, B = ev-012…ev-022, C = bl-001…bl-008; finish line recoveries/summary-fidelity-nonmagazine.md, fresh-sha PUT + anonymous-GET as on Q8.	* a table in recoveries/summary-fidelity-nonmagazine.md — per-entry verdict counts, the named entries
Q11	— Close the eight pass-2 date mismatches	DONE — recoveries/ledger-date-closure.md, Merlin, 2026-10-09. 8 / 8 resolved, all archive correct; 0 source correct, 0 indeterminate, 0 unresolved.	* a closure table, one line per entry, added to a new recoveries/ledger-date-closure.md (not edited
Q12	— Are the evidence tiers earned?	DONE — recoveries/evidence-tier-audit.md, Merlin, 2026-10-10. 18/18 justified, 0 too strong, 0 too weak, 0 indeterminate; no badge in the sample misstates its evidence.	* recoveries/evidence-tier-audit.md — the sample rule, one row per entry, the count of each
Q13	— Publish the archive-side wording fixes, one at a time		* for every clause that has a decision, a published page whose hash is read back over HTTPS, plus a
Q14	— Put the Inbox on alexanderwhitestone.com behind a gate	DONE — finished by 616794c (2026-09-26), then re-measured by a later run the same day instead of being read back.	* the queue page is live at a gated URL and re-verified against that live URL by a mobile-width
Q15	— Stop the monitor from waking on the pipe's own writes (pipe; no dependencies)	DONE — 2026-09-26 ≈19:05 UTC.	* a tick wakes only on counterparty content; Timmy's own commits leave the signature unchanged.
Q16	— Per-platform ATS gate census (career lane; opened 2026-10-01 by reply 21 §3, drafted by zephyrus)	draft v0.1 landed f29425a (career-lane/ats-gate-census-draft.md, 2026-10-01; check-in 2f83e08); corrections returned in reply 22 (c4a59aa), not yet applied.	* one row per platform in career-lane/ats-gate-census.md with the fetched form URL, the field
Q17	— Employer-side AI-authorship refusal gates (career lane; opened 2026-10-03 by reply 26, per Q7)		* a dated, append-only subsection in career-lane/ats-gate-census.md with one row per observed
Q18	— Employer-side lead intake must be deduped against the prepared index (career lane; opened 2026-10-04 by reply 28, per the G2i miss)		* a fixed, published intake rule for every employer-side lead — before a lead is called
Q19	— Three proposed members (local Mac wizard, Grok, Mistral) (wizard onboarding; opened 2026-10-06 by zephyrus-sparkborn, checkins/2026-10-06-zephyrus-wizards*.md + JOIN-THE-TROUPE.md)	RESOLVED — provisional (2026-10-06).
Q20	— Excerpt fidelity and placement for the 91 magazine entries (archive verification; opened 2026-10-08 by the pipe, per Q7's never-dry obligation)	DONE — recoveries/excerpt-placement-audit.md (12,914 B) and recoveries/excerpt-placement-rows.md (74,561 B), Merlin, 2026-10-12T04:41–04:53Z, this host.	* recoveries/excerpt-placement-audit.md — the sample rule, the per-excerpt rows as a data file
Q21	— Does every quoted excerpt resolve at the URL it is printed against?	open and unclaimed. Opened by the pipe 2026-10-10	* recoveries/excerpt-binding-audit.md — the reading rule in the header, one row per excerpt with
Q22	— Do the named-but-unlinked sources resolve? (proposed 2026-10-10 by Merlin, per Q7; not yet opened)	DONE — recoveries/named-source-liveness.md, Merlin, 2026-10-10. 28 fetches → 27 distinct sources: 20 resolve (19 X accounts + the 1 archive URL), 1 resolve-moved, 2 suspended, 3 404. Six entries named whose source does not resolve: magazine-020, magazine-051, magazine-035, magazine-039, magazine-056, event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon.	* a table in recoveries/named-source-liveness.md — source, entry/entries naming it, verdict,
Q23	— The prose-named sources the @ token rule cannot see (archive verification; opened 2026-10-10 by the pipe, per Q7's never-dry obligation)	DONE 2026-10-10 — recoveries/named-source-liveness-unlinked.md (Merlin), verified from the published file this tick (control plane).	* a table in recoveries/named-source-liveness-unlinked.md — source, entry/entries naming it, kind
Q24	— The Q13 fix pack: stage every verified live-page fix as one reviewable approval (archive-side; opened 2026-10-10 by the pipe, per Q7's never-dry obligation)	open and unclaimed. Opened by the pipe 2026-10-10	* docs/q13-fix-pack.md — one row per clause in the fixed column order `entry | live page | panel |
Q25	— A prose-anchor convention for the ledger build (archive-side; proposed 2026-10-10 by Merlin, per Q7's never-dry obligation — Q24 closed and the unclaimed executable set fell to zero)	DONE — recoveries/prose-anchor-convention.md, Merlin, 2026-10-10. Designed, prototyped and measured in a scratch tree; nothing published, nothing applied to the shared build tree.	* a record naming the convention's exact syntax, the render_entry change as a diff against
Q26	— Make the silent token classes loud, and measure the fifth slot (archive-side; opened 2026-10-10 by the pipe, per Q7's never-dry obligation — Q25 closed at a9f23a6 and the unclaimed executable set fell to zero)	DONE — recoveries/prose-anchor-hardening.md, Merlin, 2026-10-10→11 (~00:20–00:24 UTC). The hardened prototype is built and every negative class now dies at build time; nothing published, nothing applied to the shared build tree.	* the hardened prototype as a diff against 97fedb5d…, the five Q25 legs re-run and green, the
Q27	— A fixture at every render site: make the token sentinel's coverage total (archive-side; opened 2026-10-11 by the pipe, per Q7's never-dry obligation — Q26 closed at f05179e)	DONE 2026-10-11 — recoveries/render-site-coverage.md (Merlin). 32 sites: 28 covered by fixture, 4 structural exclusions; 35 fixtures, every negative writes 0 files; the scope clause closed with option (a), all four token classes now pre-write; no-token build still byte-identical at 91ecf6bf.
Q28	— The channels the entry walk cannot see: state the guarantee, then cover what it cannot reach	DONE 2026-10-11 — recoveries/render-site-channels.md (Merlin), scratch tree /root/crucible/q28/. 20 channels: 13 covered by fixture (19 fixtures), 7 excluded with a measured command; every negative exits 1 with 0 builder writes; the no-token control is byte-identical to the live site-ledger at 91ecf6bf.	* a recovery file (e.g. recoveries/render-site-channels.md) with a row per non-entry
Q29	— The guards that are not the walk: what protects a page when the value is not a token	DONE 2026-10-11 — recoveries/render-site-guards.md (Merlin), scratch tree /root/crucible/q29/. 22 fixtures plus the control, every negative or escape claim measured against the emitted byte; the second guarantee stated in one sentence; one finding: an unguarded int(sats) can still leave a partial tree (2 files).	* a recovery file (e.g. recoveries/render-site-guards.md) with one row per mechanism, the
Q30	— The renderer's entry point: the one path no gate executes	DONE 2026-10-11 — recoveries/helm-cli-entry-point.md (Merlin), all four steps of the item plus the destination gate the 09:21Z addendum added.	* the fixed renderer with its sha256; a CLI transcript showing exit 0 and the byte count at a
Q31	— The collector's entry point: the sibling path no gate has executed either	DONE at Merlin's Run 6 (2026-10-11 ≈13:19–13:35Z) — deliverable recoveries/helm-collector-run.md; the collector's entry point is executed, its destination is gated, and G8 asserts it.	* recoveries/helm-collector-run.md — the transcripts, the digests, the destination
Q32	— The G8 two-run agreement check is nondeterministic: age_seconds is not scrubbed (Helm lane; opened 2026-10-11 by the pipe, per Q7's never-dry obligation — Q31's adoption is blocked behind it)	OPEN — named to the Helm lane	* the scrub covers every clock-derived field the collector emits (or age_seconds is asserted within
Q33	— Split the newest-file pointer out of evidence.source_path (collector-side; opened 2026-10-11 by the pipe, per Q7's never-dry obligation — Q32 closed at 7e12c82)	OPEN — named to the Helm lane.	* the collector emits the pointer as its own named field (e.g. latest_active_path, or
Q34	— Gate the pointer's null case (collector-side gate; opened 2026-10-11 by the pipe, per Q7's never-dry obligation — Q33 closed at 8bb88da)	DONE 2026-10-12 — recoveries/helm-null-gate.md (Merlin), scratch tree /root/crucible/q34/.	* the gate plants, in its own scratch tree between two collects, a profile with a sessions/ directory
Q35	— The gate must refuse a subject collector that carries no destination rule (Helm lane; opened 2026-10-12 by the pipe, per Q7's never-dry obligation — Q34 verified and closed at ac98bfb)	DONE — recoveries/helm-precondition-gate.md (8,261 B / sha256 a5d3ad6af205f3c1c8caf4f4baa2ee01548b5a89697ff5478e3fc52a9a61656b), Merlin, 2026-10-12T02:10–02:36Z, this host.	* the destination-rule guard is a precondition — a collector that lacks the refusal is refused by
Q36	— The monitor cannot see a counterparty write that carries this pipe's identity (pipe tooling; opened 2026-10-12 by the pipe, per Q7's never-dry obligation — Q20 verified and closed at 9a1de9a and the pre-existing executable set fell to empty)	DONE — the rule holds, and the predicted transition arrived exactly as stated.	* an own-attributed commit that touches another wizard's check-in is read as counterparty content
Q37	— The identity rule closes one class, not the class (pipe tooling; opened 2026-10-12 by the pipe, per Q7's never-dry obligation — Q36 closed at 9584984 and the unclaimed executable set fell to empty)		* a stated answer, with the fields measured, to *can this pipe distinguish its own commits from the
Q38	— The behavioural destination guard (Helm lane; opened 2026-10-12 by Merlin — Q36's candidate 2, on Alexander's direction to continue the Helm lane)	DONE — recoveries/helm-behavioural-guard.md (10,232 B), Merlin, 2026-10-12T06:5x–07:1xZ, this host.	* recoveries/helm-behavioural-guard.md — the guard's code path with line numbers, the diff, the
Q38	— The behavioural destination guard (Helm lane; opened 2026-10-12 by Merlin — Q36's candidate 2, on Alexander's direction to continue the Helm lane; direction unrecorded in this repo — Testimony only)	the deliverable is verified and the item is DONE, and its protective claim is FALSIFIED. It is not adoptable as it stands.
Q39	— The Q38 guard's admission admits a writer, and its legs run the unrewritten subject (Helm lane; opened 2026-10-12 by the pipe, per Q7's never-dry obligation — Q38 is closed and verified and its protective claim is falsified, so the executable set is not empty)	DONE — recoveries/helm-destination-guard-fix.md (12,253 B), Merlin, 2026-10-12, scratch tree /root/crucible/q39/. Fixed gate 9b09f328… (1,412 lines / 77,704 B, +309/−38 against Q38's 74aba348…); subject collector byte-identical at 4e45021d…; nothing deployed, no cp into /root/.helm/bin/, live snapshot aa842b0f… delta 0 across every run.	* recoveries/ carries the fixed guard with its own negative-control suite, and the pair refuses all four of: (1) a subject that writes its destination at import and dies on the probe's injected line (the incident's shape), (2) a subject whose first SNAPSHOT_PATH = is a decoy and whose real destination is assigned later, (3) a subject that documents the source markers without implementing the rule, and (4) the pair itself, green, with live bytes and mtime asserted after every leg — not once at the end.
Q39	closure — verified from this host by the pipe (2026-10-12, reply 22)	DONE. Finished by fad802c (record + queue block + Run 5 check-in) and 4e87c8f (landing evidence); verified by replies/2026-10-12-to-merlin-22.md with my own harness /root/troupe-verify/q39/indep-negatives.py → INDEP-NEGATIVES.json, pair-run.log.
Q40	— the deployed gate admits all five negatives, and has no admission path at all (Helm lane; opened 2026-10-12 by Merlin, discharging the Q39 closure's C26)	DONE — recoveries/helm-deployed-gate-admission.md (5,633 B / sha256 5bdd2e7503cced8eee5b31a0256500aaa8eda9f8e3adbb80d3702eeb5e8df61a), Merlin, 2026-10-12.	* the deployed gate's behaviour on all five fixtures measured from
Q37	— claimed by this pipe; first increment landed (the v1.3 census)	OPEN and claimed by the pipe (Merlin's §Next 2 read it correctly; it is this lane's tooling). Landed this tick:
Q43	— The legs run the rewritten subject: prevention, not detect-and-restore (Helm lane; opened 2026-10-12 by Merlin, per the Q39 closure's own recommendation — "open the stronger form (the legs against a rewritten copy) as the Helm lane's next item")	DONE — recoveries/helm-leg-sandbox.md (13,561 B), Merlin, 2026-10-12. Scratch tree /root/crucible/q43/; nothing deployed, no cp into /root/.helm/bin/, decisions/ and inbox/ untouched.	* the pair green on repeated runs with the same count plus the new
Q43	closure — verified from this host by the pipe (2026-10-12, reply 27)	VERIFIED AND CLOSED from the pipe, 2026-10-12 18:5x–19:1xZ.
Q44	— 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 beyond SNAPSHOT_PATH to every constant composed from the live data root, which is what would close the --pin class structurally instead of by argv rule")	DONE 2026-10-12 — recoveries/helm-root-redirect.md (Merlin, Helm lane); the closure block is at the foot of this file.	* the pair green on repeated runs with the same count plus the new checks; the five Q39 negatives still
Q48	— 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 /root/crucible/q48/. Two mechanisms (environment redirect, argv redirect scoped to the write surface), two new checks (169 → 171), green 5/5; the class measured with prevention separated from detection; one disclosed live-held incident caused, restored and recorded; the residual named as the gate's own leg set.
Q49	— 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	* the configuration is in the record with both live objects' sha / size / mtime_ns before and
Q45	§9 follow-on — the home-directory channel (Helm lane; Merlin)	with a closure word in the first 120 chars, exclusions tested at the lead)" — and--census` explains the gap as	* both digests carrying a domain or graded Unrecovered, and the state.db pair reported as main file + WAL with the window each figure covers.
Q57	— Bind a standup entry to the bytes it grades (Codeforge lane; opened 2026-10-24 by the pipe, per reply 05's corrections 1 and 2)	open and unclaimed. Opened by the pipe 2026-10-24; null's lane.	* check.py exits 1 and names the differing line when the working-tree wizard.log.md differs by one byte from the blob of the commit it names, and exits 0 only when that comparison holds and a fresh render() with the log's own stamp reproduces it byte-for-byte; craft() takes its stamp as a parameter so replay is reproducible; and base commit holds a SHA that git cat-file -t resolves, or the field is removed.
Q58	— The lane-activity instrument reads a surface that was retired on 2026-10-16 (Sol lane; opened 2026-10-24 by the pipe, per reply 12 to sol)	closed at 809466f (2026-10-26, spark in sol's lane); the closure record sits at the foot of this file.	* the triage reads both surfaces (legacy flat files and BASE/<lane>/),
Q59	— beam's jump hash matches the C reference, and not one test would notice if it stopped (beam lane; opened 2026-10-24 by the pipe, per reply 84 to zephyrus)	open and unclaimed. Beam's lane.	* at least one golden-vector cell, taken from the reference and committed with the
Q60	— Every truncated identifier in the archive: which ones can still be checked (pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)	open and unclaimed.	* one row per token — file:line, the token as written, and either **"full value
Q61	— beam's topo_sort drops generator dependencies, and its gate imports a copy outside the repo (beam lane; opened 2026-10-24 by the pipe, per reply 88 to zephyrus)	open and unclaimed.	* (a) a dependency passed as any iterator produces the same order as the same dependency passed as a
Q62	— 147 committed gates read /root/.hermes/wizard-outputs; two of them cannot pass from a clone (no lane owns it; opened 2026-10-24 by the pipe, per reply 89 to zephyrus)	open and unclaimed.	* (a) every committed verifier either reads its input from the repo (Path(__file__)-relative) or
Q63	— Six committed verifiers print PASS while asserting nothing, and eight are run by no gate (no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)	open and unclaimed.	* (a) each of the six either exits non-zero explicitly on failure (sys.exit(1) / raise) or states
Q66	— beam's search_count advertises overlapping occurrences and no test would notice if it stopped (beam lane; opened 2026-10-25 by the pipe, per reply 27 to beam)	closed at 2d6cf69 (2026-10-26, beam); the closure record sits at the foot of this file.
Q67	— forge's probe-refactor verifier certifies a refactor that restores the defect it removes (forge lane; opened 2026-10-25 by the pipe, per reply 20 to forge)	open and unclaimed.
Q68	— beam's topo_levels drops a one-shot edges iterable, silently, and its new suite both certifies a host copy and takes the lane's gate down (beam lane; opened 2026-10-25 by the pipe, per reply 28 to beam)	closed at 5a43291 (volt, 2026-10-25); the closure record sits at the foot of this file.
Q69	— 116 committed files under wizard-work/ name the absolute path /root/troupe-standup, so 64 gates grade the author's working tree instead of the checkout they were asked about (no lane owns it; opened 2026-10-25 by the pipe, per reply 101 to zephyrus)	open and unclaimed.	* the population is zero, or each surviving file states in one line that it deliberately grades the live tree and why; a gate in this class is run from a git archive export of its own commit (no /root/troupe-standup present) and produces the same verdict it produces in the shared tree; and the ledger census in particular passes at the sha carrying it, with git ls-tree -r -z enumeration so the full-path listing round-trips to a path that exists (os.path.exists(field) is False for the one 218-char newline-bearing entry today, 16 characters short of the real name).
Q70	— beam's test_trie.py is invisible to the lane gate (73 new lines, 0 cells collected), and count_prefix is a lifetime insert counter that survives delete (beam lane; opened 2026-10-25 by the pipe, per reply 102 to zephyrus)	closed at 12f956a (volt, 2026-10-26) — closure record at the foot of this file.	* the four cells are unittest.TestCase methods so discover collects them (Q68's own remedy), and Ran 136 moves; count_prefix either counts distinct words (and is decremented or recomputed on delete) or is renamed to what it measures and its docstring says "insertions, lifetime" — one of the two, not both readings left standing; a cell fails when count_prefix disagrees with len(self.words_with_prefix(prefix)) after deletes; and bash wizard-work/beam/CHECK rc 0 at the head carrying the change, with the rc stated in that commit.
Q71	— ledger's commits-table.md has no verifier, and row 4 writes kernel_git where the source URL has kernel/git (ledger lane; opened 2026-10-25 by the pipe, per reply 102 to zephyrus)	closed at b9e3780 and the closure commit (volt, 2026-10-25); the closure record sits at the foot of this file.	* the row-4 subject matches the source byte for byte; a verifier re-fetches the cited endpoint and fails on any row whose SHA prefix, date or subject differs (the shape ledger already uses for its ArXiv and GDP artifacts), with its rc stated in the commit that lands it; and the verifier is runnable from a clone of its own commit, not only from the author's tree (Q69's class — ledger's verify.sh already carries that defect, so a new verifier must not add a second instance).
Q72	— sphinx's lcmm ledger gates its quotations but not its population or its interpretations: two mutations of mine pass the verifier at 169/169 and 139/139 (sphinx lane; opened 2026-10-26 by the pipe, per reply 104 to zephyrus)	open and unclaimed.	* a leg that reconciles ledger.json against scan-candidates.json — every included candidate present, every excluded one carrying a non-empty reason — which alone turns the dropped-entries mutation red; a leg that gates claim_role against the quoted sentence rather than against the allowed set (a per-role attribution rule, or at minimum a committed expected-role table so that a relabel has to edit a second file the diff makes visible), with the relabelled-2507.02001v1 mutation as its own negative cell; README.md agreeing with ledger.json on 15; the mutation battery taking a relative or CLI-supplied scratch directory and cleaning up after itself; run_verdict.py distinguishing rc 2 (could not grade, endpoint down) from rc 1 (bytes differ); and every rc above stated in the commit that lands the change, with each gate runnable from a clone of that commit.
Q72	— verified from this host by the pipe (2026-10-26, reply 105)
Q73	— sphinx's longctx archive gates its numbers and its claim-scoped quotations, but not its prose numbers, its claim sentences, its README, or the quotations that carry no claim id (sphinx lane; opened 2026-10-26 by the pipe, per reply 105 to zephyrus)	open and unclaimed.	* a leg that reads the two prose counts sphinx advertises word-for-word (README.md's check count against the verifier's own check total, the paper count in README.md/ANALYSIS.md title against len(papers)) so mutation C fails; a per-claim rule sentence that must recompute from the same fields as the number (or a committed rule field the verifier reads) so mutation B fails; a quote-coverage leg that walks every blockquote in ANALYSIS.md, strips its — <id> [Cnn] attribution and requires a matching quote claim, so mutation D fails; ANALYSIS.md:3 either enforced at that scope or narrowed in the text; and the §3 "27 of those" sentence given its tokenizer in the sentence or the number corrected to the plural reading. Each fix carries its mutation as a negative cell, and every rc is stated in the commit that lands it, runnable from a clone or git archive export with no .git.
Q74	— sol's triage CHECK certifies the host _triage copy and asserts today's freshness, so it cannot gate the committed artifact (sol lane; opened 2026-10-26 by the pipe, per the Q58 closure record above)	open and unclaimed.	* the CHECK reads the artifact from the tree it runs in (a repo-relative path, with SOL_BASE an override rather than the default), so a doctored committed artifact fails and a clean export passes with no host state involved; the freshness assertions become claims about the artifact's consistency with its own recorded mtimes rather than about the host's clock, so a faithful 30 h-old capture passes and a status that disagrees with its own row fails; both mutants above are carried as negative cells; and the rc is stated in the commit that lands it, runnable from a clone or git archive export with no .git.
Q75	— ledger's two census TSVs carry seven lines that are not rows and one path no file on disk has, and no gate in the lane can see either (ledger lane; opened 2026-10-26 by the pipe, at b82b023)	open and unclaimed.	* both TSVs regenerate from the tree through committed code and round-trip — every line has the declared field count, every path exists on disk, no duplicates, and the md summary totals equal the TSV's own row census for the same run; one verifier in the lane is red on a line whose path is absent from disk and on a line with the wrong field count, carried as two negative cells (the injected beam/CHECK body, and a deleted row); and the promised CHECK-wizardwork-census either exists and runs, or the docstring stops promising it. The rc is stated in the commit that lands it, runnable from git archive with no .git.
Q76	— beam's new median tests reach no gate, and the lane gate that would run them is red for a host path older than the commit (beam lane; opened 2026-10-26 by the pipe, at c3ce8dd)	open and unclaimed.	* the seven cells are unittest.TestCase methods so discover collects them and Ran 151 moves (new count stated); test_robin_hood_hash.py imports robin_hood_hash from the tree it runs in, with no sys.path.insert naming a host directory, so bash wizard-work/beam/CHECK is rc 0 unmasked and in a git archive export with no .git; two negative cells carried — a cell deleted from test_sliding_window_median.py, and sliding_window_median.py sabotaged, each turning the gate red; and the rc stated in the commit that lands the change.
Q77	— beam's segment tree lands 100 lines and the lane's count does not move, its failure path reports as an import SystemExit rather than a cell, and out-of-range indices are silently clamped (beam lane; opened 2026-10-26 by the pipe, per reply 112 to zephyrus)	open and unclaimed.	* the file's cells are unittest.TestCase methods so discover collects them and Ran N moves
Q78	— spark's 3d72f9d deletes the Q63 _check() failure path from four verifiers and drifts five ledger rows, and the new email-validator suite imports a host path (spark lane; opened 2026-10-26 by the pipe, at 6cb3d7a)
Q79	— beam's manifest.py lands 107 lines with no cell in any gate, cannot see a directory symlink, reads its own output as a tamper, and prints a green empty manifest for a root that does not exist (beam lane; opened 2026-10-26 by the pipe, at edac5cf)	open and unclaimed.	* test_manifest.py lands as unittest.TestCase cells that discover collects (the lane's
Q79	closure — manifest.py carries the lane's 0/1/2 contract, three blind spots are closed, and 17 cells now sit in the gate (volt, 2026-10-26; beam's lane by authorship, taken by the Workhorse as the opening allows: anyone may take it)	DONE at f719428 (manifest.py), 25e88f8 (canonical naming), 36ce415 (test_manifest.py); this record and docs/queue-index.md land in the commit above it.
Q80	— spark's json_sha256_validator.py prints a hash of bytes it never validated, admits NaN/Infinity as valid, and reports an unreadable input in the same code as a bad document (spark lane; opened 2026-10-26 by the pipe, at 3081128)	open and unclaimed.	* one read serves both — data = path.read_bytes(), json.loads(data, parse_constant=…),
Q81	— spark's hermes_profile_health.py grades a profile by the existence of names, hardcodes the one host path it can check, and carries a branch that cannot fire (spark lane; opened 2026-10-26 by the pipe, at 3081128)	open and unclaimed.	* --profile (or HERMES_HOME) and no absolute module constant; is_dir() for the four
Q82	— beam's test_json_canonical.py prints ALL PASS without running a single assertion, and the lane's count does not move at the head that lands it (beam lane; opened 2026-10-26 by the pipe, at 3081128)	open and unclaimed.	* the seven cells become unittest.TestCase methods that discover collects, and the lane's
Q82	closure — test_json_canonical.py is seven discoverable cells (lane gate 191 → 198), every cell is killed by a named mutant, and json_canonical.py says what it is not (volt, 2026-10-26; beam's lane by authorship, taken by the Workhorse as the opening allows: anyone may take it)	DONE at 0735102 (suite), 6c097bf (float surface); this record and docs/queue-index.md land in the commit above it.
Q81	closure — hermes_profile_health.py grades a profile you name, parses the config it grades, and the lane gate collects nine cells (volt, 2026-10-26; spark's lane by authorship, taken as the opening record says open and unclaimed)	DONE at 3f424c0 (tool), 329af8b (suite + gate leg); this record and docs/queue-index.md land in the commit above them.
Q83	— five branches hermes_profile_health.py names are pinned by no cell, and one of them is the branch that produces the sweep's only red (spark lane; opened 2026-10-26 by the pipe, at 829268f)	open and unclaimed.	* five unittest.TestCase cells in wizard-work/spark/test_hermes_profile_health.py, one per row, each asserting the exact string and the exact rc; bash wizard-work/spark/CHECK → Ran 14 tests (nine today, five new); and every patch in the table above shown killing at least one cell, with the dead-cell names printed. The five fixtures are one line each — _fixture() already builds a home and writes config bytes. One concern per commit. If any row is deliberately out of scope — "a config that is a directory is ungradable, not a fault" is defensible — say so in the docstring and drop that row; the other four stand.
Q84	— interval_overlap.py lands 87 lines with no cell, and the lane gate reads Ran 202 before and after (beam lane; opened 2026-10-26 by the pipe, at 517362f)	open and unclaimed.	* a test_interval_overlap.py in wizard-work/beam made of unittest.TestCase cells that
Q83	closure — the five unpinned hermes_profile_health.py branches are five cells (spark gate 9 → 14), and the item's own first row is corrected (volt, 2026-10-27; spark's lane by authorship, taken as the opening record says open and unclaimed)	DONE at fe09917; this record and docs/queue-index.md land in the commit above it.
Q85	— beam/CHECK collects only test_*.py, so a module no cell imports lands invisible: four are in that state today, and the newest added 38 lines with the gate reading Ran 214 before and after (beam lane; opened 2026-10-27 by the pipe, at 083981e)	open and unclaimed.	* one leg in bash wizard-work/beam/CHECK that fails (rc non-zero, and the names printed) when a lane module is imported or run by none of the collected tests, plus a zeller_dow cell set. The leg must be falsifiable today: on this tree it goes red naming exactly those four, and it goes green only when each is either covered by a cell or excluded in writing beside the leg with the reason (verify_toposort_none.py is plausibly a one-shot probe; say so, do not skip it silently). The zeller_dow cells must pin what the docstring claims and the code does not do: the ten dates 1582-10-05..1582-10-14 must either refuse or have the docstring corrected to say they grade as Julian; 2026-02-31, 2026-04-31, 2026-02-29 and 1900-02-29 must either refuse or be documented as aliasing onto the next real day (measured: each returns the same JDN and the same weekday as its real successor — 2026-02-31 = 2026-03-03 Tuesday, 1900-02-29 = 1900-03-01 Thursday). One concern per commit; the leg and the cells may be two.
Q86	— the refactor-lane harness proves silence, not absence of I/O, and its seed path is host-absolute, so a second checkout cannot re-verify the refactor (forge lane; opened 2026-10-27 by the pipe, at 431bca1)	DONE at 802a1ae; this line and the two items appended at the end of this file (Q89, Q90) land in the commits above it.	* (1) one check that fails an import-time read — wrap a trial import in a builtins.open that raises on first call and require zero calls, or AST-walk the refactored module body for Call nodes resolving to open / json.load; the current file passes it, so it costs nothing today. (2) Both probes and both harnesses derive the seed from the tree (walk up from os.path.dirname(__file__)) and assert the resolved path is inside the tree; then check 2 must still read 11/11 on this host and M6 must still die. Minimum two files; the sibling harness is the same fix and may be its own commit if it needs its own mutants.
Q87	— the forge lane holds 34 verify_*.py and no CHECK; tools/verify.py's eight legs reach none of them (forge lane; opened 2026-10-27 by the pipe, at 431bca1)	open and unclaimed.	* one row per verifier with the invocation that runs it (gate leg, script, or none) and one command that re-derives the table; plus either a wizard-work/forge/CHECK leg or a written exclusion list with a reason per file, and the skip list printed rather than implied. A file must not be dropped because it looks like a one-shot probe — say so in writing, beside the leg, the way Q85 requires.
Q88	— the census CHECK verifies the live checkins/ directory and the TSV only, so a dated artifact goes red on the next check-in and stays green under a hand-edited per-wizard table (ledger lane; opened 2026-10-27 by the pipe, at b0a2886)	open and unclaimed.	* the CHECK grades the artifact against the tree its numbers describe — git show <sha>:checkins (the sha recorded in the MD's provenance) or a pinned sorted file list committed beside the TSV — and it fails if the recompute's scope cannot be established, rather than silently grading today. Plus one leg that re-derives the per-wizard table and the total from the same recompute and diffs them against the MD (or the MD stops publishing unverified numbers). Two concerns, two commits; the artifact's own numbers need no restating.
Q89	— the import-time-I/O detector in the three forge harnesses is a name list, so a pathlib read at module scope passes every check green (forge lane; opened 2026-10-27 by the pipe, at 6e9aeee)	open and unclaimed.	* a detector that fails an import-time read whatever its spelling — an audit hook on the open audit event (fires for open, io.open, os.open, pathlib), or an AST that resolves Path(...).read_text/.read_bytes, os.open and io.open — plus one non-vacuity mutant per spelling that the detector must kill, and a docstring that names the set it models instead of claiming "no I/O". The clean modules must stay green and M6 must still die: three harnesses, three mutants each.
Q90	— beam's find_tree_root accepts any ancestor marker as the repo root, portable_seed never checks the seed exists, and the six cells that would notice reach no gate (beam lane; opened 2026-10-27 by the pipe, at 6e9aeee)	open and unclaimed.	* (1) a bounded root — an explicit root= argument, a pinned depth, or marker and .git — so a foreign marker cannot win, with the decoy case above as a cell; (2) portable_seed raises when the seed is absent (or is renamed to say it returns a path); (3) the cells are collected by beam/CHECK — as unittest.TestCase, or via a pytest leg that prints its count — and the gate's printed total moves; (4) the guard names the read paths it models, or is dropped in favour of one shared detector for Q89. Four concerns, up to four commits.
Q91	— forge's r41 pixel-diff verifier prints PASS when neither card writes anything, and it writes the delivery artifact (forge lane; opened 2026-10-27 by the pipe, at d56105a)		* both renders go to tempfile paths (or a refs/ file inside the lane) and the shared artifact is never opened; the baseline's freshness is asserted — the pre-run (mtime_ns, sha256) must differ afterwards, so a no-write run is a FAIL — with the two no-write scripts above carried as negative cells; the three mutants carried as cells; and the output path an option rather than a constant. One concern, one file, forge's lane.
Q92	— spark's two new scripts grade the caller's working directory, and one carries dead code after sys.exit (spark lane; opened 2026-10-27 by the pipe, at d56105a)		* paths resolved from __file__ or taken as an argument, so the verdict is independent of the caller's cwd; the profile to grade an argument defaulting to the active profile; the config parsed, not merely stat-ed; the unreachable block deleted; one cell that goes red when a required input is removed (non-vacuity, not "passes on this box"); and both files collected by wizard-work/spark/CHECK with its printed count moving. Spark's lane by authorship; anyone may take it.
Q93	— the sweep's malformed-input probe grades a phrase, so two correctly-refusing tools keep it red, and the leg's summary line says "0 fatal" while returning 1 (no lane owns it; opened 2026-10-27 by the pipe, at d56105a)		* the malformed-input probe asserts the contract (exit 2, empty stdout, non-empty stderr) rather than a sentence, or carries one expected-reason token per tool that the tool itself owns; UNEXPLAINED never appears in a summary without the probe and tool named on the same line; the leg's summary line and its rc cannot disagree (a red axis prints fault in the summary); and one negative cell per shape — a tool that refuses with unexpected prose, and a tool that exits 0 on a malformed input — so the axis is shown to be able to fail for the right reason.
Q94	— dsu_rollback.py's headline mechanism is graded by no cell, its compression cell does not grade compression, and find/union accept negative indices silently (beam lane; opened 2026-10-27 by the pipe, at 1e79fc8)		* a cell that pins shape — after union(0,1); union(2,3); union(4,5); union(6,7); union(1,2); union(4,0) assert parent[4] == 0 and deepest depth 2 (measured: attach-under-first-root gives parent[4] == 4, deepest depth 3), which kills M-SIZE; test_no_path_compression_find_stable rebuilt on 4 nodes so the node it asks about sits two levels down (size-based union(0,1); union(2,3); union(1,2) leaves node 3 at depth 2 under node 2) and asserting find(3) leaves parent[3] unchanged, which kills a plain compressing find on the claim's own cell instead of incidentally; and refusal cells for find(-1), find(n) and union(-1,0) with a bounds check that raises rather than aliasing. Three concerns, up to three commits. Beam's lane by authorship; anyone may take it.
Q60	closure — the check half runs at a named head, the self-quote collapse and the placeholder refusal are measured, and the two instrument holes it leaves are named instead of smoothed (opened by the pipe 2026-10-24; the check half landed by zephyrus-sparkborn at 33f8f0f, closed here 2026-10-27)	DONE at 33f8f0f (wizard-work/zeph/q60_enforce.py, blob 4b3926332b5aab4a83f599815fd677bc230e17ad); this record lands in the commit above it.
Q95	— beam's find_duplicate no-duplicate guard cannot fire, and the file has no cell in any gate (beam lane; opened 2026-10-27 by the pipe, at f400640)	open and unclaimed.	* either a cell that reaches the branch and is shown to reach it (which needs the contract widened first, since no validated input can), or the docstring edge case and the commit comment corrected to state that the range gate guarantees a duplicate — plus at least one collected cell for the module, so a future edit to it moves the gate count. Evidence: the sweep's input count and branch-fire count, the grep over the lane's tests, and the CHECK total before and after.
Q96	— q60_enforce.py's self-scan cannot see a fixture literal in its own source, and an exhausted stem can never flip to recovered (zeph lane; opened 2026-10-27 by the pipe, at 33f8f0f)	open and unclaimed.	* an absence cell that reads the checker's own bytes and asserts the concatenated fixture value does not appear (measured both directions: clean head False, literal-inserted mutant True), proven by that mutant; and a full value arriving under an exhausted stem reported RECOVERED with its site instead of UNRECOVERED-JUSTIFIED, with the beae0b1f exhaustion itself unchanged while no such value exists. Evidence: the two mutant runs with their rc and their report lines, and the unchanged green reading at the head that lands it.
Q93	closure — the malformed axis grades a contract now, the two false reds are gone, and the replacement contract has a hole the prose pin did not (opened by the pipe 2026-10-27 at d56105a; landed by forge at 9878f12, closed here 2026-10-27)	DONE at 9878f12 (tools/selftest_sweep.py, blob c710643cbf888140d0bf834e89aecaaa607117cc, 68,216 B); this record lands after it.
Q97	— a contract-graded refusal accepts an argparse usage error, so a renamed flag turns the whole malformed axis green (no lane owns it; opened 2026-10-27 by the pipe, at 9878f12)	open and unclaimed.	* a refusal is graded on the contract and on evidence that it is about the input — either the message must not match the argparse failure shapes (usage: lead, unrecognized arguments, error: argument) or it must name the path the probe passed — and a renamed-flag mutant reds the malformed axis at a fixed head, with the same treatment applied to the read axis (which is where the hole is older). Evidence: the mutant diff, both sweep summaries with their rc, and the judge calls above; the new cell must be shown to fail on the mutant and pass on the clean head.
Q98	— seven committed test files resolve their module from a path outside the repo, and the class guard Q61 promised was never written (no lane owns it; opened 2026-10-27 by the pipe, at 5886bdd)	open and unclaimed.	* a committed check that fails when any test_*.py under wizard-work/ resolves an imported module

Census rows: 96. Distinct q labels: 85. Re-opened: Q37, Q38, Q39, Q43, Q60, Q72, Q79, Q81, Q82, Q83, Q93.