b07b678ef0
Disassembling built-in 69's handler at 0x8226ADF0 instead of trusting the summary: it loads rec = base[idx], tests rec+4 against zero (early exit = absent), passes rec+4 to sub_82301240 for the lifecycle lookup, and compares the byte at rec+104. rec+16 is never touched on that path. That explains the null poke result exactly -- I wrote into a field the condition does not consult. +16 remains a faithful OBSERVABLE (the arrival and death transitions were real) but it is a readout, not the input. It also explains why rec+4 holds small consecutive integers: it is a handle that sub_82301240 resolves, not a pointer. The corrected simulation of 'this squadron is gone' is rec+4 = 0, taking the documented early exit. Flags a general caution: this built-in table came from a subagent's reading of handler behaviour, and this is the second per-offset field description that did not survive the disassembly. The identifications of which built-in does what have held up; the offset meanings are leads to verify.