fix: restore capacity after banked reset - #197
Merged
Merged
Conversation
- treated fresh positive usage as authoritative reset evidence - preserved hard fences against older concurrent observations - retained zero usage snapshots as advisory
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
1 participant
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.
Banked resets restore quota without moving the natural reset deadline. CQ retained the earlier hard 429 fence until that deadline, so a reset account remained unroutable until proxy restart.
Fresh authenticated usage refreshes now publish positive capacity as ordered authoritative evidence. Newer positive evidence lifts the older hard fence; zero snapshots remain advisory, and usage requests started before a newer hard limit cannot clear it.
Validation: