test(platform): qualify installed update recovery - #365
Open
Mat4m0 wants to merge 40 commits into
Open
Conversation
Mat4m0
changed the title
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.
What changed
Windows now builds an immediate prior signed Squirrel package and proves failed-update recovery, forward replacement, credential continuity, and rollback. Linux builds two GPG-signed Flatpak commits and proves failed-update recovery, upgrade, rollback, and profile continuity. The Linux gate also exercises encrypted per-profile secrets through GNOME Keyring and KDE Wallet.
Why
A package that starts once is not enough evidence for a safe platform rollout. Updates and rollback must preserve the launcher workspace and isolated credentials, and a broken feed must leave the installed application usable.
Invariant
The exact installed package remains on the prior deployment after a failed update, advances only to the signed candidate, and can return to the prior package while reading the same profiles. Synthetic credentials remain isolated; no real player directory or credential is used.
Delivery
This is the top qualification layer of stack #364. Merge after PR #363. Do not publish a release from this PR. Production signing credentials remain a protected release boundary.
Verification
pnpm run checkpnpm buildfocused update and package policy tests
exact Windows and Linux package jobs in GitHub Actions
I kept this pull request focused.
I ran the relevant checks.
I did not add game binaries, credentials, diagnostics, or private traffic.
I updated documentation when behavior or an invariant changed.