fix(dashboard): register shell hooks on serve/dashboard startup

[5018fhxk]

Problem

serve / dashboard are not in _AGENT_COMMANDS = {None, "chat", "acp", "rl"}, so the CLI-side register_from_config in _prepare_agent_startup (main.py) never runs for the desktop backend. The gateway path registers hooks explicitly (gateway/run.py), but cmd_dashboard has no such call.

Result: the desktop app silently runs WITHOUT any pre_tool_call hooks — even when hooks are configured and allowlisted in cli-config.yaml. That kills every hook-based guardrail for desktop sessions: budget gates, command danger filters, memory routing, skill-creation gates. Hook failures are invisible (no error, no log) — the hooks just never fire.

Fix

Mirror the gateway (gateway/run.py): register declarative shell hooks in cmd_dashboard before start_server, with accept_hooks=False (non-TTY backend → only allowlisted hooks register; consent prompts never fire). Registration failures are logged at debug level and never block startup — same policy as the gateway.

Tests

• test_cmd_dashboard_registers_shell_hooks — cmd_dashboard calls register_from_config exactly once with accept_hooks=False
• test_cmd_dashboard_hook_registration_never_blocks_startup — a failing registration still reaches start_server

Both pass; test_serve_command.py + test_dashboard_lifecycle_flags.py (10 tests) still pass.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #69832 — both implement the same cmd_dashboard shell-hook registration call with accept_hooks=False for the serve/dashboard startup gap.

[Enough1122]

AI code review — automated review for reference, author can ignore or act on any point.

fix(dashboard): register shell hooks on serve/dashboard startup

Fills a real gap (desktop backend running without pre_tool_call hooks); the tests pin the contract well. Observations:

1. Allowlisted hooks must be TTY-safe in a headless backend. With accept_hooks=False only allowlisted hooks register — but the desktop backend has no console for interactive confirmations. Worth verifying each allowlisted pre_tool_call hook (budget gate, danger, memory routing, skill gate) degrades fail-safe without a TTY (e.g., no prompt-then-hang on the danger gate) rather than assuming the interactive CLI path's behavior.
2. Failure is logged at DEBUG. The registration is wrapped so failures never block startup, but the failure is reported at logger.debug — the exact silent-absence-of-hooks regression this PR fixes would again be invisible at default log levels. Since a misregistration is a silent behavioral regression, logger.warning would make a recurrence diagnosable.
3. Double-registration / placement. The call sits unconditionally in cmd_dashboard before start_server, which also covers the interactive hermes dashboard browser surface. If register_from_config is not idempotent and any future path registers hooks again in the same process, hooks could be registered twice — worth confirming idempotency (or that no other code path in this process calls it).