fix: preserve prioritized Telegram menu commands

[cortanapham]

Summary

• Preserve configured Telegram menu priority before applying the Telegram command cap.
• Let gateway skill command collection gather all candidates when prioritization needs to happen globally.
• Add regression coverage for a priority skill command surviving an otherwise-full menu.

Tests

• venv/bin/python -m pytest tests/hermes_cli/test_commands.py::TestTelegramMenuCommands -q -o 'addopts='
• venv/bin/python -m pytest tests/hermes_cli/test_commands.py -q -o 'addopts='

[tonydwb]

LGTM. Clean 2-file fix preserving prioritized Telegram menu commands. Prevents command ordering from being lost during sync. Well-scoped with tests.

[teknium1]

Thanks for the focused regression fix. The premise is confirmed on current main: hermes_cli/commands.py:916-923 limits skill collection before the combined list can be priority-sorted, and :926 caps that un-reprioritized result. The proposed global ordering addresses that path and the added skill-under-cap regression test covers it.

Problems

• hermes_cli/commands.py:897-902 still describes a fixed core → plugin → skill ordering. After this change, a configured-priority skill can be promoted ahead of those categories before the cap, so that contract becomes stale.

Suggested changes

• Update that docstring to describe priority application over the combined eligible command list before truncation.

Automated hermes-sweeper review.

[teknium1]

Fixed on main by #98280 (commit 3e6229e) — same priority-before-cap idea you submitted first; see the credit note on #57938. Thanks @cortanapham!