feat(gateway): make Telegram command-menu cap configurable

[fnoor1]

What & why

The Telegram bot-command menu (set_my_commands) is capped at MAX_COMMANDS_PER_SCOPE = 30 per scope to stay under Telegram's undocumented ~4KB setMyCommands payload limit. The menu is built in priority order — core commands → plugin slash commands → skill commands (skills trimmed first). When core + skill commands fill the 30 slots, plugin/profile slash commands get trimmed and never reach the "/" menu. They still work when typed, but aren't discoverable.

Concretely: a profile-router plugin that registers /finance, /trend, etc. via ctx.register_command(...) has its commands silently omitted from the menu on instances with many core/skill commands — getMyCommands returns 30 with none of the plugin commands.

Change

Make the cap configurable via telegram.menu_max_commands (read from the platform extra config, clamped to Telegram's documented 1–100), defaulting to the existing MAX_COMMANDS_PER_SCOPE (30) so behavior is unchanged unless opted in. Both registration sites honor it:

• startup all-scopes registration (connect())
• lazy per-forum-scope registration (_ensure_forum_commands())

telegram:
  menu_max_commands: 50   # 1..100; default 30

A new _coerce_int_extra helper mirrors the existing _coerce_bool_extra (invalid/missing → default, with optional clamping).

How to test

Set telegram: { menu_max_commands: 50 } in config.yaml, run a plugin that registers slash commands, restart the gateway, and confirm getMyCommands lists them. Unit tests added in tests/gateway/test_telegram_menu_cap.py cover: default, override, string-encoded int, clamp-high (→100), clamp-low (→1), and invalid (→default).

scripts/run_tests.sh tests/gateway/test_telegram_menu_cap.py

Platforms tested

Linux. Pure config read + clamp — no OS-specific code paths.

🤖 Generated with Claude Code

[teknium1]

Thanks for the focused Telegram menu-cap work. This is an automated hermes-sweeper review; current main already implements the requested behavior through a broader, documented configuration surface.

• hermes_cli/commands.py:600-642 reads and safely clamps platforms.telegram.extra.command_menu.max_commands to Telegram's 1..100 range.
• plugins/platforms/telegram/adapter.py:2936-2945 uses that value for startup registration, and plugins/platforms/telegram/adapter.py:7483-7487 uses it for lazy forum-scope registration.
• Commit dbe14ce35d9cb087ae9fe3e3f166f6c475297e25 implemented the configurable cap and priority support, explicitly salvaging related PR feat(gateway): configure Telegram command menu priority #42021; d4be583d986f7bcca4f8414fd21ef9e34b18c948 raised the default cap to 60. Current tests at tests/hermes_cli/test_commands.py:1337-1391 cover defaults, overrides, invalid input, and clamp bounds.

Closing as implemented on main.