Repository navigation
Conversation
added 4 commits
September 29, 2026 21:41
roodboi
marked this pull request as ready for review
September 30, 2026 06:05
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
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.
Physical host reboots can change a filesystem device number while retaining the same inodes. After explicit provider recovery, old foreground, relay-control and dependency socket pins still refuse cleanup. Add hash-selected
graph inspect-host-pin-recovery/recover-host-pinscommands that publish an immutable witness for one prior guest generation, then allow exact owned cleanup and publisher retirement without rewriting the historical pins or removing data.Recovery checks the running guest identity independently, holds and rechecks publication/control/provider locks, and binds raw receipts, unchanged paths/inodes, dead pre-host-boot processes and current retained-volume observations. Ordinary reads and successor publications stay strict. Missing temporary roots refuse; this does not reconstruct vanished ownership evidence or migrate shared-source graph identity.
Validation:
Release signal:
fix; explicit recovery only. Legacy device rebinding does not prove original physical-volume continuity. Synthetic old host-device receipts plus a real guest reboot qualify the command path; physical host reboot and full application/browser acceptance remain separate.Stack: depends on #96 and #97 and targets
next. Restack ontonextonce those parents merge. Private logs, bundles, fixture data and internal planning are excluded.