Repository navigation
Fix toolkit correctness across cleanup, DNS, recovery and repair - #6
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.
The 3.0.0 toolkit could reject fresh privacy backups, delete Windows.old despite describing it as report-only, enforce an incorrect Quad9 IPv6 address, lose worker errors, and report success after failed repair/restore commands. This audit repairs those paths across the dashboard, all five consoles, shared modules and all 12 launchers before adding more features.
Recovery now preserves exact registry types/case, verifies AppX backup hashes before registration, handles Recall's post-reboot state, rejects linked state/cleanup paths, and guards originating-account elevation. Preview includes reviewed selections; reviewed-only runs work. Component patch versions, README, changelog, audit reports and bounded optional diagnostics are updated.
Validation: 407 local Windows PowerShell 5.1 STA assertions across six suites, 43 parsed PowerShell files, real WPF/jobs/native-process checks, all launcher success/failure paths and rendered dashboard inspection. CI runs canonical and friendly layouts. First-party action pins already match latest releases. Open Dependabot/code-scanning/secret-scanning alerts: 0 at push.
No live optimization, DNS changes, servicing, app removal or restore-point creation ran. Those mutation APIs are intercepted in fixtures; interactive UAC and performance gains are unverified. No new public release is published by this PR. Detailed coverage and limits: docs/AUDIT_2026-10-10.md and VALIDATION_REPORT.md.