Telegram channel MCP notifications not delivered to Claude Code session

Summary

notifications/claude/channel MCP notifications from the Telegram plugin are never delivered to the Claude Code session. The bot receives messages (typing indicator is shown), but Claude Code never processes them.

Environment

• Claude Code version: 2.1.83
• OS: Linux (WSL2)
• Telegram plugin version: 0.0.1 (cache: 0.0.4)

Configuration

• channelsEnabled: true in settings.json
• mcp__plugin_telegram_telegram__reply in permissions allow list
• Bot token valid (verified via getMe)
• User ID in allowFrom in access.json

What happens

1. User sends DM to the bot
2. Bot server (bun, MCP server) receives the message ✓
3. Typing indicator is sent to Telegram ✓
4. MCP server sends notifications/claude/channel notification via socket ✓
5. Claude Code session never receives the notification ✗

Evidence

• Socket pair between Claude Code process and MCP server exists and is connected
• Searched all session logs across all project directories — zero instances of source="telegram" found
• Issue persists across multiple Claude Code sessions
• Two MCP server instances were running simultaneously (one orphaned from a previous session) — reduced to one, but issue remains

Expected behavior

Channel message should appear in Claude Code session as <channel source="telegram" ...> tag, and Claude should respond via the reply tool.

Notes

• openclaw (separate gateway service on same machine) uses its own native Telegram integration with different bot tokens — confirmed no conflict
• No webhook configured on the bot
• pending_update_count is 0 (updates are being consumed by MCP server)