docs: hand off placement campaign finish

docs/plans/2026-08-02-placement-cutover.md

@@ -6,6 +6,60 @@ residence + continuation-executor owner (`38fd4b8d` / `30012361` /
 `5db3de3c`), delete the legacy duplicate authorities, and retire AP-1/AD-1
 behind connected + user-visual gates.
 
+## Handoff checkpoint — 2026-08-03
+
+**Status: stabilization checkpoint accepted; campaign closeout is not yet
+complete.** The C3c production cutover and the O(changed) collision
+publication checkpoint are now playable after five separately committed
+root-cause fixes:
+
+- `01f4791e` stops origin recenter from manufacturing and replaying a second
+  retirement receipt for a pending-only live-projection bucket. Its exact
+  binary passed the complete Release suite, lifecycle route, and canonical
+  nine-stop soak (`connected-r6-soak-20260802-204309`, nine stops, zero
+  failures/wait cues/pending retirements).
+- `670f307c` keeps remote Create placement, the local-player physics host,
+  targeting, chasing, and attacks in the same world-coordinate frame. The
+  user accepted monster placement/chase/hit behavior and static placement
+  after portals.
+- `1fc529cd` materializes the canonical minimal static physics host before a
+  distant Use/MoveTo route and reconciles the pre-PartArray startup motion
+  suffix. The user accepted near and distant object use.
+- `f24532ad` defers one-shot F754/F755 effects until canonical placement has
+  bound presentation, retries projectile/static-animation sidecars on the
+  committed visibility edge, and keeps effect cells synchronized. The user
+  accepted buffs, recalls, arrows, combat spell projectiles, portals, and
+  static animation.
+- `175ad6b0` sends LoginComplete from the local first-placement terminal edge
+  instead of raw PlayerCreate receipt, so ACE's intentional login Hidden/
+  materialization state cannot race placement. The user accepted the login
+  haze behavior.
+
+Focused verification after the final fix passed 90 App effect/projectile/
+static-scheduler tests, two Runtime login tests, the exact live-entity cell
+tracking regression, all 79 Headless tests, and the Release solution build
+with zero errors. The long connected soak and complete solution suite have
+**not** been rerun on the final `175ad6b0` binary. A broader selected fixture
+run also exposed five `LiveEntityRuntimeTests` failures tied to the still-open
+placement cutover plus one old remote first-entry fixture that supplies an
+empty collision source; classify and fix those before claiming C5 closure.
+
+Remaining campaign work, in order:
+
+1. Reproduce and repair the six fixture failures without weakening their
+   assertions or adding compatibility bypasses.
+2. Finish C4's routes 2–7 and remove their legacy placement writers; fold in
+   #276 and #277 where their route becomes authoritative.
+3. Resolve #280 with retail's configured destination-prefetch window so the
+   portal viewport never reveals visibly constructing far terrain.
+4. Run C5's complete Release suite, lifecycle/reconnect route, latest-binary
+   nine-stop soak, two-client observation, and the remaining #269 slope-glide
+   visual check. A pass from `01f4791e` is evidence for that fix, not a
+   substitute for the final-binary soak.
+5. Delete the superseded paths, retire AP-1/AD-1/AP-131 and AD-60's legacy
+   half only when the code proves they are gone, then complete AP-22 and
+   AD-10 and close the campaign ledger.
+
 **Inputs (read in order):**
 1. [`2026-08-02-runtime-continuation-executor-handoff.md`](../research/2026-08-02-runtime-continuation-executor-handoff.md)
    — the completed dormant mechanism and its cutover notes.
@@ -189,7 +243,7 @@ same commit) → docs/handoff commit. No workarounds; no fused slices.
     175401`). Closeout:
     [`2026-08-02-c3c-cutover-closeout.md`](../research/2026-08-02-c3c-cutover-closeout.md).
     **Carried to C4/C5:** route-1 far-Create service-window conversion
-    if either streaming/broadcast radius changes (#276); the
+    if either streaming/broadcast radius changes (#277); the
     window-departure park narrowing; `NotifyRetirement`-on-active-entry
     subscriber invariant; the reachable equip-mid-conductor fail-fast;
     settle-CellId discard (#276-adjacent, see ISSUES).
@@ -198,9 +252,10 @@ 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).** May land as more than one commit if a route proves large;
+  polish). — OPEN at the 2026-08-03 handoff.** May land as more than one
+  commit if a route proves large;
   each sub-landing keeps the full review discipline.
-- **C5 — legacy deletion + closeout gates.** Delete every superseded legacy
+- **C5 — legacy deletion + closeout gates — OPEN.** Delete every superseded legacy
   path; parity tests; exact lifecycle/reconnect + canonical nine-stop
   connected routes; two-client observation; **user visual matrix** (the
   campaign's stopping point for user acceptance). Retire AP-1, AD-1,