72b0e23e3b
Driving toward a mission for the second capital-ship capture works as far as two screens nobody had captured — DIFFICULTY, then SELECT DATA — and then the guest dies at PC 0x82307128, the SAME std::map/set erase as the boot-time throw, with 537 stacked dumps. Both screenshots are committed. So the ship item's blocker is the crash, not navigation: the game reaches the save-slot screen and dies enumerating save data. mem_watch stays eliminated — this run had it off. And the save/cache path is the common factor across both firings. Stated as unsettled: whether a warm cache prevents this firing the way it prevents the boot-time one. The cache WAS warm here, so it looks like no, but that is a single run and the cold/warm A/B was only ever run against the boot-time throw.