Telegram channel plugin: notifications/claude/channel silently ignored in remote-control sessions

Description

The official Telegram channel plugin (telegram@claude-plugins-official v0.0.4) sends notifications/claude/channel MCP notifications that are silently ignored by Claude Code v2.1.87 in remote-control spawned sessions. Messages from Telegram reach the plugin, polling works, mcp.notification() resolves successfully — but the spawned session never receives or logs the notification.

Environment

• Claude Code v2.1.87 (latest as of 2026-03-30)
• Jetson Orin NX, Ubuntu 20.04 ARM64
• Plugin: telegram@claude-plugins-official v0.0.4
• Bun v1.x (plugin runtime)

Steps to reproduce

1. Install and configure the Telegram plugin (/telegram:configure, pair a user)
2. Start claude remote-control --name "Test" --spawn same-dir
3. Verify the spawned session connects MCP to the plugin (debug log shows MCP server "plugin:telegram:telegram": Successfully connected)
4. Send a message to the bot from Telegram

Expected behavior

The spawned session receives the channel notification and responds to the Telegram message.

Actual behavior

• Plugin receives the Telegram message (typing indicator appears in chat)
• Plugin calls mcp.notification({method: 'notifications/claude/channel', params: {...}}) — resolves successfully
• Spawned session debug log shows zero channel-related entries — only heartbeats
• Session transcript (bridge-transcript-*.jsonl) remains empty
• No response is sent to Telegram
• After ~70–220s of inactivity, the pre-created session dies (UNKNOWN connection closed)

Debugging done

• Confirmed plugin polling works (409 Conflict on manual getUpdates)
• Confirmed gate() passes (added process.stderr.write instrumentation — logs "gate passed, delivering")
• Confirmed mcp.notification() resolves without error (instrumented .then() — logs "notification sent OK")
• Confirmed MCP transport is connected (hasTools: true, server connected in 370ms)
• Notification goes over stdio from plugin → Claude Code, but Claude Code has no handler for it

Additional notes

• The plugin README and docs reference a --channels plugin:telegram@claude-plugins-official flag for claude remote-control, but this flag does not exist in v2.1.87 (Error: Unknown argument: --channels). This suggests channel support may be incomplete or unreleased.
• The plugin works correctly as an MCP tool provider (tools like telegram__reply are available in spawned sessions), but the inbound notification path is broken.