fix(gateway): respect explicit Telegram disabled when TELEGRAM_BOT_TOKEN is set

[keiravoss94]

What does this PR do?

Telegram matched Slack's bug: TELEGRAM_BOT_TOKEN always forced enabled: true, so telegram.enabled: false / platforms.telegram.enabled: false was ignored. This mirrors the existing Slack _enabled_explicit pattern so users can keep the token for tools/cron while leaving the gateway adapter off.

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• gateway/config.py — tag platforms.telegram / top-level telegram.enabled as explicit like Slack; only auto-enable from env token when disable was not explicit
• tests/gateway/test_config.py — regression tests for explicit Telegram disable with token present

How to Test

1. uv run pytest -o addopts= tests/gateway/test_config.py -k telegram -q
2. Set TELEGRAM_BOT_TOKEN and platforms.telegram.enabled: false in config — confirm the Telegram gateway adapter does not start
3. Omit explicit disable — confirm token still auto-enables Telegram as before

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

N/A — delete this section otherwise.

Screenshots / Logs

N/A

[teknium1]

Thanks for the focused regression fix. This is an automated hermes-sweeper review; current main already provides the requested behavior.

• gateway/config.py:1108 records explicit enabled configuration for every platform, including Telegram.
• gateway/config.py:1436-1457 uses _enable_from_env() for TELEGRAM_BOT_TOKEN; an explicitly disabled platform remains disabled while the token is retained.
• gateway/config.py:2132-2144 also prevents the plugin auto-enablement pass from re-enabling an explicitly disabled platform.
• gateway/run.py:7020-7024 skips disabled platforms during adapter startup.
• This generalized fix shipped via d682f320b35a13084371a541a835e1d988c982b8 and is contained in v2026.7.1. It also addresses the same plugin-platform disablement class discussed by the linked PRs fix(gateway): respect explicit plugin platform disables #31665, fix(gateway): respect explicit platform enabled:false in YAML config #35562, and fix(gateway): respect disabled telegram config #36014.