feat(installer): persist verified GPT artifacts through retained directories - #120
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.
GPT capture and restore currently operate on memory buffers. Add an internal filesystem primitive that creates a digest-named backup exclusively through a retained private directory, syncs the file and directory, then reopens and verifies the exact artifact. Interrupted and existing files are preserved; unsafe files, changed inodes, corrupt bytes and revoked checks fail closed.
The disposable VM qualification uses a separate ext4 root disk and covers four cancellation and child-process exit checkpoints, fresh-descriptor recovery, duplicate creation, unsafe file types/metadata, chunk cancellation and caller input mutation. Both 512-byte and 4096-byte sector runs passed with unchanged target/canary evidence. Independently extracted the stored file from the stopped VM disk and confirmed its digest, root ownership, 0600 mode and single link.
Validation:
bun install,bun run verify, strict C compilation, nine QMP runner tests, and both complete local VM lanes after syncing with develop. CI retains source-bound qualification reports.This is an uninstalled internal candidate for #20. Production backing-storage policy, locking/backend composition, journal integration, hardware power-loss testing and physical media qualification remain outstanding; this does not close #20.