0b4dcc6e8f
BACKLOG said the per-class ship generalisation needs "the capture-ship-placement build of Canary". Checked: the ship capture is in the CURRENT build — RequestShipCaptureFrame and CaptureShipDrawForRE are in command_processor.cc on auto/re-ui-draw-order, and F10 wrote a 2.9 MB ship capture from this session's binary. No separate build is needed. What actually blocks it is navigation: a mission is behind the main menu, and (A) at the title is accepted on about half of boots with nothing observable predicting which. tutorial_launch.sh drives boot -> title -> menu -> TUTORIAL and retries the WHOLE BOOT on refusal, because re-pressing the same title never works — measured, not assumed. First run of it: (A) refused, so it rebooted. That is the expected shape rather than a failure of the harness.