erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs: reconcile the Current-state banner + milestones (M1.5 active; D.2b UI + R5 arc = interleaved parity tracks)

Browse source 
Discharges the 2026-06-22 banner-reconcile note: M1.5 stays the single
active milestone (remaining: A7 dungeon lighting, #137 dungeon collision,
#138 teleport-OUT). The D.2b retail-UI track and the R5 movement-manager
arc are recorded in the milestones doc as user-report-driven,
issue-level parity tracks subordinate to M1.5 — not milestones. Banner
rewritten within the 6-line budget; R5-V3/#170/#171 closes and the
R5-V4 pickup pointer included.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-07-05 10:02:04 +02:00
parent 0b998db713
commit 530453067a
2 changed files with 27 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/plans/2026-05-12-milestones.md
View file

@ -225,6 +225,24 @@ synthesis workarounds were removed by A6.P4. Remaining feel-level debt is
tracked (#116 slide-response, partial Ghidra fix shipped; A7 indoor
lighting fidelity not yet done — folded forward).
**Interleaved parity tracks (reconciled 2026-07-04 — NOT milestones).** Two
work streams have run alongside M1.5, both driven by the user's live
side-by-side-vs-retail sessions, both issue-level per the operating rules
(observed defects → ISSUES → fix → user gate), and both stay subordinate
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:
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
would manufacture scope where a tactical ledger (ISSUES + handoffs)
already carries them.
**Still OPEN in M1.5 — dungeon support (Phase G.3, issue #133).** Dungeons
don't work: the streaming/load/render/physics pipeline was built entirely
around outdoor landblocks (terrain + scattered buildings) and has no path