fix(cli): register shell hooks in hermes serve sessions by adding 'serve' to _AGENT_COMMANDS (#61806)

[webtecnica]

Summary

Shell hooks (pre_tool_call) were never registered in hermes serve sessions, allowing Desktop app / dashboard API sessions to bypass all hook policies.

Root Cause

_prepare_agent_startup() gates shell hook registration on args.command in _AGENT_COMMANDS. "serve" was missing from that set, so serve sessions never called agent.shell_hooks.register_from_config().

Change

Added "serve" to _AGENT_COMMANDS in hermes_cli/main.py.

Verification

731 serve-related tests pass.

[alt-glitch]

This was generated by AI during triage.

Related: #61806 (the issue this fixes), and competing fix PRs #57020 and #61823 for the same desktop/serve shell-hook gap. This PR takes the narrowest approach (add serve to _AGENT_COMMANDS so _prepare_agent_startup registers config hooks); #57020 registers at the tui_gateway._make_agent chokepoint (covers the serve in-memory path + has tests) and #61823 wires both entry.py and server.py. All three are open and address the same gap via different mechanisms -- a maintainer should pick the canonical one.

[teknium1]

Thanks for isolating the current-main gate: serve is indeed absent from _AGENT_COMMANDS at hermes_cli/main.py:12383, so _prepare_agent_startup() returns before register_from_config().

Problems

• The added serve entry only covers the launch-profile, in-process server. dashboard shares the same cmd_dashboard handler but remains outside _AGENT_COMMANDS; profile-scoped dashboard chats deliberately spawn tui_gateway.entry rather than attach to the in-process gateway (hermes_cli/web_server.py:14544-14547). Those paths still do not pass through this gate.
• tests/hermes_cli/test_serve_command.py has parser/headless contracts only; it does not verify configured hook registration or pre_tool_call blocking.

Suggested changes

• Re-scope registration to the agent-construction paths with explicit profile-aware behavior, covering both in-process and spawned TUI sessions.
• Add regression coverage that proves an allowlisted blocking hook fires on both paths.

Automated hermes-sweeper review.

[teknium1]

serve covers only the launch-profile in-process path. dashboard shares the handler but remains excluded, while profile-scoped dashboard chats spawn tui_gateway.entry and never reach this gate (hermes_cli/web_server.py:14544-14547). Please register at the agent-construction path(s) with profile-aware coverage instead.