Repository navigation
feat(desktop): add verified Restore and recovery workflow - #163
Merged
Merged
Conversation
…d target identity
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.
Phase 8 — verified Restore and recovery
preview_restoreand gatedexecute_restoresidecar commands. Preview verifies manifest/file hashes, exact target identity, and a separate safety-backup location; execution revalidates all of these and requires exactRESTOREconfirmation bound to a preview token.restore_verified_backupimplementation, which creates a verified safety backup before replacement and attempts recovery from it if restoration fails. The UI reports success/recovery state and warns when manual recovery may be required; it never auto-retries or auto-resumes.