Support scoped quota data and consistent usage status - #18
Open
TheBeems wants to merge 2 commits into
Open
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Modern Codex quota categories and unusual window durations were ignored, and refresh failures could replace confirmed account data with unrelated local observations. This sprint preserves separate quota categories, retains the last confirmed measurement with its original age, and isolates persistent history by account and default category. Unidentified observations stay in memory; old unscoped history is not imported.
The Dock, dashboard, and forecasts now share one freshness policy. Stale forecasts pause while observed history remains visible. A safe diagnostics page distinguishes missing reset fields from an explicit zero and reports the running build separately from Store rollout. Account and chart data are captured atomically for rendering.
Validation: 186 native ARM64 tests passed; x64 and ARM64 Debug application builds passed without warnings. Existing test-name analyzer warnings are unchanged. Both integration preflights passed static manifest/COM/assets/runtime checks, but package registration and AppExtension discovery were unavailable in this test context. Interactive Dock/clipboard rendering and real-account behavior still require the documented isolated integration check; no package was installed and no reset was consumed. PR CI supplies the x64 test and Store-package checks.
Sprint 1 of the implementation series in SPRINTS.md. Related to #16; this adds diagnostic evidence and does not claim the original user's reset issue has been reproduced or resolved.