Context lost on Esc interrupt - no auto-save of intermediate results

When a long-running task (e.g., running multiple verification commands that take 20+ minutes) is interrupted by the user pressing Esc, all context from that execution is completely lost. The subsequent conversation has no memory of what was being done or any partial results.

Steps to reproduce

1. Ask Claude Code to run multiple long-running shell commands (e.g., 3 CLI verification tests)
2. Wait 20 minutes while they execute
3. Press Esc to interrupt
4. Continue the conversation — Claude has zero knowledge of what it was doing or any results

Expected behavior

• Intermediate results should be persisted (to memory or temp files) as they complete, not only after all tasks finish
• At minimum, Claude should retain context about what task it was working on and what was completed before interruption

Actual behavior

• Complete context loss on Esc
• User's time is wasted with no recovery possible

Impact

• Long-running tasks become risky to run — if anything goes wrong, everything is lost
• Users must choose between waiting indefinitely or losing all progress