57f0238af2
Ran the direct test instead of a seventh attempt at winning. All three objective squadrons were live (state 2); the write to +16 sticks, and 60s later with all three reading 4 -- the value a naturally-destroyed squadron takes, measured on ADN111 -- [ScriptPhase+196] is still 0 and the ordinal still 1. So 'phase 1 clears when ADN110/111/112 are destroyed' is not confirmed and its simplest form is refuted. The bytecode reading (three unit_state polls then set_flag(8)) stands; what does not follow is that flipping the field equals the kill. The persistence is the clue: built-in 69 normalises +16 when it polls, so a running condition coroutine should have overwritten the poke within a frame. It did not, which points at the condition being evaluated only when a trigger fires. Also corrects the per-unit record layout: +4 is 26/27/28 for the three squadrons -- small consecutive integers, NOT the 'live object pointer' the built-in summary describes (an undeployed squadron has +4=0). +20 = 9 is exactly their member count n from the roster, so the record is per-squadron and carries its strength. My own probe printed 'obj=yes' by testing that word for non-zero rather than pointer-ness, which made an index look like an object.