0c930f203a
rec+4 = 0 (the early-exit path built-in 69 actually tests) sticks for 60s with all three squadrons poked, and neither the phase nor +16 changes. +16 stayed 2 while the handle it derives from read zero. Leading explanation: the phase-1 condition coroutine is not polling. Both pokes persist untouched and nothing recomputes anything, which fits the polls at 0xF524 living in a coroutine that only runs when a trigger starts it (built-in 1, fed from [phase+272]). But the honest problem is bigger: two pokes have now produced no observable effect and I cannot tell 'the game ignored the write' from 'the write never reached the game'. The stick test only proves the value persisted in the shared-memory FILE, not that Canary's guest sees it. That control should have come first, so both null results are downgraded to INCONCLUSIVE rather than evidence about the condition. Next: poke something with a visible effect (player hull, a HUD counter) and confirm it on screen before trusting any further null result. What still stands from these runs is only what was observed rather than poked -- the arrivals, ADN111's destruction, and the mission-over branch.