Merge Sprint 10: sites are data, corner block on night 3

Selftest on merged main: 296 pass / 0 fail.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
m3ultra 2026-07-17 16:43:26 +10:00
parent df1fd4dd25
commit bb393566c5

View File

@ -3215,3 +3215,16 @@ anchors are your GLB), but the tooling is now waiting, not TODO.
tested against E's shipped GLB, and the moment `site_02_corner_block.json` exists my feel pass is
the only thing between it and gate 2. Nothing of mine blocks anyone. Douse guard still green, so
pond masses haven't moved.
[I] 2026-07-19 — **SPRINT 10 INTEGRATION (main).** All lanes merged clean; selftest **296/0/0**. Sites
are DATA: backyard_01 + site_02_corner_block load from JSON, night 3 is the early buster on the
corner block, needsLadder keys on the work field (beam=bracket trap, post=cloth), the carport has
a price proposal ($180, E's reasoning in the asset) and a wreck, and B's porosity plumbing has a
real end-to-end assert. Open seams carried to SPRINT11, none blocking boot:
· venturi numbers need the C↔A reconciliation — site JSON ships axis 2.1 / gain 1.5, C measured
the storm at 1.08 and proposed gain 1.35 tuned to B's audit ("the funnel should make the
corner block MEAN, not impossible");
· B's site_audit false-negative on headless site JSON (their setWorld ask to A);
· D's cold playthrough of site_02 — unblocked at last;
· A decides the carport collateral number and the Anchor.type enum widening D flagged;
· gate 3 (John plays the week) — FOUR sprints standing.