e9541d213f
The 6s post-spawn liveness poll (#86687) returned on the FIRST process-table hit, so a gateway created and then killed moments later — e.g. by the parent shell's Job Object teardown when CREATE_BREAKAWAY_FROM_JOB is denied — still earned a "✓ Gateway started" line (#91675 hole a). And no poll can ever observe a death that happens AFTER the CLI process exits, which is exactly when the Job Object teardown fires. Two layers: 1. _wait_for_gateway_ready now treats the first hit as provisional: the gateway must stay visible through a 2s confirmation window (_confirm_gateway_stable) before it is reported ready; a death during confirmation resumes polling until the deadline. Failure output is an honest ✗ with the Job Object explanation and the schtasks /Run recovery command when a Scheduled Task exists. 2. Start attestation (report-async-death): every ✓ persists state/gateway.start-attestation.json with the vouched-for PIDs. The next `gateway start`/`gateway status` invocation checks it — if the attested PIDs are gone with no clean-exit record in the lifecycle ledger, the CLI reports (once) that the previous ✓ was false and prints the schtasks recovery hint. `gateway stop` and a clean lifecycle-ledger exit clear the marker silently. Also: when _spawn_detached had to retry without CREATE_BREAKAWAY_FROM_JOB, the ✓ now carries an explicit "could not break away from this shell's Job Object" warning, and the post-update cold-start ✓ (update_cmd) writes the same attestation marker. Sub-symptom (b) of #91675 (post-update cold-start only resumes the active profile) is handled separately by PR #99685. Fixes #91675