9e421b341c
wait_flight.sh carries the corpus's best discriminator, and it is a whole-image statistic rather than a named pixel: the flight HUD paints green over the frame at 1.3-1.5% green fraction, against <0.1% on every menu. Measured on the post-take-off state: green=0.0022, mean (1.6, 45.6, 50.1). That is 0.22% -- an order of magnitude above a menu, an order of magnitude below flight, on a dark blue-green frame. screen_id.py files it under "menu" because that is the closest bucket it has; the state is neither. wait_flight.sh then tapped A for 280 seconds and never saw the HUD. With the 12 \dat\movie accesses, the reading is consistent: this is the cutscene, it does not end on A, and it does not reach the flight HUD within five minutes. Open, cheapest first: how the movie path signals completion (the corpus already decoded the movie handler for the intro video and found a software-decode deadline); whether a mission can be started by a route that skips the launch cinematic; or whether the cutscene simply needs far longer under lavapipe. Oracle status overall: boot, menus and take-off are reliable and reproducible; only the cutscene->mission step is unsolved -- a much smaller and better-defined gap than the freeze it replaced.