Summary

Telegram channels are not readable yet even when the bot is a channel admin, because the adapter appears to poll all Telegram update types but only registers handlers for normal messages/media/commands, not channel_post / edited_channel_post.

Current behavior

Observed in the local Hermes setup:

• Bot was added as admin to a Telegram channel
• New channel content was still not ingestible/readable in Hermes
• The channel did not appear in the local channel directory

Repo inspection suggests:

• polling uses allowed_updates=Update.ALL_TYPES
• but the Telegram adapter only adds handlers for:
  • text messages
  • commands
  • location
  • media
• there is no explicit channel_post / edited_channel_post handling path

Relevant files:

• gateway/platforms/telegram.py
• ~/.hermes/channel_directory.json only showed the DM, not the channel

Expected behavior

If the Telegram bot is an admin in a channel, Hermes should be able to ingest new channel posts and route/store them similarly to other inbound Telegram events.

Suggested direction

Minimal fix would likely require:

1. explicit handling for channel_post and probably edited_channel_post
2. translating those updates into the normal internal MessageEvent flow
3. persisting the channel in directory/session routing so later delivery/inspection works consistently

Why this matters

Right now channel IDs can be known/configured, but Hermes still cannot actually read channel content, which makes Telegram channels only partially supported in practice.