Added Hermes Agent + Codex CLI providers (multi-provider runtime support) — PR #383

[josephndex]

Hey! Big fan of this project — the HookProvider boundary is genuinely clean to extend, so I built out two more integrations on top of it: Codex CLI and Hermes Agent (an open-source agent I use daily).

Quick summary of what each one needed, in case it's useful context for review:

• Codex CLI has no hooks/plugin API today, but it writes a structured, append-only JSONL session rollout (~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl). I added an in-process tailer that reads that and re-emits it through the existing POST /api/hooks/:providerId ingress — same pipeline every other provider uses, just fed from a file instead of a live hook callback.
• Hermes Agent actually has three separate hook systems, and I initially assumed the wrong one would work (gateway hooks look the most hook-like but only fire for messaging-platform sessions, never CLI). The one that covers CLI sessions is its plugin-hook API (ctx.register_hook()), so the integration installs a small stdlib-only Python plugin and enables it via Hermes's own hermes plugins enable CLI.

Since AgentRuntime was hardcoded to exactly one provider at construction, I extended it to accept providers: HookProvider[] and run one HookEventHandler per provider, all sharing one AgentStateStore — so all three now render in the same office simultaneously, each tagged by which CLI they came from.

377 existing tests pass unmodified (proving Claude support has zero regressions), plus 42 new tests for the multi-provider routing and the two new providers.

PR: #383 — happy to adjust scope/tests/anything based on what maintainers want before merge. Thanks for building something this pleasant to extend!