[BUG] Auto-armed artifact live-updates watch keeps running after the artifact is deleted

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Creating a doc through the claude.ai Docs connector auto-arms a live updates for artifact … watch. After the doc is deleted with the same connector's delete, and after the connector itself is removed from the session with a permissions.deny rule, the watch keeps running and is shown as working. It uses no tokens, but it stays in the task list as an active task for more than 1.5 hours, and the assistant has no way to stop it. #89019 and #89308 report that the watch returns no handle; this report is about a watch that outlives its artifact.

What Should Happen?

The watch ends when its artifact is deleted: there is nothing left to watch. It also ends when the connector that created the artifact is no longer available in the session.

Error Messages/Logs

No error is shown. The watch stays in the task list as working, with 0 tokens.

Steps to Reproduce

1. In a session with the claude.ai Docs connector, ask Claude to create a doc. The connector's batch call creates it, and a live updates for artifact https://claude.ai/artifact/<id> task appears.
2. Ask Claude to delete the doc. The connector's delete on the project succeeds ({"verdict":"allow"}).
3. Add "permissions": {"deny": ["mcp__claude_ai_Claude_Docs"]} to ~/.claude/settings.json. The session reports that the connector's tools are gone.
4. Look at the task list.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.283 (Claude Code)

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

• NixOS. Claude Code is driven by a third-party desktop client (T3 Code) over --output-format stream-json. Session model: Opus 5.5.
• The 2.1.283 changelog says an automatically armed watch now ends after 3.5 hours with no activity, so it presumably clears then, but a deleted artifact should end it at once.
• Why it matters: a client that lists background tasks shows a task that has been "working" for hours. I took it for a stuck subagent and had to investigate, and the assistant cannot stop it either (#89308).