[codex] Persist Hermes API server config before gateway startup

[FFFergie]

Summary

• persist Hermes API server settings with hermes config set before Clawket cold-starts hermes gateway run --replace
• keep the existing process env injection so the immediate spawned gateway still receives API_SERVER_*
• add a regression test that verifies config persistence happens before gateway startup

Root Cause

Clawket only passed API_SERVER_ENABLED, API_SERVER_HOST, and API_SERVER_PORT through the spawned gateway process environment. If Hermes launchd/service or a competing --replace startup became the surviving gateway process, that process could start without the API server enabled. The bridge and relay stayed connected, but chat send failed later when the bridge fetched http://127.0.0.1:8642/v1/runs and nothing was listening.

Validation

• npm run --workspace @clawket/bridge-core build
• npm run --workspace @clawket/bridge-runtime typecheck
• npm run --workspace @clawket/bridge-runtime test -- --run src/hermes.test.ts -t "persists Hermes API server config"

Note: full src/hermes.test.ts was not used as the final signal in this local environment because a real Clawket bridge was listening on the default 4319 port and local Hermes model config affected existing model-list assertions.