Preserve learning data through validated backups and system file export - #5
Merged
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.
WordAI could preserve progress inside one installation but had no way to export it or review a restore before replacement. This adds a bounded learning snapshot, a confirmation flow, and native system-file saving for Android and iOS. Restoring keeps earned progress and answer history, closes unfinished rounds, and prepares fresh questions next round.
The format uses explicit field allowlists, strict identity/reference checks and a 32 MiB actual-byte limit. Capture reads one SQLite transaction; replacement writes one transaction, with disk-backed trigger tests for rollback after partial work. Startup sample seeding is now atomic and only runs for an empty profile, so refreshes and later launches preserve a restored vocabulary.
Android acceptance uses an API 35 emulator, the real document picker and synthetic providers, including blocked writes and late callbacks. iOS has a signing-free simulator build check. Widget coverage includes confirmation, safe errors, disposal during async work and large text; manual Flutter render review checks the light and dark layouts.
Native CI results are required before merge. These tests do not establish physical-device coverage, power-loss durability or cloud-provider synchronization. Backups are readable JSON, omit credentials/settings/audio, and cannot extract data from an older installation signed with another key. Development APK distribution still uses debug signing.