[Feature]: Multi-profile Telegram group communication — bots don't see each other's messages

Problem

When running multiple Hermes profiles (each with their own Telegram bot token) in the same Telegram group, bots cannot see each other's messages. This is due to a Telegram API limitation: bots do not receive updates containing messages from other bots.

This prevents multi-agent collaboration scenarios where multiple Hermes profiles (or other bots) operate in the same group chat and need to be aware of each other's responses.

Repro

1. Create two Hermes profiles (e.g. default and latent), each with its own Telegram bot token
2. Add both bots as admins to the same Telegram group
3. Have one bot send a message
4. Observe: the other bot never receives the update — Telegram API simply doesn't forward bot messages to other bots

Expected Behavior

A mechanism for Hermes agents to be aware of messages from other Hermes profiles (and potentially other bots) in the same Telegram group, enabling coordinated multi-agent conversations.

Suggested Approaches

1. Shared Telegram bot token — All profiles share a single bot token, with internal routing via @mentions or message prefixes. This bypasses the Telegram limitation since messages from the single bot appear as "user" messages from the bot's perspective. The gateway would need to filter/route messages to the appropriate profile.

2. Cross-profile pub/sub — Each profile publishes its outgoing messages to an internal bus (in-memory or file-based). Other profiles subscribed to the same group chat consume these messages and inject them into their own session context. This creates a virtual shared conversation state.

3. Bridge proxy profile — A dedicated lightweight profile acting as a "router" in the group. All other profiles communicate through it via internal delegation (delegate_task or similar), and the router handles group chat interaction using a single bot token.

Technical Context

Each Hermes profile runs an independent Telegram platform adapter (gateway/platforms/telegram.py) with its own python-telegram-bot Application instance, polling/getUpdates independently. The TELEGRAM_BOT_TOKEN is set per-profile in their respective .env files.

Looking at gateway/platforms/telegram.py, there's currently no mechanism for cross-profile message sharing or shared update handling.

Additional Notes

• This is a Telegram API limitation (bots don't receive other bots' messages), not a Hermes bug
• Workaround: setting Group Privacy → Disable in BotFather allows bots to see all human messages, but still NOT other bot messages
• The feature would unlock multi-agent orchestration scenarios in group chats