Windows: --resume silently fails for sessions created by older CLI version (npm to native migration)

Description

claude --resume <session-id> silently exits (returns to terminal prompt with no error message) when attempting to resume sessions created by a prior CLI version. Sessions created by the current CLI version resume successfully.

Environment

• OS: Windows 11 Home 10.0.26200
• Shell: Git Bash
• Current CLI: v2.1.62 (native installer, latest channel)
• Previous CLI: v2.1.58 (npm installation)

Steps to Reproduce

1. Had Claude Code installed via npm (v2.1.58), created multiple sessions
2. Uninstalled npm version, installed native CLI (v2.1.62)
3. Attempted to resume an older session:

``bash
claude --resume da034b9b-11bd-45f8-b4e9-8d992114d7b8
``

1. CLI silently exits back to the terminal prompt — no error, no output

Expected Behavior

Session should resume, or CLI should display an error message explaining why it cannot.

Actual Behavior

CLI silently exits with no output.

Investigation

• Sessions created by v2.1.62 resume fine with --resume
• The .jsonl files for old sessions are valid JSON (verified programmatically — zero invalid lines)
• The session format is identical between versions — same keys (cwd, gitBranch, isSidechain, message, parentUuid, permissionMode, sessionId, timestamp, todos, type, userType, uuid, version), same structure
• Only difference is the version field: 2.1.58 vs 2.1.62
• The sessions-index.json file was also missing/stale for the project directory, though this does not explain the --resume <id> failure since that uses the session ID directly

Additional Context

• Also observed that /resume within an active session fails — likely related to the missing/stale sessions-index.json
• Multiple session .jsonl files exist in the project directory from the npm era but are invisible to the native CLI
• This affects users migrating from the deprecated npm installation to the native CLI
• Possibly related to #33912 (same symptom on macOS, different trigger)