--continue breaks all tool spawning after auto-update (stale binary path)

Bug Description

When resuming a session with --continue, all tools that spawn subprocesses (Bash, Glob, Grep) fail silently if Claude Code has auto-updated since the original session was created.

Error

ENOENT: no such file or directory, posix_spawn '/home/john/.local/share/claude/versions/2.1.39'

Every Bash command returns exit code 1 with no output. Glob and Grep also fail with the same posix_spawn ENOENT error. Only Read (which doesn't spawn a subprocess) continues to work.

Steps to Reproduce

1. Start a Claude Code session on version X (e.g., 2.1.39)
2. Let Claude Code auto-update to version Y (the old binary at ~/.local/share/claude/versions/X gets removed)
3. Resume the old session with --continue
4. Attempt any Bash command, Glob, or Grep — all fail

Expected Behavior

When resuming a session with --continue, the sandbox/tool configuration should resolve to the currently installed binary version, not the version that was active when the session was originally created.

Workaround

Start a fresh session instead of using --continue. This picks up the current binary path.

Environment

• Platform: Linux (Ubuntu, kernel 6.17.0)
• Claude Code version: was 2.1.39, now updated past it