validation: final destructive flash transaction hardening - #6
Closed
Zhanfg wants to merge 94 commits into
Closed
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.
Temporary validation PR for the final flash-readiness branch. Do not merge. This exists to run the normal pull_request Build + Flash safety workflows against main while preserving PR #5 as the release-review thread.
Key additions: durable pending transaction identity, write-failure verified rollback, fatal recovery evidence, late superkey staging, pending-key recovery bound to state=written + exact boot bytes, bound-restore-only unpatch, and destructive fault-injection tests.
FLASH_REVIEW_BLOCKEDremains present. This PR is not a flash/release candidate.