docs: a fourth paint order attempted; the title is intermittent, not input-bound

The tie-break needs a fourth measured screen with a tied group, and OPTIONS is
three d-pad steps from the main menu, avoiding the NEW GAME hang. It was not
reached.

Advancing past the title is intermittent: 1 success in 3 attempts today with the
same binary, profile and procedure.

Attempt 1 stalled before the title existed. The guest was alive - RSS steady at
598MB and the keystroke poll counter climbing past 15000 - but the screen was
black and screen_children.py found ONLY the splash object resident. So that
failure is not a presentation problem: the game never constructed the title.
Being able to separate "stalled before building the screen" from "built but not
presenting" is new, and it is what the reader is for.

Attempt 2 reached the title at 265s and refused four presses - (A) at 0.25s,
0.25s and 0.5s, START at 0.3s - every one of them logged as DELIVERED to the
guest. Third independent confirmation that input delivery is fine and the game
simply does not act on the press. Waiting longer does not help either: presses
were spread from 10s to about 4 minutes after the title appeared, while the
earlier successful run's press landed within seconds.

Records the log as evidence and states the next probe: it has to be guest-side
now, on whatever consumes the keystroke, since the input path is excluded.

docs/re/BACKLOG.md

@@ -141,7 +141,12 @@ See [`structures/ui-composable-bundles.md`](structures/ui-composable-bundles.md)
   the alpha says otherwise.
   **Next:** it is one element on one screen, so the cheap move is a fourth
   measured screen with a tied group — not more static guessing at fields that
-  have all now been checked.
+  have all now been checked. 🔴 **Attempted 2026-08-19 and blocked:** advancing
+  past the title is intermittent — **1 success in 3 attempts**, same binary,
+  same profile, same procedure. Input is excluded for the third time (every
+  press logged as delivered, `vk=5800`/`vk=5814`); one failure stalled *before
+  the title was built at all*, with the guest alive and polling and only the
+  splash object resident. Next probe must be guest-side, not input-side.
 * ❔ **Blend mode.** Everything is straight alpha-over. The near-white flash
   quads (`0xf0ffffff`) and coloured ones (`0x60ff0000`) may be additive. The
   title capture cannot separate the two — its resting elements are all