feat(olympus): add Telegram routing on live-compatible Hermes baseline

[chadsm-sys]

Scope

Supersedes #17 as the Telegram child of live-compatible release-binding PR #18. Cold and active gateway paths now dispatch canonical /olympus commands while preserving active work and the existing base-adapter command bypass.

Exact candidate

• Head: 9c16fb0416018a9a091ebf1d95d5648a32557046
• Logical parent/integration base: feat(olympus): bind authority on live-compatible Hermes baseline #18 28df8559346b2a267ca8e105e90bde767767556c
• Child delta: 11 Telegram/Olympus routing and regression paths.
• Gateway dispatch slice: 107 passed.
• Complete 66-test authority/router file: 10 consecutive stress passes (660 test executions) after aligning only the synthetic verifier clock with the production integer request clock.
• Cross-store crash/reopen/replay: PASS against Mission Control Receiving API errors when messaging through Telegram and using Nous Portal auth NousResearch/hermes-agent#28 b6512e3820b38cb8a2a593e97ee7e5efd0801dd6.
• Remediation-range Gitleaks and diff check: PASS.
• Hosted: run 29345807433 passed at this exact head: 21 success, 8 skipped, 0 failed.

The automated hyphenated-board-slug comment is a closed false positive; valid canonical slugs intentionally permit hyphens.

Boundary

Review only. No merge, deployment, migration, restart, activation, production Telegram routing, external send, credential change, production mutation, or live-runtime edit is authorized.

Olympus v1 final-candidate binding

• Current exact head: 57ff300bec5effed73efcfd4e36b102246a11642
• Current exact base: e10d5c83f23a8297c9b7fb3d9bb6130467927645 on codex/M-20260714-olympus-pr19-attested-base
• Current base-relative diff SHA-256: 6188ed0ec8ce5e89da6d912b412f341a45f617fcc1e3262a9b54e14c210772ed
• Governance packet: /Users/macmini/Hermes-Handoff/M-20260714-olympus-authority-remediation/release-preparation/20_FINAL_GOVERNANCE_DECISION.md through 28_FINAL_EVIDENCE_INDEX.md
• Status: governance decision required; this binding is not merge authorization.
• Supersession: any older head/base SHA or review-thread status in this description or prior release evidence is historical and non-authoritative.
• Drift rule: any head change invalidates this binding. Any base change requires final-diff/check/review revalidation before merge.
• Review policy: operator must explicitly select Path A (strict independent human review) or Path B (one-release personal-lab exception, which does not count as independent human review).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ae7cd65fe8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".