docs: C4 handoff for routes 4b-3, 5, 6, 7, 3

Closes #312 as user-confirmed, with the caveat recorded rather than buried: the
accepting session's probe capture showed 22 parks and zero park-restores, so the
restoration path was not observed executing. If an invisible-remote report
recurs, that is where to start.

Re-scopes #309 as largely superseded by #312 — the presentation restore is the
behaviour its connected check was written to probe. What survives is the
narrower faithfulness question: retail's GotoLostCell keeps a lost-cell object
hidden until reenter_visibility, where acdream re-shows it on cancel.

Adds the handoff itself: branch state and the measured 11,027 baseline, the two
known flakes and the standing instruction not to conflate them, per-route
scope with the retail addresses and the traps already paid for (teleport_hook
runs BEFORE the placement; route 5 has no possible live gate because ACE never
sends UpdatePosition for a missile; route 6 needs zero production lines and the
campaign plan carries a false premise about create-time effects; route 7 must
write the child cell at BOTH the set_parent analog and the per-commit position
analog), and the six process rules this session paid for — chiefly that the
contract causes the defect, that a slice must split on discovery, and that a
green suite and a clean-looking live session are both non-evidence.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-04 12:00:15 +02:00
parent 2eb39a0250
commit 3e002993dd
2 changed files with 150 additions and 13 deletions

View file

@ -32,7 +32,14 @@ the delta-review round on the same route's remediation. Evidence:
## #309 — Cancelled lost-cell park re-shows the entity where retail would keep it hidden
**Status:** OPEN
**Status:** OPEN — but **largely superseded by #312** (closed `b1f914d5`,
2026-08-04). #312 made a cancelled park restore the presentation half as well
as the Runtime half, which is the behaviour #309's connected check was written
to probe. What remains genuinely open here is the narrower retail-faithfulness
question: retail's `GotoLostCell` keeps a lost-cell object HIDDEN until
`reenter_visibility` fires on cell arrival, whereas acdream re-shows it on the
cancel. Re-scope before running; the original six-step gate is now partly
redundant.
**Severity:** MEDIUM
**Filed:** 2026-08-04
**Component:** physics / placement
@ -230,19 +237,16 @@ not allocate a new array per tick.
## #312 — Cancelled park restored Runtime state but never the presentation half
**Status:** FIXED `b1f914d5`, **live gate NOT YET EXERCISED**. The 2026-08-04
two-client run looked correct to the user, but the probe capture shows 22
`[park]` lines (all `cause=unplaceable`) and **zero `[park-restore]` lines**
no park was cancelled, so the restoration path never ran. That session
therefore observed the intermittent failure *not reproducing*; it neither
confirms nor refutes the fix. Do not close on it.
**Status:** CLOSED — fixed `b1f914d5`, **user-confirmed 2026-08-04**.
**To actually exercise it:** the failing shape needs a park that is then
cancelled while the entity is canonically whole. Run with
`ACDREAM_PROBE_PARK=1` and look for a `[park-restore] … presentation=True`
line for the remote's guid. Absence of that line means the gate did not run,
whatever the screen showed. The mechanism is pinned by four tests with a
seven-revert discrimination table; what is missing is live confirmation.
**Caveat recorded for whoever revisits this:** the probe capture from the
accepting session showed 22 `[park]` lines (all `cause=unplaceable`) and zero
`[park-restore]` lines, i.e. no park was cancelled during it, so the
restoration path itself was not observed executing. The user judged the
behaviour correct and closed it. The mechanism is pinned by four tests with a
seven-revert discrimination table. If an invisible-remote report recurs, start
here and look for `[park-restore] … presentation=True` under
`ACDREAM_PROBE_PARK=1` before assuming a new cause.
**Severity:** HIGH (a remote player permanently invisible in world and radar)
**Filed:** 2026-08-04
**Component:** physics / placement / presentation