feat: add Hermes as a second executor family (backend + CLI)

[plutoless]

Summary

Adds Hermes (Nous Research) as a first-class detached executor family, peer to Codex, driven over Hermes's TUI Gateway JSON-RPC stdio app-server. V1 is core run loop only: create session → submit prompt → stream progress → settled answer → cancel → follow-up.

• New hermes/ adapter (probe, jsonrpc peer, gateway client, session, executor) emitting the generic ExecutorEvent stream — no Codex multi-message-turn coupling.
• Gateway launched as the Hermes project venv python -m tui_gateway.entry; workspace set via TERMINAL_CWD at spawn, so gateway processes are keyed by working directory and multiplex sessions by params.session_id.
• Single terminal message.complete selects COMPLETED / CANCELLED / FAILED via payload.status; approval.request/clarify.request → terminal BLOCKED. Follow-ups use session.steer only (no prompt.submit fallback). Gateway crash/EOF and a timeout_seconds liveness bound both surface as observable FAILED (no silent hangs).
• Capabilities: supports_follow_up + supports_cancel; supports_pause/supports_resume/supports_thread_list false.
• Single source of truth newbro/executors/families.py::SUPPORTED_EXECUTOR_FAMILIES, aliased by runtime/config.py::SUPPORTED_DETACHED_EXECUTOR_TYPES and referenced by the registry (now validates family membership), both CLI parsers (top-level + detached node), and interactive setup.
• CLI: newbro executor probe/use --executor hermes, install-hermes, --enabled-executor hermes, and executor setup writes the executors.hermes block.
• Docs: docs/protocol/hermes-gateway.md (+ real captured fixture), docs/architecture/executors.md, docs/memories.md.

Out of scope (follow-on plan): macOS menu-bar app changes (single-choice executor selector, per-family probe state) — spec §6. Also deferred: Hermes thread import, skills, audio, resume, interactive approval/clarify response wiring.

Design spec: docs/superpowers/specs/2026-06-09-hermes-second-executor-design.md
Implementation plan: docs/superpowers/plans/2026-06-09-hermes-second-executor.md

Test Plan

• pytest full suite green (747 passed)
• ruff check clean on new hermes/ adapter + touched CLI
• Discovery fixture captured against live hermes v0.12.0
• Unit tests: event mapping (progress/completed/cancelled/failed/blocked), no-fallback follow-up, cancel→interrupt, gateway-EOF→FAILED, timeout→FAILED, registry family validation, both CLI parsers, interactive setup, executor_settings probe/use/install
• Manual: run a real hermes executor node end-to-end and drive a Bro turn

🤖 Generated with Claude Code

[plutoless]

Update — operator-facing Hermes support added to this branch

Since the original adapter, this branch now also includes:

Web UI

• Hermes is selectable in the create/connect-a-Bro agent-client picker (was a hardcoded "Coming soon" gate); single-select, family passed into createExecutorNode. Fixed a follow-on where auto-issue-on-mount locked the picker.

CLI

• executor run --enabled-executor hermes runs config-free when hermes is on PATH (readiness defaults an unconfigured family command to its own name).
• newbro executor install-hermes runs the vendor installer (install.sh) defensively (stdin /dev/null, bounded timeout), resolves ~/.local/bin/hermes; auth (hermes setup --portal) stays manual.
• probe --executor hermes --json carries a best-effort authenticated field (hermes auth list).
• PROBEABLE_EXECUTOR_FAMILIES = (codex, hermes); ACPX is run-only (probe/use reject it; no more silent codex payload).
• Local config writers enforce the single-family node invariant (single-element enabled_executors).

macOS menu-bar app (spec §6)

• Per-family probe state (probeByFamily/statusByFamily) with scoped per-family refresh (Codex and Hermes are separate Settings panes; each Refresh probes only its family).
• Family-aware start diagnosis: Hermes missing → Set Up (install-hermes); present but unauthenticated → Sign-in prompt (hermes setup --portal); authenticated/undetermined → ready (mirrors Codex login-required; nil never blocks).
• No-fallback single-choice executor picker in the profile editor (Save gated on an explicit family).
• Sign-in and install-failure surface as informational text / streamed log — no Terminal launcher.

Specs/plans: docs/superpowers/specs/2026-06-09-hermes-second-executor-design.md, …-hermes-macapp-and-cli-design.md (+ matching plans). Two design rounds + grilling.

Verification: pytest 760 passed; swift test 125 passed; feature files ruff-clean. A final opus code review flagged 4 functional defects (set-up-then-start not resuming, scoped refresh not re-deriving diagnoses, Hermes status row, post-install PATH resolution) — all fixed and re-verified.

Out of scope / follow-ups: web picker no-fallback parity; Hermes thread import / skills / audio / interactive approval wiring.

[github-actions]

Vercel preview is ready.

https://newbro-o3nwwhjpd-agora-devx.vercel.app