docs: correct #312 — the live gate was never exercised

I closed #312 as user-passed on a two-client run that looked correct. The probe
capture from that same run shows 22 [park] lines, all cause=unplaceable, and
ZERO [park-restore] lines: no park was cancelled, so the restoration path never
executed. The session observed the intermittent failure not reproducing, which
it also did on the prior day's second recall. It neither confirms nor refutes
the fix.

Reopened to FIXED / live-gate-not-exercised, with the acceptance signal stated
explicitly: a [park-restore] ... presentation=True line for the remote's guid
under ACDREAM_PROBE_PARK=1. Absence of that line means the gate did not run
regardless of what the screen showed.

This is the same class of mistake the probe was added to prevent one commit
earlier — treating a clean-looking session as evidence that a rarely-taken path
works. The mechanism remains pinned by four tests with a seven-revert
discrimination table; only the live confirmation is missing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-04 11:48:32 +02:00
parent 97b22b8606
commit f4f2579575

View file

@ -230,9 +230,19 @@ not allocate a new array per tick.
## #312 — Cancelled park restored Runtime state but never the presentation half
**Status:** CLOSED — fixed `b1f914d5`, **two-client visual gate USER-PASSED
2026-08-04**. The recalled remote appears in world and on radar and stays
correct after going idle.
**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.
**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.
**Severity:** HIGH (a remote player permanently invisible in world and radar)
**Filed:** 2026-08-04
**Component:** physics / placement / presentation