Hook payload session_id misattributed after /resume #26563

Bug Description

After resuming a session with /resume, the session_id in hook payloads switches to a different, older session ID. All subsequent tool use and prompt events are attributed to the wrong session, while the actual resumed session receives only lifecycle events (SessionStart/SessionEnd).

Environment

• Claude Code version: Latest (Feb 2026)
• OS: macOS (Darwin 24.6.0)
• Shell: zsh

Steps to Reproduce

1. Have multiple session JSONL files in a project directory (e.g., ~/.claude/projects/<project>/)
2. End a session (1be8b33f) with /exit
3. Resume it with /resume selecting 1be8b33f
4. Interact with the session (send prompts, trigger tool uses)
5. Observe hook payloads — the session_id field points to a different session (22c210bd)

Evidence

Session 1be8b33f (the one actually resumed and interacted with)

• JSONL file actively written until 14:58
• Hook events received:

Session 22c210bd (old session, incorrectly receiving events)

• JSONL file last modified at 02:53 AM (session was done hours ago)
• Hook events received:

Payload confirmation

The session_id field inside the JSON payload delivered to hooks via stdin is 22c210bd-3efd-4575-9390-226dd6c6bca6 for all misattributed events. This is not a downstream processing issue — Claude Code itself is injecting the wrong session_id.

Expected Behavior

After /resume of session 1be8b33f, all hook payloads (SessionStart, tool uses, prompts, Stop) should contain session_id: 1be8b33f-....

Actual Behavior

• SessionStart lifecycle events are correctly attributed to 1be8b33f
• All subsequent tool use and prompt events are incorrectly attributed to 22c210bd (a different, older session in the same project)
• The old session 22c210bd also receives a spurious SessionStart(source=resume) event

Impact

Any hook-based system that tracks sessions (analytics, logging, agent monitoring) will misattribute all activity to the wrong session after a /resume. This makes session-level analytics unreliable.