Read the Decoder's existing title draw log from the ref. The additive quad carries
per-vertex alpha 68, 67, 56 across log frames 1, 2 and 4.
Identification confirmed independently and without using their attribution: the
quad is 537.6 x 75.6 px and ptbtn00f.png ships at 537 x 76.
Their free check on my ramp holds -- all three alphas are at or below my declared
peak of 80 and none equals a keyframe value, so the game interpolates rather than
steps. Two independent decodes agreeing.
The frame spacing does not fit. At HANDOFF Q1's 2 units per rendered frame my
falling segment predicts 68, 64.5, 57.6 against observed 68, 67, 56; at 0.5 units
it predicts 68, 67.2, 65.4. No constant rate fits both steps.
Three candidates I cannot separate: my ramp is wrong somewhere, the log's frame
numbering is captured rather than engine frames -- it skips from 2 to 4, so it is
demonstrably not dense -- or emulator pacing varies. The middle is most likely and
cheapest to check, and it is theirs.
It does not disturb the ramp's shape or ceiling, which the alphas confirm. It
disturbs only posing my renderer at their captured instant by stepping units, so
the vertex alpha stays the right readout and a frame index would have been wrong.
6b713e8d14