fix(gateway): preserve stream flood-backoff accounting

[chadsm-sys]

Live-compatible stream successor

Preserves the approved live gateway/stream_consumer.py flood-backoff behavior and its two regression tests. No Anthropic adapter, lockfile, credential, routing, authority, migration, or production-runtime change is included in the child delta.

Exact candidate

• Head: 52b8b465b32897b270df1ee0554f295b6428ffeb
• Logical parent/integration base: feat(olympus): add Telegram routing on live-compatible Hermes baseline #19 9c16fb0416018a9a091ebf1d95d5648a32557046
• Child delta: gateway/stream_consumer.py and tests/gateway/test_stream_consumer.py; 113 insertions, 1 deletion.
• Integrated CI/gateway/stream slice: 381 passed, including 124 stream-consumer tests.
• 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 29345816694 passed at this exact head: 21 success, 8 skipped, 0 failed.

Boundary

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

Olympus v1 final-candidate binding

• Current exact head: e45689c5df583142cd717adcdfeb82b38754334f
• Current exact base: 57ff300bec5effed73efcfd4e36b102246a11642 on codex/M-20260714-olympus-pr20-attested-base
• Current base-relative diff SHA-256: 5a777fc6f3227fa9150804027802c08db0b1bc7366c0c2a8d50b53ec3d1aeb88
• 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).