OOM crash corrupts session data: custom names lost and sessions missing from resume

Description

When Claude Code crashes due to OOM (high RAM consumption — see #21403, #20348), the session resume functionality is left in a broken state:

1. Custom session names are lost — sessions that were given custom names revert to unnamed or are no longer identifiable
2. Sessions are missing entirely — multiple sessions that existed before the crash no longer appear in the resume picker at all

This means an OOM crash not only kills the active session but also damages data for other unrelated sessions.

Expected Behavior

• An OOM crash (or any unexpected termination) should not corrupt session metadata
• All previously saved sessions should remain available in the resume picker with their original custom names intact
• Session data should be written atomically or journaled so that a crash mid-write doesn't destroy existing data

Actual Behavior

After an OOM crash:

• Several sessions are missing from the resume list
• Sessions that do appear have lost their custom names

Environment

• OS: Windows 11 Home 10.0.26200
• Claude Code: Latest (CLI)

Related Issues

• #21403 — Memory leak causing OOM kill (15-17GB memory consumption)
• #20348 — Memory leak: VmPeak reaches 135GB, causes OOM kill
• #22107 — Session resume logic losing context