fix: route Op Admiral through connected agent and resume approvals

[jmagly]

Summary

• route keyless Op Admiral planning through the connected local agent (including Hermes)
• preserve approval receipt IDs across Full Auto retries and resume automatically after the requested receipt is approved
• add regression coverage for connected-agent selection and receipt-aware retry behavior

Root cause

The Op Admiral configuration path did not consult the connected local-agent selection and could fall back to Codex. Separately, Full Auto discarded the receipt returned by the approval gate, so later attempts could not present the approved receipt and minted a new one.

Impact

Hermes users can plan operations without a local Codex binary, and Full Auto now progresses through the existing scoped approval gates after operator approval. The backend continues to validate every receipt ID against its action and target.

Verification

• npm test — 60 test files / 644 tests passed; 11/11 ops-preflight checks passed
• npm run typecheck
• git diff --check

Closes: #104