diff --git a/docs/plans/2026-08-02-placement-cutover.md b/docs/plans/2026-08-02-placement-cutover.md
index 565baf2e..64bc8348 100644
--- a/docs/plans/2026-08-02-placement-cutover.md
+++ b/docs/plans/2026-08-02-placement-cutover.md
@@ -252,8 +252,24 @@ same commit) → docs/handoff commit. No workarounds; no fused slices.
   4 (remote Create/Position; delete `RemoteTeleportController`/`Placement`
   and the inline MoveOrTeleport duplicate), 5 (projectile authoritative),
   6 (drops + split-recovery marking), 7 (residual pickup/parent/delete
-  polish). — route 2 implementation COMPLETE, pending review, at the
-  2026-08-03 handoff; routes 3/4/5/6/7 remain OPEN.**
+  polish). — route 2 COMPLETE AND USER-ACCEPTED 2026-08-03 (`9966b531`);
+  routes 3/4/5/6/7 remain OPEN.**
+  **Route 2 connected gate PASSED (user, 2026-08-03).** Provoked with the
+  retail `@pklite` entry-collision bump (`69ba9486` — the only reachable ACE
+  trigger for `ObjectForcePosition`; admin teleports advance `ObjectTeleport`
+  and exercise route 3 instead, see
+  [`2026-08-03-c4-route-2-visual-gate.md`](../research/2026-08-03-c4-route-2-visual-gate.md)).
+  The user observed the visible slide off the overlapped character (the
+  ForcePosition applied), correct animation, no heading change, and no leash
+  tethering or rubber-band after the correction — so the two named behaviour
+  changes (ack after commit; no `ConstrainTo` re-arm on this route) are
+  accepted live. Both Opus reviews PASS on the final diff after three FAIL
+  rounds.
+  **Adjacent, NOT a route 2 regression:** shipping `@pklite` made PK Lite
+  reachable for the first time and immediately exposed pre-existing PvP gaps —
+  melee/ranged attacks refuse a PKLite target (auto-target retargets to the
+  nearest other; auto-target off does nothing) while spells on the same target
+  work. Under investigation; filed separately.
   **Route 2 (ForcePosition) — implemented 2026-08-03, contract:**
   [`2026-08-03-c4-route-2-contract.md`](../research/2026-08-03-c4-route-2-contract.md),
   **plan:** [`2026-08-03-c4-route-2-implementation-plan.md`](../research/2026-08-03-c4-route-2-implementation-plan.md).