Cyd's screenshot: the commit board's LAUNCH button lit - which requires
the local pod to be staged - while the host's own row read 'connecting',
which is the word for a state of -1. Two reads of the same fact from two
places, disagreeing: the tick read the application state and armed on it,
and the paint handler read it AGAIN, separately, and got something else.
Why the paint's read returned -1 is not proven, and it does not need to
be: re-deriving state at paint time was the mistake, the same one that
broke five instruments in one night of the render-tick hunt. The tick
already stores every state it acted on in gShownStates, for change
detection - the paint now draws those values and reads nothing else. The
board and the arming can no longer disagree, because they are the same
read.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CydandClaude Opus 5
50399e016e