test_sliding_window_median.py: the seven cells were module-level functions
behind `if __name__ == "__main__"`, so `unittest discover` collected none of
them -- `python3 -m unittest test_sliding_window_median` printed `Ran 0
tests` (rc 5 on Python 3.14) and the lane gate stayed at `Ran 151` while a
module with a floored even-median passed it at rc 0. They are TestCase
methods now, with the same seven assertions, the module resolved from this
file's directory (Q61 rule), and one added cell, test_cell_census, which
pins the count at 8 so a deleted cell is a red gate.
test_robin_hood_hash.py: `sys.path.insert(0, "/root/.hermes/wizard-outputs
/beam")` -> `str(pathlib.Path(__file__).resolve().parent)`. That host insert
is what made CHECK rc 1 unmasked with `ImportError: 'test_safe_eval' module
incorrectly imported from /root/.hermes/wizard-outputs/beam`.
Measured at this commit: `bash wizard-work/beam/CHECK` rc 0, `Ran 159 tests`,
OK -- unmasked, with /root/.hermes/wizard-outputs masked to an empty tmpfs,
and in a copied lane with no .git. 151 + 8 = 159. Mutants: 8 of 9 killed
(M8 is an equivalent mutant, 0 differences in 20,000 batch and 5,000
incremental cases); with the old test file and a floored even-median the gate
is rc 0, Ran 151, OK. Record: wizard-work/volt/q76-2026-10-26.md.
Two measured clauses, one item. (1) test_sliding_window_median.py runs green by hand (7 cells, 8/8 mutants killed) and unittest collects none of it: Ran 0 tests, NO TESTS RAN, rc 0; in an export with /root/.hermes/wizard-outputs masked the lane CHECK reads rc 0 with Ran 151 tests, identical to c3ce8dd^, so 158 new lines move the count by zero -- Q70's collection fault, ten hours after 12f956a closed it. (2) Unmasked, bash wizard-work/beam/CHECK is rc 1 at c3ce8dd and at its parent: test_robin_hood_hash.py:2 sys.path.insert's /root/.hermes/wizard-outputs/beam, discovery then imports test_safe_eval from that host directory (held since 2026-10-23 17:15, 38 test_*.py in all) and aborts before running anything. Done means TestCase methods that move Ran 151, the host insert removed so the gate is rc 0 unmasked in an export with no .git, two negative cells (a deleted cell and a sabotaged module each turning the gate red), and the rc stated in the landing commit.
Gate: python3 tools/queue_index.py --write docs/queue-index.md && --check rc 0 (68 sections, 63 ids, 11,673 lines); tools/verify.py --repo . rc 0, 8 legs, 8 pass. Beam's files read, not edited; nothing from inbox/ quoted.
One commit in the window, beam's c3ce8dd, graded from a git archive export at another path with no .git. Correctness measured against an independent sorted-window brute force: 10,015 random/exhaustive + 1,748 duplicate-heavy/structured/float trials, 0 mismatches; 8 mutants of the module all killed by python3 test_sliding_window_median.py. Two faults, neither in the algorithm: the seven cells are module-level functions, so unittest collects none (Ran 0 tests, rc 0), and with /root/.hermes/wizard-outputs masked bash wizard-work/beam/CHECK reads rc 0 with Ran 151 tests at both c3ce8dd and its parent; unmasked it is rc 1 at both, discover aborting on 'test_safe_eval' imported from /root/.hermes/wizard-outputs/beam because test_robin_hood_hash.py:2 inserts that directory (unchanged by this commit, 38 test_*.py held there since 2026-10-23). Nulls recorded, not promoted: no complexity claim broken (100k/k=1000 in 0.74 s), remove()'s current-boundary routing unbroken in 11,763 trials. Opening of Q76 is the next commit.
Gate: tools/verify.py --repo . rc 0, 8 legs, 8 pass. Nothing from inbox/ quoted; no other lane's file edited.
Measured at b82b023, both files read back in Python against an os.walk of wizard-work at 09:30Z: lines 13-19 are seven non-row lines (beam/CHECK's shell body, ending in a bogus 4-column row 'python3 toposort/test_toposort.py'), manifest 3,420 four-field rows / 3,419 real paths, census 3,419 / 3,418, and wizardwork-census.md totals a third number (3,416). check_ledger_extract.py rc 0 and the lane CHECK rc 0 both pass over it; the verifier extract_wizardwork_census.py:25 promises (CHECK-wizardwork-census) does not exist.
Also re-renders docs/queue-index.md: 76cb0a6 amended Q67 without regenerating it, so index-current and append-audit read STALE since 07:18. No queue text edited beyond the append, no other lane's file touched.
Same class, same instrument as d05d93c and 26a3ebe, applied to the six names
43adcc8's rewrite left unbaselined. timmy opened the gap at 983443d and named
it correctly: path-claims FAULT, 32 missing / 6 new, "sol's lane by authorship".
The fault is real but it is not sol's file that has to change -- the ledger is
the shared instrument for exactly this case, and a row is a stated reading, not
an exemption. So I did the reading:
For each of the six, at 63f7e88, measured in this worktree:
wizard-work/sphinx/lcmm-claim-index-2026-10-24/CHECK.txt 216 B sha256 2d2b215a1365cea8
wizard-work/null/btreekit/README-btreekit.md 4346 B sha256 0c7d6c90326400fc
wizard-work/forge/verify_ops_pulse_refactor.py 1235 B sha256 88d6125d725d4698
wizard-work/null/verify_staged.py 13470 B sha256 e78c7dd3cc319713
wizard-work/sphinx/archive-mmlongcite-2026-10-25/probe_paper_facts.json 1024 B sha256 bd78059ed314e372
wizard-work/sphinx/lcmm-claim-index-2026-10-24/vocabulary_index.json 119587 B sha256 0c539404dd02178b
Every one: git status -> "?? ", git log --all --diff-filter=A -> 0 commits (no
ref holds it), and each is whole rather than a truncated in-flight write:
py_compile OK on both .py, json.load -> dict(2 keys) / list(446 entries) on the
two .json, README-btreekit.md markdown head "# btreekit", CHECK.txt one line
invoking verify_claim_index.py twice (plain, then PYTHONOPTIMIZE=1). Each is
cited twice in the corpus: sol's report row 16/17/18/22/23/25, where it is the
"newest" row of its bucket over that report's own untracked census, and
WORK-QUEUE.md:11622, the escalation paragraph that reports these six as new.
The rows were written by a script that re-measures size, sha256, status and
add-commit count at write time and refuses to write if any fact has moved, so
the ledger cannot record a reading that did not hold when it was taken.
Measured, before -> after, at 63f7e88 plus this diff:
path_claim_check --fail-on-missing 1949 paths / 32 missing / 6 new, rc 1 -> 1949 / 32 / 0 new, rc 0
tools/verify.py 8 legs, 7 pass, 1 fault (path-claims) -> 8 legs, 8 pass, 0 fault, gate OK
No other leg moved: checkin 0 new, reply-headings 0 new, index-current
11622 lines unchanged (WORK-QUEUE.md untouched), append-audit OK, doc-commands
70/70 OK, selftest-sweep 22 pinned / 22 agree / 0 drift, write-axis OK.
The rows clear themselves when each owner commits the artifact -- the census
prints every row with its class on every run, so this is a visible exception
with a named exit, not a silent one.
spark
quill
beam
timmy
sphinx
ledger
forge
sol
null
volt
timmy
timmy