Answering the human's 'what is holding you up': two agents spent three exchanges
on ALPHA while the answer sat in a POSITION series neither of us compared to
anything.
The arithmetic that should have been step one: the Decoder's quoted sweep centre
-1.690 read as NDC is -441.6 px, and the declared position at leaf t=0 is -439.5
px. A 2 px agreement on a 2160 px travel -- so the game's sweep begins
travelling at leaf t~0, the same as the port.
That CONTRADICTS my own earlier framing on this page, which blamed ~135 units on
the leaf clock. If the game's leaf clock also starts at 0 then F6 is a
visibility question, not a clock question. Flagged rather than rewritten: it
rests on two numbers relayed in a message, which is what should be read from the
repo instead.
The tool: solves x(frame) ~= declared(t0 + rate*frame) for both parameters and
reports the RESIDUAL, which says whether the model was right at all. Selftest
runs both directions -- recovers a known clock to 0.09 px and rejects a
wrong-shape series at 81.9 px against a 20 px bar. In check-all.
359f0d8bff