[Bug] `claude stop <id>` removes session from list while Ctrl+X updates status to "done"
Bug Description
Title: claude stop <id> does not behave like a single Ctrl+X in agent view
Claude Code version: 2.1.288
OS: <your OS / terminal>
### Description
The agent view documentation (https://code.claude.com/docs/en/agent-view) describes Ctrl+X and claude stop as equivalent ways to stop a background session ("You stopped the session with Ctrl+X or claude stop"). In practice, they behave differently.
### Steps to reproduce
1. Start two background sessions, e.g. claude --bg "<task A>" and claude --bg "<task B>".
2. Open agent view with claude agents.
3. Select session A and press Ctrl+X once.
4. From a separate shell, run claude stop <id-of-session-B>.
5. Compare the session rows in agent view and the output of claude agents --json.
### Expected behavior
Both methods produce the same result: the session is stopped, and its status is updated consistently in agent view and in claude agents --json.
### Actual behavior
- Ctrl+X (once) in agent view: Works as expected. The session is stopped and shows the status "done".
- claude stop <id> via CLI: The session is removed entirely from the claude agents --json output, but agent view still shows its previous status unchanged.
### Additional notes
- The documentation states that both methods are equivalent, but this is not the case.
- <optional: output of claude agents --json --all before/after claude stop>
- <optional: output of claude daemon status>
Environment Info
- Platform: darwin
- Terminal: xterm-256color
- Version: 2.1.288
- Feedback ID: 555fac76-f626-4397-8151-7416514c07d1