diff --git a/docs/LANES/LANE_F_NOTES.md b/docs/LANES/LANE_F_NOTES.md index 7c2a57f..6121200 100644 --- a/docs/LANES/LANE_F_NOTES.md +++ b/docs/LANES/LANE_F_NOTES.md @@ -1373,3 +1373,43 @@ Attempts 1–3 were also never winnable: the shops faced backwards the whole tim at a wall and tuning the geometry.** The measurement that would have found it in five minutes — compare the two conventions against each other — is the one nobody ran for nine rounds, F included, right up to the vacuous 72/72 F nearly filed as "B is wrong". + +--- + +## 28. Round 28 — v5.1 THE SPIKE AND THE SWEEP. **The sweep landed. The spike did not reach the game.** + +### ⚠ F's pose gate has NO SUBJECT — SKIPPED with the reason, per the law +The brief: *"New-clip figure checks (lean/look poses through the scale gate), a bookmark spot-check +(leaning peds in old frames)."* **There are no new poses in the game, so there is nothing to check:** +- **`lean` does not exist.** E measured it rather than assumed it — the stash's 34 clips contain no + lean, and `find -iname "*lean*"` across ultra returns nothing. The brief and the kickoff both named it + as already-cached; **the premise was half wrong**, and E found it the only way anyone ever finds these: + by looking instead of trusting the list. +- **`look.glb` is shipped, verified, published — and NOTHING BINDS IT.** `loadPedFleet()` loads + `walk.glb`, `idle.glb`, and `sit` (gated). No `look`. E's own handoff said it plainly: *"→ D: it's + ready. Gate it behind an opt the way rigs.js gates sit."* **D's entire R28 commit is + `LANE_D_NOTES.md` — 48 lines, docs only.** The run order said *"When E's clips land: D (#1 wiring)"*; + the log says **D committed BEFORE E shipped** (`afad68b` precedes `640bdbb`). Nobody was careless — + the wave order was, and the file on disk looks exactly like a delivered spike from every angle except + the one that matters. + +**The R17/R23 pattern, fifth appearance, and the cheapest one yet to have missed**: an asset on disk, +verified, published to a public depot, sha1-checked by fetching the bytes BACK — and no consumer. Every +check E ran was real and passed. None of them could see that nothing loads it. *A gate on the artifact +cannot see the wire.* + +### So: v5.1 SHIPS, and it does not claim the spike +Nothing is broken — an unbound clip is inert, the game is unchanged and correct. This is not R18's +"known breach"; it is an **unfinished item**, and holding a polish tag over an inert file would be +precious. **What ships is the sweep, and the tag says exactly that:** +- **C's `audioEmitter`** — the till rings from the counter, the bed from the stage. C's own idea, parked + since R7, and C found its own v3.0 note had specified it wrong on both halves (*"the panner was + inert"*). +- **Two items KILLED with the measurement** — B's awning ripple and D's instrument LOD, the oldest tri + item on the books. They don't leave the backlog "deferred"; they leave it **gone**, with the number + that killed them. *A backlog that only grows is a backlog nobody measures.* +- **`look.glb`** — staged on the depot, and honestly described as staged. + +**Filed for R29 (D, one opt):** `rigs.js` gains `look` the way it gates `sit`; F passes it from the shell. +Then the pose gate has a subject and F will run it. **v6 has not begun in-game — the tag must not say it +has.**