Session ID changes when resuming a conversation via --resume

When resuming a conversation using --resume, the session_id provided to hooks is a new UUID rather than the original session's ID.

Observed behavior:

• Start a session → hook receives session_id: abc-123
• Quit terminal, resume with --resume → hook receives session_id: xyz-789 (new ID)

Expected behavior:
Resumed sessions should retain the original session_id, or hooks should receive an additional field like original_session_id or resumed_from to link them.

Use case:
Building integrations that need to track conversations across terminal restarts (e.g., logging to external files keyed by session).

Environment:

• Claude Code version: 2.0.50
• macOS