Fix settings persistence and usage reliability in 0.6.1 - #17
Merged
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.
Settings were lost whenever the extension restarted, and several data paths could report misleading usage or silently lose local state. Version 0.6.1 persists preferences before service startup, reports the restrictive quota window and true fallback measurement age, publishes limits independently of token scans, shares gap-aware forecast rules, and handles invalid history and failed saves/deletions explicitly. Tests now inject isolated storage.
Validation: all 132 tests passed on ARM64 for 0.6.1. The preceding implementation passed all 132 tests and trimmed Release publication on both ARM64 and x64. CI validates the release version and Store package matrix. Read-only integration preflight confirmed manifests and runtime layout; actual activation/restart of this new build remains unverified because the current user runs the Store installation.
No package identity, publisher, capabilities, or release workflow changes. This PR prepares the Store submission; Store availability depends on Microsoft certification.