konsisumer 6fda92aa7f fix(gateway): bridge top-level require_mention to Telegram config ... Users commonly place `require_mention: true` at the top level of config.yaml alongside `group_sessions_per_user`, expecting it to gate Telegram group messages. The key was silently ignored because the config loader only checked `yaml_cfg["telegram"]["require_mention"]`. When `require_mention` is found at the top level and no telegram-specific value is set, the fix now: - adds it to platforms_data["telegram"]["extra"] so _telegram_require_mention() picks it up via the primary config.extra path - sets TELEGRAM_REQUIRE_MENTION env var for the secondary fallback path A telegram-specific value (telegram.require_mention) still takes precedence over the top-level shorthand. Also corrects telegram.md: bare /cmd without @botname is rejected when require_mention is enabled; only /cmd@botname (bot-menu form) passes. Fixes #3979		2026-05-03 16:59:46 -07:00
..
developer-guide	feat: final platform plugin parity — webhook delivery, platform hints, docs	2026-04-29 21:56:51 -07:00
getting-started	feat(gateway): restart manual profile gateways after update	2026-04-30 20:00:31 -07:00
guides	docs: two-week gap sweep — platforms, CLI, config, TUI, hooks, providers (#17727)	2026-04-29 20:32:37 -07:00
integrations	docs: resync reference, user-guide, developer-guide, and messaging pages against code (#17738)	2026-04-29 20:55:59 -07:00
reference	fix(kanban): add per-path env overrides + dispatcher env injection	2026-05-03 15:13:39 -07:00
user-guide	fix(gateway): bridge top-level require_mention to Telegram config	2026-05-03 16:59:46 -07:00
index.md	docs: publish llms.txt and llms-full.txt for agent-friendly ingestion (#18276)	2026-04-30 23:17:14 -07:00
user-stories.mdx	docs(website): add User Stories and Use Cases collage page (#18282)	2026-04-30 23:56:59 -07:00