37aaecf48b
Table-driven across every session-scoped RPC that can hit a dead runtime id, plus the invariants the scattered copies disagreed on: resume targets the session-owning profile (never forks into the active one), the recovered id publishes exactly once, drift during the resume aborts instead of retrying, a resume that itself 404s rethrows the ORIGINAL error, and recovery is bounded to a single retry. These run without touching the REST layer because profile resolution is injected — the pre-consolidation helper reached through resolveStoredSession -> getSession(), which made its coverage depend on store state left behind by whichever test file ran first (passed alone, timed out at 15s alongside index.test.tsx). Co-authored-by: xxxigm <xxxigm@users.noreply.github.com> Co-authored-by: rapsealk <rapsealk@users.noreply.github.com> Co-authored-by: webtecnica <webtecnica@users.noreply.github.com>