docs(physics): hand off placement continuation executor

Synchronize the architecture doc, milestones, roadmap, and ISSUES with the
continuation-executor behavior commit (5db3de3c): the residence system is
now a complete dormant mechanism, both independent reviews PASS, and the
next boundary is the all-host production cutover. The admission handoff
gains its superseded banner; the successor handoff records the executor's
ownership, the retail anchors proven during review (the wire-contact gate,
queue-by-parent-GUID relation replay, HasAnims semantics), the seven new
register rows, exact test totals, the rollback command, and the cutover
checklist. #275 filed for the post-cutover legacy-Position unification.

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

docs/ISSUES.md

@@ -99,6 +99,25 @@ Copy this block when adding a new issue:
 
 ---
 
+## #275 — Unify the legacy Position wire path onto the executor's route classifier
+
+**Status:** OPEN — post-cutover (physics campaign, filed 2026-08-02)
+**Severity:** LOW (internal refactor debt; not a retail divergence)
+**Component:** Runtime / inbound Position
+
+**Description:** the legacy `InboundPhysicsStateController.TryApplyPosition`
+(today's only production Position wire caller) has no route-classification or
+contact concept; the continuation executor's `ApplyPositionAction` runs
+`RuntimeAuthoritativePositionRouteClassifier` with the wire's own `IsGrounded`
+bit and threads the classified `installPlacementFrame`/`clearParent` flags
+(register rows AP-131 documents the legacy caller's unconditional flags, AD-60
+the cell-semantics difference). When the production cutover wires the executor
+in, unify the legacy caller onto the same classifier (or delete it with the
+route) and retire AP-131/AD-60's legacy halves. See
+`InboundPhysicsStateController.TryApplyPosition` remarks.
+
+---
+
 ## #274 — Restricted/barred-house entry needs a connected retail comparison
 
 **Status:** OPEN — explicitly deferred by the user on 2026-07-31