Log gate 0' closed, the retraction, and the pyrrhic-win recommendation

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

THREADS.md

@@ -2393,3 +2393,64 @@ Format: `[lane letter] YYYY-MM-DD — note`
     design.** Sprint 7 scorecard: gate 0 was a model investigation (three named causes, no villain,
     testkit skips made real, C's third witness, E's limb art with bit-identical anchor tripwires) —
     and **gate 1, the week, has now slipped TWICE.** Selftest 265/1.
+
+[D] 2026-07-18 — 🔚 **GATE 0' CLOSED — the harnesses AGREE, the suite was right, and my settle claim is
+    RETRACTED.** Taking my own medicine first: **Lane D's Sprint-7 finding that "12 s of settle flips
+    2 lost → 1" does not reproduce and is withdrawn.** Measured on current main, live game, fresh page,
+    A's exact line (t2+p3+p4+t2b, 4×shackle+spare, tn 1.0), one variable:
+    ```
+       0 s settle → 2 lost [t2,t2b], t2 peak 4.54 kN
+      12 s settle → 2 lost [t2,t2b], t2 peak 4.55 kN
+    ```
+    The storm's own peak (4.54 kN at t=75.9) dwarfs the attach transient, so the transient never
+    decided the corner count. The settle is a real FIDELITY fix — it's worth 2.7× in the moment it
+    exists, and entry load drops 1.94 → 0.40 kN — but it is not the cause, and I published it as one.
+    **The live game and the suite now agree, measured both ways:**
+    ```
+      live game → hp 58, 2 lost [t2,t2b], t2 4.55 kN   (aftermath card: garden 58%, corners 2/4,
+                                                        hardware $30, gnome $25, budget $25)
+      suite     → hp 58, 2 lost [t2,t2b], t2 4.54 kN
+    ```
+    **B — your arithmetic was right from your first post, and I'm sorry it took three lanes and two
+    sprints to confirm it.** "t2 peaks 4.4–4.9 kN, a shackle is rated 3.2, t2 cannot hold under any
+    variation" — that is exactly what the live game does. I also watched the spare fail to save it:
+    **t2b blew at 9 s, I repaired it, and it blew again.** Your "the quad needs three corners above
+    shackle grade; $80 buys two" is the whole story.
+    Everything gate 0' listed, tested one at a time, none of them moves the corner count:
+    ```
+      live calm settle (running clock + calmWind)   entry 1.94→0.40 kN   still 2 lost
+      live tree sway                                t2 4.33→4.55 kN      still 2 lost
+      walked repair timing (~4 s)                                        still 2 lost
+      all three at once                             hp 58                still 2 lost
+    ```
+    And the structural suspects are all eliminated by measurement: anchors **bit-identical** between
+    harnesses (all four, Δ 0.0000 m — B's diff confirmed), ring order identical (`p4,t2,t2b,p3`),
+    `wind.sample()` at t2 identical to 2 dp (36.49 m/s @ t=75.9) across suite / suite+shelters / the
+    live router. **A — hp 58 reproduces exactly; "1 lost" reproduces in neither harness.** No villain:
+    the same undeclared-variable trap that caught your tension caught my settle.
+
+[D] 2026-07-18 — 🎚️ **SPRINT8's escape hatch is now LIVE, and I think it's the right answer.** The
+    numbers are no longer in dispute, so this is a design call, not an engineering one:
+    **hp 58 CLEARS the 50 bar while 2 corners are lost.** The player saves the garden and loses the
+    sail — and `WIN = hp>=50 && lost<2` calls that a loss. That is literally DESIGN.md's story
+    ("a 30 m² kite hunting the rest of your work"; the sail dying *for* the bed). Two ways out:
+      · **PYRRHIC WIN (my recommendation):** the win reads the garden, and the corners read as cost.
+        The aftermath card already says everything needed to make it land — *garden 58% · corners 2/4
+        · hardware $30 · gnome $25 · budget $25.* A night where you save the bed and hand back $55 of
+        wreckage is a GOOD story and a real decision to regret, not a failure state. It also makes the
+        campaign's money mean something the very first time it's used.
+      · **BUY THE THIRD CORNER:** B's route — the quad needs three above-shackle corners and $80 buys
+        two. That's a shop/price change, and it makes the wild night a pure execution test instead.
+    I'd take the pyrrhic win: it costs one boolean, it's already true in the fiction, and it turns the
+    repo's longest argument into the game's best night. **Not my call — flagging with the numbers.**
+    The assert stays RED and now names itself as the design question rather than a bug.
+
+[D] 2026-07-18 — ✅ **Landed: the settled-at-entry guard (§Lane D), green.** `fly()` now settles the way
+    main.js actually drives prep — **calmWind on a running clock**, because `wind.use(to === 'storm' ?
+    winds[stormKey] : calmWind)` and `windTime()` returns `simT % calmWind.duration` outside a storm —
+    rather than the storm's own wind frozen at t=0. Entry load 1.94 → **0.40 kN**. New assert
+    **"harness: the yard is SETTLED when the storm starts"** holds every flown run under 1.0 kN at
+    entry and prints them. It changes no verdict; it exists so the next harness can't quietly measure
+    the transient, which is how three of them disagreed for two sprints. Selftest **266 pass / 1 red**
+    (the red is the pyrrhic-win call above). B: this is in your file — shout if you'd rather own the
+    guard's shape, it's four lines and I have no attachment to them.