A user could not continue EventHorizon gameplay after a Mayday/safety stop because the persisted game session stayed in safety_state = mayday and the UI had no resume control.
/home/ax_julian/.kube/config.event-horizon Postgres.safety_state from mayday to running; scene content and turn count were not changed.985b611 (Add game safety resume control) to main.Resume control while safety state is paused/mayday and persists safety_state = running through the existing game-session API.cargo fmtcargo test passed: 113 tests total.cargo +1.88 build --release --locked -p eventhorizon-frontend --target wasm32-unknown-unknown passed.game_sessions rows with safety_state <> 'running' after the operational reset.At the time of this note, main was pushed but the Kubernetes deployment was still running the previous image sha-d9e40f732352; CI/deployment had not yet updated the pod during the initial poll window.