Long multi-phase sessions lose all context after sleep/Windows Update

What happened

I worked with Claude Code for ~5+ hours on a multi-phase plan. My Windows machine went to sleep during inactivity and a Windows Update ran during that period. When I resumed, Claude Code had:

• No memory of the multi-phase plan it had been executing
• No recoverable conversation history I could pull back up to reconstruct context
• No persisted plan state to resume from

The auto-memory system was empty — it had not captured the plan or progress through it.

Impact

5+ hours of working context — including the plan structure, decisions made, and progress through phases — was effectively lost. There was no /resume path back to that session.

Environment

• OS: Windows 11 Home (10.0.26200)
• Working dir is on a WSL-mounted path (Z:\home\lily\wsl_git\...)
• Triggering event: idle sleep + Windows Update reboot

What I'd want

1. Conversation transcripts for long sessions should survive reboots and be discoverable from /resume (or equivalent), even after a Windows Update.
2. When a multi-phase plan is active, the plan state itself should be persisted somewhere recoverable on restart (not only in-memory).
3. If transcripts already are persisted on disk somewhere, surface where — I couldn't find them.