--resume loads hours-old context instead of current session state

Description

When resuming a session with claude --resume, the context is hours behind the actual work done. The resumed session doesn't reflect recent tool calls, file edits, or task progress — it picks up from a much earlier snapshot.

Steps to Reproduce

1. Work in a Claude Code session for several hours (running tasks, editing files, making progress)
2. Get forced out of the session (e.g., by the PowerShell escape bug #21576, or a crash)
3. Resume with claude --resume and select the session
4. The resumed session context is hours behind — it doesn't know about recent work

Expected Behavior

Resumed session should reflect the most recent state, including all tool calls, file changes, and task progress up to the point the session was interrupted.

Actual Behavior

The session resumes from a much earlier checkpoint. Hours of context are missing. The user has to re-explain what was done or start over.

Environment

• Platform: Windows (MSYS_NT-10.0-26200)
• Shell: bash (Git Bash / MSYS)
• Claude Code: latest channel

Notes

This is especially painful when combined with the PowerShell escape bug (#21576), which forces users out of sessions frequently. The combination means losing hours of work context on every crash.