[costaeder]

Summary

• classify Antigravity 429 responses with reset after 0s as transient rate limits
• preserve durable quota cooldowns for explicit non-zero quota reset windows
• add a regression test covering the zero-reset response

Why

Cloud Code can return an exhausted-capacity message with reset after 0s for burst/RPM throttling. Classifying it as quota exhaustion sends the account into the durable cooldown path unnecessarily.

Test plan

• targeted antigravity-429-quota-cooldown unit test

[diegosouzapw]

Heads-up: this PR is running against a stale base

release/v3.8.49 has moved 116 commits ahead of the base this PR was last built against, and several gate failures that were red on the older base have since been repaired on the branch itself:

Gate class	Repaired by
No new ESLint warnings (exit 2 — orphaned suppressions, not a lint violation)	#8706, #8831
Fast Quality Gates / check:file-size / Quality Ratchet	#8585, #8767, plus the post-merge-train re-pins
Docs Gates (fast-path) (missing Polish API_REFERENCE)	#8831
backoff-clamp + compressionDetailNormalizers unit tests	#8706

I verified this on a clean checkout of the current tip (3b515d90b3): lint:json --max-warnings 0, check:file-size, check:docs-sync, error-classification.test.ts (24/24) and check-db-rules.test.ts (22/22) all pass with no changes.

Currently failing here:

• Lint
• Quality Gates (Extended)
• Quality Ratchet

Please update the branch (the Update branch button, or rebase onto origin/release/v3.8.49) and let CI re-run. That should clear any failure caused by the stale base.

Note this is not a promise that every red disappears — a failure specific to the changes in this PR will survive the rebase, and Build (advisory) is advisory and does not block. Rebasing just removes the noise so what is left is actually yours.

No action was taken on this PR beyond this comment.

[diegosouzapw]

Re-homed to release/v3.8.50: v3.8.49 entered its release freeze, so the branch now belongs to the release captain and development continues on the next cycle. Nothing is wrong with this PR — it just needed a live base. No action needed from you; CI will re-run against the new base.