Repository navigation
Fix repair workflow after rechecks and retain execution results - #11
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
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.
Rechecking from a problem, undoing a fix, or continuing after installation could clear the repair plan and leave no usable repair entry. This change generates a fresh reviewed plan after those flows and keeps a visible retry entry for failed previews, while invalidating stale plans and requiring a new audit after an unknown execution outcome.
Execution receipts now retain failed-step reasons and recovery guidance across rechecks. The home page shows the actual watchdog restoration notes and avoids duplicate region recovery buttons. Version 0.24.1 keeps the existing minimal desktop layout.
Validation: 677 Python tests (5 platform skips), 16 JavaScript tests, full JavaScript syntax and publication checks; isolated Windows/macOS workflow tests cover expiry without writes, preview errors, failed audits, denied OS/file writes, installation continuation, undo, and watchdog restoration with readback and logs. Independent code review completed. Browser regression and native packaging checks also run in CI. All fixtures leave production settings unchanged.