What does this PR do?

Makes /busy available on gateway platforms so Telegram/Discord/Slack users can inspect or change busy-input behavior without switching back to the local CLI.

Related Issue

Fixes #18362

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

• remove the CLI-only restriction from /Users/leongong/Desktop/LeonProjects/worktrees/hermes-agent/hermes-18362-gateway-busy-command/hermes_cli/commands.py so /busy is advertised to gateway clients
• add /Users/leongong/Desktop/LeonProjects/worktrees/hermes-agent/hermes-18362-gateway-busy-command/gateway/run.py::_handle_busy_command() to read, update, and persist display.busy_input_mode
• allow /busy to run even while an agent is active, without interrupting that run
• add gateway tests in /Users/leongong/Desktop/LeonProjects/worktrees/hermes-agent/hermes-18362-gateway-busy-command/tests/gateway/test_busy_session_ack.py covering config writes and mid-turn handling

How to Test

1. uv run --frozen --extra dev pytest -q -o addopts='' tests/gateway/test_busy_session_ack.py tests/cli/test_busy_input_mode_command.py
2. uv run --frozen ruff check hermes_cli/commands.py gateway/run.py tests/gateway/test_busy_session_ack.py tests/cli/test_busy_input_mode_command.py
3. In gateway mode, run /busy, then /busy queue or /busy steer, and confirm the mode changes without interrupting an active run

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 15

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

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

• uv run --frozen --extra dev pytest -q -o addopts='' tests/gateway/test_busy_session_ack.py tests/cli/test_busy_input_mode_command.py -> 25 passed
• uv run --frozen ruff check hermes_cli/commands.py gateway/run.py tests/gateway/test_busy_session_ack.py tests/cli/test_busy_input_mode_command.py -> All checks passed!