Repository navigation
Conversation
added 9 commits
September 29, 2026 21:41
roodboi
marked this pull request as ready for review
September 30, 2026 07:56
This was referenced Sep 30, 2026
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.
When a host reboot removes a retained graph’s temporary publisher and startup-control directories, ordinary cleanup cannot establish their ownership and refuses recovery. This change adds explicit, selection-bound cleanup for that verified absence while preserving named data and original graph history. Ordinary startup and cleanup remain strict.
The selected original Owner and host inspection are bounded, private inputs. Recovery reserves the foreground lock before acquiring the Engine lease, rechecks exact Owner/boot/share/volume identities, and records durable intent before any startup or bridge effect. Cleanup confirmation and publisher retirement remain separately recorded and verified. Foreign, stale, replaced or pending evidence refuses without adoption. Legacy receipts still cannot establish original physical-volume continuity across a host reboot; the acknowledgement and output state that limitation.
Recovery also explicitly unlocks the VM flock on scope exit, including failure, so inherited descriptors cannot retain it after completion. The regression holds a duplicate descriptor across success and error. Test fixtures now use exclusive directory creation and atomic sequences after a same-timestamp collision was reproduced under parallel execution.
Validation at
571862cc:The native fixture uses synthetic prior-host-boot metadata and no shared source. A real retained post-host-reboot graph also completed this cleanup with
stopped-data-retainedand unchanged provider Owner bytes. Shared-source translation, normal application restart, retained app-marker readback and signed-in browser acceptance are separate remaining gates. No Event Agent source/config changes or release publication.Base: protected
next. Includes the pending provider/host-identity recovery prerequisites; coordinate their merge before narrowing this diff. Release intent:fix, explicit recovery only.