t27b overnight loop 2026-10-05: 100% coverage, broken specs, reference denominator #8520

Re-filed from #6434. An attempt claimed that issue on 2026-10-07 and left an empty branch, and a dispatch row that has spent its retry ceiling keeps its issue for good - so no bee could take it again, however much the brief improved. The work below is carried over unchanged.

Refs #6063

Overnight improvement loop started by the owner on 2026-10-05 ("merge all t27b PRs yourself, go to 100%, fix every broken spec"). A 15-minute in-session cron runs it; the ledger is ~/.local/state/t27b-queen/ledger.md.

Where it starts (lab run at master 03362c1)

• The reference path (t27c gen-zig + zig test) passes 722 of the 1259 specs in this repo.
• Among those 722: t27b passes 379 with tests checked, and 281 have no tests at all (vacuous pass). 62 are still blocked by t27b. Mismatch 0.
• The other 534 specs fail the reference path itself (509 blocked, 25 fail), so they sit outside the denominator.
• The SPECS catalog at app.t27.ai/game/specs covers 1778 specs from 14 repos. It shows 176 Broken and 232 Warnings. It was built from a vendored WASM at bf7d8ee. 23 of the Broken entries are intentional negative fixtures.

Plan (one lane per row; each lane files its own issue and PR)

• t27b lane: tuples (16 files)
• t27b lane: f32 (7 files)
• t27b lane: tail blockers (undefined, std.*, method calls, assign, alias, anonymous struct, void)
• Broken in gHashTag/t27: re-measure with master t27c; fix the specs; show negative fixtures as expected-fail in the catalog
• Broken in other repos (trinity-fpga, tt-trinity-gamma, turbobaby-user-bot, tt-trinity-euler, trios, tt-trinity-phi, trinity)
• t27c reference denominator: fix(t27c): read a dotted module name and use path whole #6102, then the largest gen-zig failure classes (201 undeclared identifier, gen-zig: brace invariants and tail expressions become 'value ignored' (16 specs do not compile) #6315, t27c gen: open slice x[i..] emitted as x[i]; &[_]T{...} emitted as &.{ _ } #6250, t27c gen (Zig): test bindings shadow module vars, redeclare locals, and inherit param renames #6295)
• tri: a catalog-health command so Broken/Warn counts come from one command, not a hand-written script
• Steward self-heal: a silent ledger is an anomaly (skill rows Q44 and Q45)
• Vacuous passes: 281 reference-passing specs have no test. An owner decision is pending on whether they count.

Weak points found

1. The steward was dead from 06:04Z to 14:35Z with no alarm. The claim pid was gone and no ticks ran.
2. Q37 (one lower.rs lane at a time) serialised all coverage work. This loop moves new lowering into per-lane submodules instead.
3. 42% of the corpus fails the reference itself, so "100% of reference passes" understates the work.
4. The SPECS catalog is built by a stale WASM compiler and counts intentional negative fixtures as Broken.

🤖 Generated with Claude Code

Boundary

• cli/t27b/src/lower.rs

User Scenarios

• Given the overnight loop runs against master 03362c1, when the tuples lane executes, then t27b passes all 16 tuple-related specs with tests checked
• Given the reference path passes 722 specs, when the loop completes the tuples lane, then the t27b pass count increases from 379 toward the reference denominator without new mismatches

Requirements

• FR-001: The tuples lane MUST lower tuple types and expressions in cli/t27b/src/lower.rs without breaking the 379 currently passing specs
• FR-002: The 16 tuple-related spec files MUST compile via t27c gen-zig and pass zig test when the lane completes
• FR-003: The lane MUST execute as an independent submodule so Q37 serialisation no longer blocks other lanes

Success Criteria

• zig test cli/t27b exits 0 with the 16 tuple specs added to the passing set
• The ledger at ~/.local/state/t27b-queen/ledger.md shows tuples lane completed with 0 new mismatches
• cli/t27b/src/lower.rs contains the new tuple lowering submodule and no regression in the existing 379 passing specs

The instruments

Every one of these reads and prints; none of them writes. Run them from the repository root, with <spec> replaced by the file in ## Boundary:

.t27 is not Rust and not Zig, and a bee fluent in either writes one by
accident. Measured 2026-09-20: a bee filled eight bodies in
specs/file/watcher.t27 with return Ok(());, Err(FileError::WatcherNotFound)
and for i in 0..watchers.length. The parse ratchet refused the whole file --
Unexpected token in expression: RParen, line 123 -- and a spec that does not
parse generates nothing, so every test it already carried stopped running.

At the top level the parser accepts exactly these eight forms, with an optional
pub, and no others:

const   var   fn   enum   struct   test   invariant   bench

There is no trait, no impl, no type X = ..., no generics, no macro. What
a bee reaches for from another language, and what happens:

• Rust's result sugar (Ok(()), Err(E::V), ?) is not a construct here.
• Rust macros (println!, format!, vec!) are not constructs here.
• A range loop (for i in 0..n) is Rust and Zig, not this language.
• Zig builtins (catch unreachable, @intCast, @constCast) are not constructs here.
• Cross-module reuse (use other::fn;) parses and then generates a comment and an unqualified call, so the Zig fails with use of undeclared identifier (use a::b; generates no import, so no spec can reuse a function from another spec #4298). It does not work yet.

t27c parse <spec> answers in one line whether what you wrote is the language.
Run it before you report, every time.

• t27c spec-status <spec> - the compiler's one-word verdict: IMPLEMENTED, PARTIAL, UNWRITTEN, NOPARSE, NOFN. Exit code is 0 whatever it says, so read the word.
• t27c symbols <spec> - every name the file declares, with its kind. Answers "does this already exist here?" before you add it.
• t27c outline <spec> - per function: its locals, what it calls, what it returns. The contract you are implementing against.
• t27c coverage <spec> - which functions have a test and which do not. The issue asks for tests; this is how you check you wrote them.
• t27c lint <spec> - style and shape warnings. It OVER-REPORTS has no test or invariant: measured 2026-09-20 over 60 specs it printed 677 of those where coverage found 190 untested functions, disagreeing on 59 of the 60 - it warns about bit_to_trit_pair in specs/base/ternary_encoding.t27, which test bit_to_trit_pair_zero calls on line 249. Read it as a hint; coverage is the answer.
• t27c typecheck <spec> - types, before generation. Prints Typecheck OK (0 errors, 0 warnings) or the errors.
• t27c test-report <spec> - builds this spec and runs its own tests, which is what the oracle does. BLOCKED means the generated Zig does not compile, with the error beside it.
• python3 tools/dupe_scan.py --name <function> - where that function already lives, if it does. 576 of 4021 bodies here are byte-identical copies.

The rest of the toolbelt is in docs/BEE_TOOLBELT.md.