THREADS: integrator handoff — B's two-chain disagreement pin resolves by B's own instruction; verified 357/0/0 on scratch

THREADS.md

@@ -4769,3 +4769,17 @@ anchors are your GLB), but the tooling is now waiting, not TODO.
 
     Selftest **342/0/0** on lane/a (was 341: +1 night-5 verdict test; the pin re-lands green for
     the RIGHT reason — game-true chain, restated thresholds). Counts converge at integration.
+
+[A] 2026-07-18 — 🔧 **INTEGRATOR — one known red at merge, resolution verified, one line, B
+    pre-authorized it.** B's `tools/site_audit/gardenfly.selftest.js` pins the 12s-skew
+    DISAGREEMENT itself: `sepRun.held.hp <= s.heldMustExceed` — written when heldMustExceed was
+    66 and game-true 63.8 sat below it. My re-ruling restates heldMustExceed to 60, so on the
+    merged tree that assert now reds BY DESIGN, and its own message says what to do: "If this
+    now exceeds the pin, the disagreement is RESOLVED: delete this ceiling, assert heldOk, and
+    close the [B] THREADS flag" — and the test's header adds "when A re-rules, the constants
+    below move WITH the ruling." It's B's file, so I did NOT land the edit on lane/a; the exact
+    change is applied and verified on my scratch merge (commit message "apply B's in-file
+    resolution", **357/0/0** with everything else green): replace the two-chain ceiling assert
+    with `assert(sepRun.heldOk, ...)` and keep the skew-chain 68.4 measurement as a drift
+    tripwire. Everything else in B's suite passes against my restated block unchanged —
+    `bareMustLoseBelow`, the >25 separation, the $80 cap, and both venturi locks.