[maxmad64bis]

Stacked on #13657. Only the last commit is this PR's scope; rebase onto the release base once #13657 lands.

Summary

When the first pass stops early, some accounts were never tried. This change spends them exactly once, within a single 90-second deadline, then drains like #13657. If none is left it drains directly. Only this PR's last commit is in scope.

Related Issues

• Related to fix(sse): stop retry wave on rate-limited 429 and drain 429 once #13657 (base of this stack).
• Related to question: Cannot use Claude Code or OpenCode — all providers return 429 rate limit #9611 (free-tier IP-based limits; rotation never avoids paying).
• Related to fix(sse): rotate opencode accounts on transient 5xx #12975 (same-upstream resume after a transient 5xx/cut).

Validation

• Change type: provider
• Focused tests and category gates from the golden path
• npm run lint — clean on the touched files; the full run is red on the base (inherited, out of scope)
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

Tests Added Or Updated

• tests/unit/opencode-rate-limited-classify.test.ts extended (wave stop, retry visits untried accounts only, drain carries both headers; 11 tests green with the 9 from fix(sse): stop retry wave on rate-limited 429 and drain 429 once #13657).
• Gates rerun on merge-base: typecheck:core clean, targeted eslint clean, file-size OK, new-code complexity green.

Coverage Notes

Same health gate as #13657; no new persisted state. The retry relays the latest upstream Retry-After (headers re-read, no body read).

Reviewer Notes

• Retry storm is bounded by construction (one pass, untried-only, deadline-bounded). Rollback is one revert on top of fix(sse): stop retry wave on rate-limited 429 and drain 429 once #13657. Rebase at fix(sse): stop retry wave on rate-limited 429 and drain 429 once #13657 merge.
• Date-form Retry-After is accepted and normalized by the same parser, so no format falls through.

[diegosouzapw]

Thanks for pushing on the 429 handling. After reworking #13657 with the maintainer, nothing from this branch remained valid on its own: the retry pass over untried accounts either repeated what the default cross-account wave already does, or (with the early-stop flag on) cancelled the stop the operator had just chosen, and it counted any non-429 status as a success, swallowed network errors and ignored the client abort signal.

What was worth keeping — the rate-limited 429 classifier and returning the last real upstream 429 with its body and headers intact — landed through #13657 under your authorship. Closing this one as consolidated into #13657.