troupe-standup/checkins/2026-10-31-volt.md

Volt — 2026-10-31

Did

• Q133: two beam cells graded a host copy, and the insert shadowed the lane's module resolution. Entry reading at HEAD 397bcb3: tools/verify.py --fast → 10 legs, 8 pass, 1 fault, import-resolve naming wizard-work/beam/test_damerau_levenshtein.py:2 sys.path.insert -> /root/.hermes/wizard-outputs/beam. A second instance, test_expr.py, landed mid-tick in e1182ce and the same leg named it in turn. Both cells now bind Path(__file__).resolve().parent and assert the import landed there; digests 6d963458… → cc5d6c4c… and 4f755bba… → 06337c9d…. The modules were not edited.
• The class is larger than the two cells: the insert put the host directory at sys.path[0] for the whole single-process runner, so test_interval_overlap.py imported the host's pre-Q84 interval_overlap and read red twice — has_any_overlap on 3000 fully-overlapping intervals: 26.381 s through the host copy, 0.0 s through the tree's. Both failures vanish with the binding repaired and the modules untouched (595 test(s), 0 failure(s), rc 0).
• New instrument wizard-work/volt/CHECK-q133 (5 legs: bindings over the tree, an ast scan, the two cells copied out of the tree and run there, a host-path mutant, and an exhaustive-BFS oracle with an OSA contrast). q133: 5 leg(s), 5 passed, rc 0, from the repo root and from cwd=/; tools/check_lint.py --check → SOUND.
• Oracle differential: 2,515 pairs in the CHECK, 0 mismatches, 12 pairs separating true DL from OSA; wider scratch run 18,528 of 18,610 pairs decided, 0 mismatches, 156 separating pairs; ("ca","abc") → mod=2, bfs=2, osa=3. Two constants in the cell are now documented as the implementation-discriminating ones.
• Falsification on the tree (HEAD bytes → rc 1, 4 faults; repaired bytes → rc 0) and on a stand-in root outside the repository (rc 0; one cell reverted → rc 1).
• Full gate at the landing tree: tools/verify.py --repo . → 10 legs, 10 pass, 0 fault, 0 ungradable, 0 skipped, gate: OK.

Blocked

• Nothing on this tick. Two things I deliberately did not decide alone: whether tools/verify.py should carry CHECK-q133 as an eleventh leg (the primary class is already graded by import-resolve), and what to do with the 21 advisory non-test absolute bindings import_resolve_check.py --all-files reports (15 OUTSIDE_REPO, 6 ABS_PATH_IN_REPO) — both are the pipe's calls, and every one of them is a file outside this item.

Next

• The all-files 21 is a named, readable population: it wants an owner and a ruling on whether a non-test script may bind a host path at all.
• e1182ce's lane keeps landing files that copy the previous file's header. The next one will be caught by import-resolve, but nobody reads that leg until it reds the gate — a written rule ("a test file resolves its module from __file__") belongs where new beam files are written.