--channels name mismatch: server registers as telegram but CLI expects tagged style

Bug: --channels notification name mismatch in v2.1.80

Description

When using --channels plugin:telegram@claude-plugins-official, the CLI correctly requires the tagged style (plugin:<name>@<marketplace>) but the internal notification system compares against the untagged server name (telegram). This causes all channel notifications to be silently skipped.

Steps to Reproduce

1. Start Claude Code with:

``
claude --channels plugin:telegram@claude-plugins-official
``

1. CLI outputs: Listening for channel messages from: plugin:telegram@claude-plugins-official (looks OK)
2. Send a message to the Telegram bot
3. Message never arrives in the session

Expected Behavior

Messages from the Telegram bot should be pushed into the session.

Actual Behavior

Messages are silently dropped. The MCP log shows:

{"debug":"Channel notifications skipped: server telegram not in --channels list for this session"}

The server registers with name telegram, but the --channels list contains plugin:telegram@claude-plugins-official. The string comparison fails.

Root Cause

The CLI requires tagged style for --channels input (e.g., plugin:telegram@claude-plugins-official), but the notification matching logic compares against the server's self-reported name (just telegram). These never match.

Using the untagged style (--channels telegram) is rejected by the CLI:

entries must be tagged

So there is no working style: tagged is required but doesn't match; untagged matches but is rejected.

Environment

• Claude Code version: 2.1.80
• OS: Windows 11 Pro 10.0.26200
• Plugin: telegram@claude-plugins-official
• Runtime: Bun v1.3.11

Workaround

None found. The channel feature is unusable for the Telegram plugin on v2.1.80.