b4d4167d42
Live WS E2E after the #93361 merge (real web_server + tui_gateway, isolated HERMES_HOME, 2s grace): drop socket -> re-resume stored id on a new socket still produced a ws_orphan_reap reclaim. The lazy/unpersisted resume branch (no state.db row yet -- every fresh Bot Chat) returned the sentinel-parked live record without rebinding its transport or cancelling the armed reap Timer, so the storm survived for exactly the Bot Mode sessions the cluster targeted. The unit-covered paths (_live_session_payload, _reuse_live_response, _claim_or_reuse_live) were all correct; this branch bypassed them. Regression test drives the real session.resume RPC against a sentinel-parked unpersisted record (sabotage-verified: fails without the fix). After the fix the full live E2E passes 10/10 scenarios including a 4-cycle drop/resume storm loop with zero reclaim broadcasts.