Session resume fails immediately after logout

Description

Session resume command fails with 'No conversation found' error immediately after session ends, even though the resume command was just printed.

Steps to reproduce

1. Run a long session in Claude Code
2. Session ends and prints resume command: claude --resume <session-id>
3. Immediately try to resume with the provided command
4. Get error: 'No conversation found with session ID: <session-id>'

Expected behavior

Session should be resumable for at least several minutes after end-of-session message is printed.

Actual behavior

Attempt to resume fails within seconds, suggesting race condition in session state persistence.

Environment

• Platform: Windows 11 Pro
• Session duration: 9h 7m 37s
• Session ID: a07ddbcc-7d0a-4856-acc9-6f8bed3514e8
• Models used: claude-sonnet-4-6, claude-haiku-4-5

Analysis

The resume command is printed as part of normal exit output, but the session metadata appears not to be flushed to disk before logout completes. The session ID is valid but the local Claude Code client doesn't have it in its session cache.