MCP channel notifications stop being delivered to session, requiring /reload-plugins

Description

MCP channel notifications (specifically notifications/claude/channel from the Telegram plugin) stop being delivered to the active Claude Code session after some time. Messages are received by the MCP server process (confirmed running via ps), but they never surface in the conversation.

Running /reload-plugins immediately fixes the issue — new messages start arriving again. This suggests the stdio MCP transport or the notification forwarding layer drops/ignores channel notifications after a period of inactivity or some other trigger.

Steps to reproduce

1. Start Claude Code with --channels plugin:telegram@claude-plugins-official
2. Send messages via Telegram — they arrive correctly
3. Wait some time (unclear exact duration, possibly related to idle periods)
4. Send new Telegram messages — they are not delivered to the session
5. Run /reload-plugins — messages start arriving again

Environment

• Claude Code: 2.1.80
• macOS 26.3.1 (arm64, M4 Mac Mini)
• Session runs inside tmux 3.6a, accessed via mosh 1.4.0 through Tailscale, from iOS (Termius client)
• Plugin: telegram@claude-plugins-official v0.0.1 (bun 1.3.11)
• The MCP server process (bun) remains alive throughout — it's the notification delivery that stops, not the server itself

Expected behavior

Channel notifications should continue to be delivered to the session for the lifetime of the MCP server connection.

Workaround

/reload-plugins restores delivery immediately.