[BUG] Telegram plugin MCP server does not auto-reconnect after Mac sleep/wake or network drop — requires manual /mcp

Summary

The Telegram plugin's MCP server (plugin:telegram:telegram) does not automatically reconnect after the Mac sleeps/wakes or after the network drops and returns. The connection stays dead until I manually run /mcp to reconnect.

Environment

• Platform: macOS (Darwin 25.5.0)
• Shell: zsh, terminal: Ghostty
• Plugin: plugin:telegram:telegram (MCP server)

Steps to Reproduce

1. Start a Claude Code session with the Telegram plugin connected and working.
2. Let the Mac go to sleep (or drop off WiFi) for a while.
3. Wake the Mac / reconnect to the network.
4. Incoming Telegram messages are not received; the server is silently disconnected.

Expected Behavior

After wake or network restoration, the MCP server should detect the dropped connection and re-establish it automatically (with backoff/retry), without manual intervention.

Actual Behavior

The connection stays down. I have to manually run /mcp each time to reconnect (Reconnected to plugin:telegram:telegram.).

Impact

Telegram messages sent while disconnected are missed entirely (the Bot API exposes no history/search), so the gap is silent and easy to miss.