Bug: `claude --resume` silently exits when resuming a Fable 5 session (false "requires usage credits")

Summary

Resuming any session that was running on Fable 5 causes the CLI to attach and then exit silently within seconds — no error message, exit to shell prompt. Workaround discovered: passing --model opus on resume avoids the death entirely.

Environment

• Claude Code v2.1.215 (native, npm), Windows 11 Pro
• Max 20x plan, Fable 5 weekly usage under 10% (credits clearly available)
• Session model: claude-fable-5[1m] (set via settings.json model)

Steps to Reproduce

1. Run an interactive session with model Fable 5 (e.g. claude --rc "name", work normally)
2. Exit cleanly with /exit
3. claude --resume <session-id> (or pick from the resume list)

Expected

Session resumes; if a model entitlement check fails, show a message and fall back to another model while staying alive (this is exactly what happens in live sessions — we observed "Switched to Opus 4.8 (1M context) for this session · Fable 5 requires usage credits" mid-conversation with the session continuing normally).

Actual

• CLI attaches, prints session content, then exits silently (no error, exit code appears clean)
• In some runs the "Switched to Opus 4.8 … Fable 5 requires usage credits" line is visible right before death
• The "requires usage credits" claim is false — the account has >90% of its weekly Fable allowance remaining
• Session .jsonl is intact (a new bridge-session/remote-control record is appended, then nothing)

Evidence collected

• Reproduced across multiple projects/sessions on the same machine, in clean environments (spawned via Task Scheduler with no inherited env)
• Controlled A/B test on the same session id:
• claude --resume <id> --rc "name" → dies within seconds (repro 100%)
• claude --resume <id> --rc "name" --model opus → survives, full context restored, works normally
• Windows Application event log: no crash records (node/claude), i.e. process exits “voluntarily”

Hypothesis

The resume path runs a Fable 5 entitlement check before account state is fully restored, gets a false negative, and the model-switch fallback in the resume path terminates the process instead of continuing (unlike the live-session fallback which works).

Impact

Any Fable 5 user who exits a session cannot resume it without knowing the --model workaround — looks like data loss (session appears dead) though the transcript is intact.