Conversation
Track each candy window's resets_at epoch separately from the stable key so a missed utilization dip (sleep/quit across reset) still grants.
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
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
resets_at, leavingcandyGrantTierstuck at 1 (5 hours limit reached multiple times but no candy's are awarded to my bag #326).claude.fiveHour, …) and persistcandyWindowEpoch[key]fromresets_at/ Codex unix / AntigravityresetTime. A changed epoch clears the tier so a fresh 100% can grant again.Fixes #326
Type of change
UI changes
resets_at) rearms candy even when utilization stays at 100% across the gapChecklist
swift buildandswift testpass locallyTest plan
swift test --filter 'RareCandy|CandyGrant|SaveTransferTests'(79/79)testRearmWhenWindowEpochAdvancesWhileStillAt100RED; restored → GREEN