fix Hermes local bridge auth and history ordering

[macournoyer]

Summary

• Resolve Hermes API server keys for local bridge commands from --api-key, CLAWKET_HERMES_API_KEY, API_SERVER_KEY, HERMES_API_KEY, or ~/.hermes/.env.
• Pass Hermes bridge/API secrets to detached child runtimes through env instead of argv.
• Merge native Hermes history with local bridge history by de-duplicating local messages and sorting by timestamp, so locally-recorded user prompts are not dropped when native history already has the assistant response.

Validation

• npm run --workspace @p697/clawket test -- src/index.test.ts
• npx vitest run packages/bridge-runtime/src/hermes.test.ts -t "keeps local user prompts ordered before newer native assistant replies"
• npm run bridge:typecheck

Notes

npm run --workspace @clawket/bridge-runtime test -- src/hermes.test.ts also ran the new history-ordering test successfully, but the full workspace src test invocation failed in this local checkout on unrelated environment-dependent tests: port 4319 was already in use, and model/provider assertions picked up the current local Hermes provider state.