Fix Command Code rolling and monthly usage windows - #2466
Conversation
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: Fix Command Code rolling and monthly usage windows This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b73f4040bf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| primary: self.fiveHourWindow, | ||
| secondary: self.weeklyWindow, | ||
| tertiary: monthly, |
There was a problem hiding this comment.
Keep monthly depletion stabilization on the tertiary lane
When the optional subscription request fails after a paid snapshot, commandCodeSnapshotResolvingDepletionOnEnrichmentFailure still reads and replaces primary, but this change makes primary the live five-hour window and moves monthly usage to tertiary. Consequently, a transient enrichment failure can falsely replace valid five-hour usage with 100%, while a snapshot without a rolling window no longer preserves the depleted monthly lane at all; update that stabilization path and its Command Code quota-transition tests to operate on tertiary.
Useful? React with 👍 / 👎.
Summary
Verification
make test./Scripts/lint.sh lint-linuxcodexbar usage --provider commandcode --format json --prettyagainst a Go account