lsm / neokai / 28137825013

82%

Build Type

push

github

Committed by web-flow

Commit Message

fix: map HTTP 529 to overloaded_error in all provider bridges

* fix: map HTTP 529 to overloaded_error in all provider bridges

Today every bridge routes status>=500 to generic api_error, so upstream
HTTP 529 (overloaded) lands there. The overloaded_error type exists in
shared/error-envelope.ts but was never emitted by any bridge.

The Claude Agent SDK retries overloaded_error with the correct
retry-after cadence, whereas api_error retries with generic backoff.

Add a 529 → overloaded_error branch before the status>=500 fallthrough
in all three bridges:
- openai-responses-bridge (Codex/gpt-5.5 path)
- openai-chat-bridge (custom OpenAI endpoints)
- anthropic-messages-bridge (GLM/Kimi/OpenRouter pass-through)

Add a regression test for each bridge verifying a 529 upstream is
classified overloaded_error.

* fix: map HTTP 529 to overloaded_error in Ollama bridge

The Ollama bridge (ollama-bridge-server.ts) has the same status-mapping
pattern as the other three bridges but was missed in the initial change.
The acceptance criteria requires 'a 529 from any provider is classified
overloaded_error'.

Add the same 529 → overloaded_error branch before the status>=500
fallthrough, plus a regression test.

Coverage Stats

11363 of 16393 branches covered (69.32%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 4 files covered. (100.0%)

26 existing lines in 4 files now uncovered.

95298 of 113573 relevant lines covered (83.91%)

300.64 hits per line