Telegram channel: support multiple bots (per-project configuration)

Feature Request

Current behavior:
The Telegram channel reads a single bot token from ~/.claude/channels/telegram/.env, shared globally across all Claude Code instances. Only one bot can be active at a time.

Desired behavior:
Support multiple Telegram bots, ideally with per-project configuration. This would allow users who run different Claude Code instances in different directories to have a dedicated bot for each project context.

Use case:
Users working across multiple projects (e.g., personal life system, work repo A, work repo B) want separate Telegram bots so messages route to the correct Claude Code session without ambiguity.

Possible approaches:

• Per-project channel config (e.g., .claude/channels/telegram/.env within the project or a project-scoped override)
• A config file that maps bot tokens to project directories
• Multiple named channel instances (e.g., telegram/personal, telegram/work)

🤖 Generated with Claude Code