Finding REMAINING OB in RAM means getting to the escort stage, and launch_mission.sh exists for exactly that. It carried three of the dead patterns this session has been clearing: six vgamepad calls (the command no longer exists, so the entire scripted route pressed nothing), the XUID E0300000EFBEA3D4 which has no profile behind it and therefore opens the sign-in dialog that swallows every keystroke, and the emulator's stdout going to /dev/null. wait_flight.sh had a fourth, in the tap that skips the launch cinematic. Fixed, the route works far past where it used to stop: boot -> title -> LOAD GAME -> slot 01 -> READY ROOM -> TAKE OFF -> the Stage 02 briefing map, with ACROPOLIS labelled on it. And it stops there: 384 dumps at PC 0x82307128 and no flight HUD within 300s. The briefing is still animating (two shots a minute apart differ by RMSE 2986), so the emulator is not frozen - flight simply never starts. One discriminator worth recording: the TUTORIAL reaches flight and has run completely crash-free, while this path crashes during the briefing, which is where the stage content loads. That is consistent with the cache-flush shape the crash has always had, and points at WHAT is being loaded rather than at how far the navigation gets. REMAINING OB is therefore still not found - the mission was never entered.