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>
This commit is contained in:
parent
dccd700991
commit
aa734f3409
5 changed files with 75 additions and 18 deletions
|
|
@ -734,8 +734,24 @@ diagnostic scaffolding, not yet the final collision system.
|
|||
streaming hole (`9b06a9b8`) — both verified live. Filed **#170** (remote
|
||||
creature chase+attack animation divergence vs retail — glide/over-frequency/
|
||||
uniform attacks; decomposes into #159 + pending_motions loop + dead-reckon
|
||||
glide). NEXT: R5-V3/V4 (sticky/TS-39, facade/#164 — `r5-wiring-handoff.md`)
|
||||
OR #170. Entry point: `docs/research/2026-07-03-session-handoff.md`.
|
||||
glide). **#170 CLOSED + gated 2026-07-04** (`427332ac` re-dispatch flood +
|
||||
`1051fc83` armed-moveto-always-ticks). **R5-V3 SHIPPED + gated 2026-07-04**
|
||||
(#171 sticky melee, three slices `5bd2b8bc`/`7a823176`/`69966950` — TS-39
|
||||
retired, TS-43/TS-44/AP-82 filed). **R5-V4 behavioral items SHIPPED + gated
|
||||
2026-07-04 `f423884b`** (head style-on-change all mt types, #164 autonomy
|
||||
bit, mt-0 wire flags consumed). **R5-V5 SHIPPED 2026-07-05 — the R5 arc is
|
||||
DONE**: the `MovementManager` facade (retail acclient.h `/* 3463 */`,
|
||||
methods 0x00524000-0x00524790) now owns each entity's interp+moveto pair —
|
||||
ONE per entity (`RemoteMotion.Movement`, `PlayerMovementController.Movement`,
|
||||
chase-harness mirror); the three wiring sites construct through
|
||||
`MoveToFactory` + `MakeMoveToManager` (0x00524000) and the relay shapes
|
||||
(`UseTime` 0x005242f0, `HitGround` 0x00524300, `HandleExitWorld` 0x00524350,
|
||||
`CancelMoveTo` 0x005241b0, `HandleUpdateTarget` 0x00524790,
|
||||
`PerformMovement` 0x005240d0) replace the loose-pair call sites. Structural,
|
||||
zero behavior change; 15 facade conformance tests; suite 4052 green with the
|
||||
183-case/funnel/moveto/chase/sticky suites unmodified. Arc close-out:
|
||||
`docs/research/2026-07-03-r5-managers/r5-wiring-handoff.md`. Open follow-ons
|
||||
carried: #167 (ConstraintManager arming), TS-42 per-tick order (R6).
|
||||
- **L.2g — Inbound motion interpretation (remote-entity CMotionInterp funnel).**
|
||||
ACTIVE 2026-07-02. Port retail's inbound motion pipeline verbatim for ALL
|
||||
remote entities (players, NPCs, monsters — one funnel, user-approved):
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue