konsisumer a4fb0a3ac3 fix(cron): route Telegram cron deliveries to a dedicated topic via TELEGRAM_CRON_THREAD_ID ... When Telegram topic mode is enabled, cron messages delivered to the bot's root DM (TELEGRAM_HOME_CHANNEL without a thread id) land in the system lobby — replies there are rebuffed with the lobby reminder and reply_to_message_id is dropped, so users cannot interact with the cron output (#24409). Add an optional TELEGRAM_CRON_THREAD_ID env var that overrides TELEGRAM_HOME_CHANNEL_THREAD_ID for cron deliveries only. Operators can create a "Cron" forum topic in the DM, point this var at its thread id, and replies to cron messages will land in that topic's existing session instead of the lobby. The home-channel thread id (used elsewhere, e.g. restart notifications) is unchanged, and explicit deliver="telegram:chat:thread" targets continue to win over the env var. Per the reporter's clarification on 2026-05-13, option (a) (cron-side route to a dedicated topic + config knob) was chosen. Fixes #24409		2026-05-18 22:36:11 -07:00
..
developer-guide	docs(session_search): update all docs for the single-shape rewrite (#27840)	2026-05-18 00:36:17 -07:00
getting-started	docs(windows): avoid piping installer directly into iex	2026-05-18 20:05:47 -07:00
guides	docs: ignore box diagrams in ascii guard	2026-05-18 20:12:00 -07:00
integrations	docs(xai): link OAuth-over-SSH guide from xAI provider surfaces (#26610)	2026-05-15 14:45:59 -07:00
reference	fix(cron): route Telegram cron deliveries to a dedicated topic via TELEGRAM_CRON_THREAD_ID	2026-05-18 22:36:11 -07:00
user-guide	fix(cron): route Telegram cron deliveries to a dedicated topic via TELEGRAM_CRON_THREAD_ID	2026-05-18 22:36:11 -07:00
index.md	docs(windows): avoid piping installer directly into iex	2026-05-18 20:05:47 -07:00
user-stories.mdx	docs(website): add User Stories and Use Cases collage page (#18282)	2026-04-30 23:56:59 -07:00