diff --git a/CLAUDE.md b/CLAUDE.md
index 4c6efe7a..7ad9a6a2 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -161,6 +161,8 @@ retired the duplication behind three separate defects. Suite 11,027 →
 user-passed 2026-08-05 with probe evidence; route 7's is THIN (one
 `cause=propagate`) and 4b-3's `cause=cellless` case remains unrun with an
 UNESTABLISHED trigger — route 7 invalidated its recorded recipe.
+**The owed connected-gate batch ran and USER-PASSED 2026-08-07** (see the
+banner atop the C5c handoff); the probe-family strip is unblocked and queued.
 
 **Read `docs/research/2026-08-05-c4-closeout-handoff.md` before any C5 or
 placement work.** It carries the four gate recipes, what C5 inherits (#318's
diff --git a/docs/research/2026-08-06-c5c-closeout-handoff.md b/docs/research/2026-08-06-c5c-closeout-handoff.md
index f7c52a59..b7b0f160 100644
--- a/docs/research/2026-08-06-c5c-closeout-handoff.md
+++ b/docs/research/2026-08-06-c5c-closeout-handoff.md
@@ -1,5 +1,28 @@
 # C5c closeout + successor handoff — the placement cutover's automated half is done (2026-08-06)
 
+> # GATES CLOSED 2026-08-07 — the owed connected batch ran and USER-PASSED
+>
+> The full six-part sitting ran the morning of 2026-08-07 on the post-S4
+> binary: nine-stop tour, portal repetition, the cancelled-teleport
+> vanish-and-return, equipped-item teleport, two-client observation
+> ("All of that pass"), and the fresh-process logout/relaunch/reconnect
+> ("Looks good" — graceful logout cleared the ACE session instantly, login
+> returned to the exact last location). Log evidence (`morning-gate.log`,
+> `reconnect-gate.log`): 19 reveal generations, 17 materializations, one
+> cancel correctly superseded by its immediate replacement, zero hangs,
+> zero wait-cues, zero invariant failures.
+>
+> **Honest residuals, recorded not hidden:** the placement probe families
+> were not armed during the sitting (only the edge-slide and step-height
+> probes were), so route-7's THIN `cause=propagate` evidence was not
+> thickened and 4b-3's `cause=cellless` case remains unexercised — its
+> trigger was never established and no known recipe produces it. Both
+> rows close as user-passed-with-thin-log-evidence; if either mechanism
+> regresses, the symptom-side gates above are what will catch it.
+>
+> **The probe-family strip is now UNBLOCKED** and queued behind the
+> in-flight Campaign S slice (build-slot ordering).
+
 **Read this before any C5c or post-campaign work.** It is the successor to
 `2026-08-05-c4-closeout-handoff.md` (whose ⚠ BISECT HAZARD block still
 applies and is repeated in §6).