Repository navigation
Conversation
added 14 commits
September 29, 2026 21:41
roodboi
marked this pull request as ready for review
September 30, 2026 09:01
Contributor
Author
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.
A retained shared-source graph still names its prior host filesystem device after explicit post-reboot cleanup. Ordinary restore refuses that mismatch. This adds a selection-bound source-device witness so the same run can restore while preserving its original stopped receipt, cleanup proofs and named volumes.
The witness requires exact completed absent-publication cleanup and retirement, current Owner/guest/share identity, and verified retained volumes. It projects only the device in memory and remains pinned through the first new-attempt write. Later ordinary generations use current source ownership; historical witnesses grant no authority. Pending or changed inputs refuse and are preserved. Exact-current cleanup now takes precedence over older enrollment records only after committed historical live/dead cleanup, bridge selection and unresolved-effect checks pass. Legacy physical volume continuity remains explicitly unproven.
Validation at 9da7305: default Rust suites 951 passed / 62 ignored; all-feature suites 1,037 passed / 84 ignored; default and all-feature/all-target strict Clippy, formatting and privacy passed. All eight exact-head CI checks pass. The signed native fixture passed: same-run marker preservation, two ordinary restart cycles, live host source edits reaching the guest, immutable history and verified owned VM/home/alias disposal. The prior device in that fixture is synthetic.
A real retained application accepted the source witness without changing its stopped receipt, Owner bytes or VM boot. Whole-application restart remains a separate gate: its legacy unbranched namespace differs from current named-branch review. No application source/config edits, merge or release publication.
Base: protected
next. Depends on #103 and its identity-recovery prerequisites; coordinate those merges before narrowing this diff. Release intent:fix, explicit opt-in recovery only.