Repository navigation
feat: route accounts by service tier safely through fallback - #847
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes the closed #827 because its source fork does not allow maintainer edits. Preserves the original service-tier routing constraint before account acquisition can downgrade the request to default; both no-account and retry-exhaustion API-key fallback paths now remain fail-closed for restricted requests. Adds integration coverage for tier downgrade followed by 429/account exhaustion (API-key fallback prohibited) and for unrestricted requests (API-key fallback remains available).\n\nValidation:\n-
ode ..\..\node_modules\vitest\vitest.mjs run tests/integration/proxy-handler.test.ts: 40 passed.\n-
px tsc --noEmit: passed.\n- git diff --check: passed.\n- Full CI pending.