Repository navigation
Recover verified previous-boot service generations - #19
Merged
Merged
Conversation
This was referenced Oct 7, 2026
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.
After an unclosed Linux boot, installed query and monitor services reject ready state from the previous kernel and require manual recovery. This change recovers only a fully validated generation whose supervisor and every worker identity belong to one verified previous boot. Current, mixed, missing, malformed and unknown identities remain quarantined; accepted snapshot metadata is preserved.
Validation: three focused lifecycle tests plus public query/monitor startup regressions; direct-compiler build and all 20 Meson groups pass serially. Initial suite failed an existing overflow fixture; unchanged baseline also failed. Scanner-only delay and bounded terminal observation repair the fixture without weakening eight-overflow, failure-exit or snapshot preservation assertions. Original failures are retained in the plan.
Refs #18, #5. Installation/package identity and live readback remain separate gates; no host reboot or new roots.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.