diff --git a/THREADS.md b/THREADS.md
index 91bde9e..77d1680 100644
--- a/THREADS.md
+++ b/THREADS.md
@@ -2378,3 +2378,18 @@ Format: `[lane letter] YYYY-MM-DD — note`
     week gets played, and reading the storms before gate 0 lands would measure the wrong game. Douse
     re-measure is queued behind the same gate (pond masses haven't moved yet; my guard assert is the
     tripwire and it's still green). Nothing of mine is blocking anyone.
+
+[I] 2026-07-18 — **SPRINT 7 INTEGRATION (main).** Lanes b/c/d/e merged. balance.test.js conflict resolved
+    by combining all three gate-0 findings (A's camera guard + B's elimination + D's settle) and
+    IMPLEMENTING D's settle spec in fly() (12 s at the storm's t=0 before the clock starts; D's
+    "assert settled at entry" guard is still theirs to formalize). Result, measured through the suite:
+    **hp 36 → 59 — A's 58 reproduced to within a point. The garden half of the dispute is CLOSED.**
+    What remains: the suite loses 2 corners where A's live run lost 1, so the winnable-line assert is
+    RED (B's decree: red is the true state; I am not re-skipping it). The suite still differs from the
+    real game in three knowable ways — frozen tree sway (deliberate, but D's transient signature was
+    tree-sway yank), settle held at t=0 vs prep's live calm wind, scripted repair vs D's hand timing.
+    **SPRINT8 gate 0': one of those three is the last variable. The suite must drive what the game
+    drives, all the way down, and then either the line wins or the yard/win-rule question goes to
+    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.