zyycnandCodex e23689ae22 fix: harden response recovery and resource bounds ...

Keep replay history within the active downstream WebSocket, rotate failed requests through the configured account scheduler, and retain only bounded response ownership metadata in Redis.\n\nRemove duplicate account retries, bound transport waits and runtime maps, defer noncritical stream persistence, and cover the recovery and timeout paths with integration tests.

Co-authored-by: Codex <noreply@openai.com>

2026-07-13 04:40:31 +08:00

..

architecture.md

fix: harden response recovery and resource bounds

2026-07-13 04:40:31 +08:00