Fixed
- HTTP 529 (Service overloaded) now triggers failover — when an upstream provider returns 529, the router previously passed the error straight to the client instead of failing over to the next model in the priority chain. Clients like OpenCode saw
unknown [retrying attempt #3]because every retry hit the same overloaded upstream. 529 is now part of the retryable status set ([429, 500, 502, 503, 529]) so it cascades to the next model, matching the behavior of 429/500/502/503 in both the streaming and non-streaming code paths. (Fixes GitHub issue #148)
Tests
- 799/799 tests passing, including two new regression tests covering 529 failover for non-streaming and streaming requests (priority-1 model returns 529 → request succeeds via priority-2 model).