Telegram plugin: inbound messages consumed but never delivered to conversation (Windows)

Bug description

The Telegram channel plugin (plugin:telegram@claude-plugins-official) receives inbound messages from Telegram (confirmed via getUpdates returning empty — updates are consumed by the plugin's grammy polling), but notifications/claude/channel MCP notifications are never delivered to the active Claude Code conversation.

Outbound works perfectly — telegram__reply sends messages to Telegram successfully. Inbound is silently swallowed.

Steps to reproduce

1. Start Claude Code with --channels plugin:telegram@claude-plugins-official
2. Verify plugin starts (bun process running, tools available)
3. Send a message from Telegram to the bot
4. Message is consumed (getUpdates returns empty) but never appears in the Claude Code conversation

Environment

• Claude Code version: 2.1.81
• OS: Windows 11 Pro 10.0.26200
• Shell: PowerShell + bash
• Plugin version: telegram@claude-plugins-official 0.0.1
• Bot token: valid (getMe succeeds)
• Access config: allowlist policy, sender ID matches

Diagnosis

• getUpdates confirms messages are consumed by the plugin (not sitting in queue)
• getWebhookInfo shows no webhook blocking polling
• Plugin's handleInbound() calls mcp.notification({ method: 'notifications/claude/channel', ... }) — this call appears to succeed (no error logged to stderr)
• Claude Code's MCP notification handler does not route the notification into the conversation
• Calling Telegram MCP tools directly (reply, react) works — the MCP connection is alive
• Plugin is lazy-loaded (only starts when a tool is first called), but even after starting, inbound notifications don't arrive

Related issues

• #36431
• #36472
• #36503

Same symptoms reported on macOS. This confirms the bug exists on Windows as well.