docs: R5 arc close-out — V5 facade shipped, arc DONE; M1.5 critical path next

- r5-wiring-handoff.md: arc close-out banner (V1-V5 trail, relay/anchor
  inventory, carried follow-ons #167 / R6 TS-42 / TS-43)
- roadmap: R5 ledger entry completed through V5 (incl. the #170/#171/V4
  gate history that had only lived in memory/handoffs)
- milestones: the interleaved parity-track note — R5 arc DONE 2026-07-05
- CLAUDE.md Current state: R5 arc DONE; next work = M1.5 critical path
  (#137 dungeon collision, #138 teleport-OUT, A7 dungeon lighting)
- pickup prompt marked DONE

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

docs/plans/2026-05-12-milestones.md

@@ -232,11 +232,13 @@ side-by-side-vs-retail sessions, both issue-level per the operating rules
 to M1.5 rather than becoming milestones of their own: (1) **D.2b retail
 UI** — inventory window / paperdoll / item interaction shipped and gated;
 next container-switching (`claude-memory/project_d2b_retail_ui.md`);
-(2) **the R5 movement-manager arc** — the retail MovementManager family
-port (TargetManager voyeur system V2, StickyManager/PositionManager V3)
-that closed the #170 chase-slide and #171 pack-melee gates (2026-07-04);
-one capstone slice (R5-V4) remains
-(`docs/research/2026-07-03-r5-managers/r5-wiring-handoff.md`). Rationale:
+(2) **the R5 movement-manager arc — DONE 2026-07-05** — the retail
+MovementManager family port (TargetManager voyeur system V2,
+StickyManager/PositionManager V3, V4 behavioral items, V5 MovementManager
+facade — every entity now holds ONE `MovementManager` owning its
+interp+moveto pair) that closed the #170 chase-slide and #171 pack-melee
+gates (`docs/research/2026-07-03-r5-managers/r5-wiring-handoff.md` has the
+arc close-out). Rationale:
 rule 1's "one active milestone" governs where NEW scope goes — these
 tracks fix observed retail-parity defects in already-shipped systems,
 which the operating rules have always allowed; declaring them milestones