docs: record the C4 connected gate results — three of four run, with their gaps

User-run against the exact e0f96a55 Release binary with the retail UI and both
probes; user verdict "works great".

Route 3 passes unambiguously: three [local-tp] lines, all Committed,
hookTail=ran, leash=armed, across three destinations. leash=armed is the
load-bearing observation — before the round-2 R3 fix that field read
IsFullyConstrained() and could only ever print unarmed, so the line proves
both the leash arm and the corrected probe.

Route 7 passes but THINLY: 17 [child-cell] lines, of which 13 attach, 3
delete, and exactly ONE propagate. The stated criterion (at least one
propagate) is met, so the gate passes — but propagation across a parent cell
crossing is the slice's whole purpose, and one sample shows the path executes
rather than that it holds across repeated crossings. Recorded as thin rather
than counted as full coverage; a future session should expect double-digit
propagate counts from several equipped boundary crossings.

Route 6 passes on visual confirmation only, which is inherent to a route with
zero production lines and therefore no probe.

Gate 4 (4b-3's cause=cellless) remains unrun, as expected — route 7
invalidated its recorded trigger and the replacement is UNESTABLISHED.

Two things this session did NOT exercise, recorded rather than glossed: route
3's autorun cancel never fired (all three portals report autorun=unchanged, so
the PlayerTeleported @0x006B32B0 SetAutoRun port is live-unverified — engage
autorun before a portal to close it), and AP-144's autonomy divergence stays
structurally unreachable. Per both round-2 reviewers' condition, this session
is explicitly NOT scored as covering #318.

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

docs/research/2026-08-05-c4-closeout-handoff.md

@@ -357,3 +357,50 @@ exist, record that, never a substitute that measures something else.**
   never a player character (see rule (g)).
 - Graceful close matters — a hard kill leaves ACE holding the session
   ~3 minutes.
+
+---
+
+## Connected gate RESULTS — 2026-08-05 (user-run, user-accepted)
+
+Run against the exact `e0f96a55` Release binary with the retail UI
+(`ACDREAM_RETAIL_UI=1`), `ACDREAM_PROBE_CHILD_CELL=1` and
+`ACDREAM_PROBE_LOCAL_TELEPORT=1`, live ACE at `127.0.0.1:9000`.
+Log: `c4-gates.log` (731 lines). **User verdict: "works great."**
+
+Three of the four owed gates were exercised in one session. Probe evidence,
+because a clean-looking session is not a pass:
+
+**Route 3 (portal) — PASS, unambiguous.** Three `[local-tp]` lines, every one
+`status=Committed hookTail=ran leash=armed`, across three distinct
+destinations (`0x00070143`, `0xA9B40019`, `0x1134001F`). `leash=armed` is the
+load-bearing observation: before the round-2 R3 fix the field read
+`IsFullyConstrained()` and was structurally incapable of printing anything but
+`unarmed`, so this line proves both the arm AND the corrected probe.
+
+**Route 7 (child cell) — PASS, but THIN.** 17 `[child-cell]` lines:
+13 `cause=attach`, 3 `cause=delete`, **1 `cause=propagate`**. The stated pass
+criterion (at least one `cause=propagate`) is met, so the gate passes — but
+propagation across a parent cell crossing is the slice's entire purpose, and
+one sample proves the path executes rather than that it is robust across
+repeated crossings. A future session should run several equipped landblock
+crossings and expect `propagate` counts in double digits.
+
+**Route 6 (drops) — PASS on visual only.** Route 6 has no probe (zero
+production lines by design), so this gate rests entirely on the user's visual
+confirmation. That is inherent to the route, not a gap in the run.
+
+**Gate 4 (4b-3 `cause=cellless`) — STILL NOT RUN**, as expected: its recorded
+trigger was invalidated by route 7 and the replacement is UNESTABLISHED.
+
+### Not exercised — recorded, not glossed
+
+- **Route 3's autorun cancel never fired.** All three portals report
+  `autorun=unchanged`, meaning the local player was not auto-running at
+  arrival. The `PlayerTeleported` @0x006B32B0 `SetAutoRun(0,1)` port is
+  therefore live-unverified. To close it: engage autorun, then take a portal,
+  and expect `autorun=cancelled`.
+- **AP-144's autonomy divergence remains unreachable** (`TrySetAutonomyLevel`
+  has zero production callers), so nothing in this session could have
+  exercised it either way.
+- Per both round-2 reviewers' condition, **this session is explicitly NOT
+  scored as covering #318** (the end-to-end presentation composition test).