4b0263b80f
The previous entry named the next step: "tap (A) once per second and see whether the success rate goes to 1". It was run. The answer is no. 40 presses at 1/s on the title change nothing, and neither does one each of START, B, BACK, X and Y. Every press was delivered (the driver logs down/up for each) and the new [RE-INPUT] diagnostic never fired, so nothing was swallowed — the guest received them and ignored them. Also recorded, because it destroys a run rather than merely wasting it: tapping (A) through the boot (88 presses over the intro) ends on a permanent black screen with no crash and no throw. What is left is a difference in STATE, not in input: the one success came on a title that appeared ~83 s into a warm boot, the failures on titles that appeared after a full attract cycle. "The attract-loop title is a non-interactive presentation" is written down as a hypothesis with the experiment that would settle it — a log_ui_draws capture in each state, looking for ptbtn00.
