fix(cli): accept launcher flags after dashboard command

[OmarB97]

Summary

• accept known global Hermes launcher flags when they are placed after the subcommand
• cover the official desktop launch shape (dashboard ... --tui) so the backend does not exit before readiness

Root cause

The packaged macOS desktop app launches the backend as hermes dashboard --no-open ... --tui. --tui is a global option, but argparse only accepted it before the dashboard subcommand, so the backend exited with status 2 during desktop startup.

Validation

• python -m pytest tests/hermes_cli/test_default_interface_resolution.py tests/hermes_cli/test_subparser_routing_fallback.py tests/hermes_cli/test_startup_plugin_gating.py -q
• live ~/.hermes/hermes-agent cherry-pick ran the same focused tests
• direct /api/status returned gateway_running=True, gateway_state=running
• direct /api/ws probe opened and received gateway.ready
• normal /Applications/Hermes.app relaunch opened past CONNECTING into the chat shell with backend command dashboard --no-open --tui --host 127.0.0.1 --port 9120

Related

• Upstream PR: fix(cli): accept launcher flags after dashboard command NousResearch/hermes-agent#39108
• fix(bootstrap): re-seal installer after copying to ~/.hermes on macOS #76 is still separate and still needed for macOS bootstrap installer re-signing; it is not the cause of this backend argparse failure.

[github-actions]

🔎 Lint report: fix/macos-desktop-backend-startup-fork vs origin/main

ruff

Total: 0 on HEAD, 0 on base (➖ 0)

🆕 New issues: none

✅ Fixed issues: none

Unchanged: 0 pre-existing issues carried over.

ty (type checker)

Total: 9842 on HEAD, 9842 on base (➖ 0)

🆕 New issues: none

✅ Fixed issues: none

Unchanged: 5105 pre-existing issues carried over.

Diagnostics are surfaced as warnings — this check never fails the build.