Repository navigation
Conversation
This branch has not been deployed
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.
Diagnostic only; DO NOT MERGE. Based on authoritative PR #92 exact source
6b5d31d47db0a07f3eb565dbb93bd5cf97ffe051. Test-first adversarial restore-path regression: a validly re-fingerprinted legacy backup containing NTFS alternate-data-stream syntax, DOS reserved device names, or Windows wildcard names must fail closed before stage creation on every platform. This RED commit intentionally contains no source correction. Confirm failing Ubuntu/Windowsrelease:validateevidence, then implement the narrow path-validation fix and rerun both platforms. Do not port to PR #92 until both full platform validations pass. No Windows physical power-loss evidence or independent approval implied.