Keep selected profile usage refresh current#254
Open
andrei-hasna wants to merge 1 commit into
Open
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
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.
Summary:\n- let the selected or root auth profile refresh usage metadata even when its cached usage snapshot is still fresh\n- keep ordinary request interval and failure backoff plus non-selected freshness suppression unchanged\n- add regressions for selected refresh throttling, sparse rolling snapshot preservation, and configured Ordered first-unknown behavior\n\nValidation:\n- focused codex-tui tests for all three changed behaviors passed\n- just fix -p codex-tui passed\n- just fmt passed\n- staged and exact-range gitleaks scans passed; no Co-Authored-By or private-key markers\n- two independent final adversarial reviews passed\n\nKnown baseline:\n- just test -p codex-tui executed 3354 tests and found seven snapshot drifts in unrelated existing permissions, terminal header, model picker, prompt suggestion, empty submission, full input, and small-height snapshots\n- this PR changes none of those source or snapshot files; generated snap.new files were rejected and are absent from the diff\n\nScope:\n- three TUI files, 101 additions, 12 deletions\n- no protocol/schema, reset-generation state, Ordered selection rewrite, publish, deployment, or E2B change