38df977b30
The plan was to separate ptlogo_back2eff from ptlogo_back2eff5 (same 1133x280, declaration 20 vs 18, either side of ptlogo_back2 at 19) by their resting fade alphas. Carried out, and refuted: both quads come back at alpha FF, and reading the bundle again, both elements REST at 255 under this project's own max-dwell rule — back2eff5's longest hold is t=74 at 255, and the 192 I had quoted is a later, shorter keyframe, not its resting value. The ambiguity stands. What the colour did buy is worth more than the tie-break: the first check of the fade/keyframe decode against the RUNNING GAME rather than against another parse. Every static element draws at exactly the resting alpha the bundle predicts, and the only two quads whose alpha moves between consecutive frames (88->88/86->87 and 3C->38) are the rotating effect pair and the PRESS (A) glow — the two things visibly animating on screen. Nothing had confirmed before that the alpha channel of a keyframe is what drives that throb.
