Archived session keeps running for hours after archive_session succeeds

Summary

Archiving a session via the session-management archive tool (archive_session) completes successfully, but the underlying session process continues running for hours afterward instead of terminating.

Steps to reproduce

1. In a running Claude Code session, call the session-management archive tool (mcp__ccd_session_mgmt__archive_session) with session_id: "self".
2. Approve the confirmation prompt shown in the client.
3. The session is archived successfully (confirmed by later un-archiving it).

Expected behavior

The session's underlying process stops running once it is archived.

Actual behavior

The session kept running for 2+ hours after the archive prompt was approved. Checking session state via get_session during that window showed isArchived: false, isRunning: true. A second archive attempt was then made, which also reported success. The user confirmed the archive action itself "works fine" — the problem is that the session keeps running regardless, requiring the window/terminal to be closed manually to actually stop it.

Environment

• Platform: Windows 11 Pro (10.0.26200)
• Model: claude-sonnet-5
• Local (non-remote) session

Additional notes

Surfaced while running the /wrap-up skill, which calls archive_session as its final step.