Repository navigation
Conversation
zibi-pplx
added this pull request to stack #768
October 21, 2026 07:56
zibi-pplx
force-pushed
the
codex/compatible-restore-consumers
branch
from
October 21, 2026 13:40
5b6835b to
b24a8ec
Compare
zibi-pplx
changed the title
zibi-pplx
removed this pull request from stack #768
October 21, 2026 13:44
zibi-pplx
added this pull request to stack #779
October 21, 2026 13:45
zibi-pplx
force-pushed
the
codex/compatible-restore-consumers
branch
from
October 21, 2026 13:51
b24a8ec to
d4872f5
Compare
…nance Restore prefers the snapshot producer when allowed and usable, then selects a qualified compatible loader without requiring boot-kernel files or rewriting the snapshot manifest. Save the exact consumer before effects and resolve each new attempt from immutable producer evidence. Exact requests never silently upgrade, and adding an allowed environment does not change a usable source. Document policy defaults, cohort rollout constraints, independent policy freshness and the difference between revocation and lifecycle retirement. A failed restore can leave a consumer recorded for a later exact stop/start. Resident-VM incident handling and incompatible upgrades are separate work: preserve matching disk/checkpoint rollback data and require explicit memory-loss consent; retention never permits a revoked runtime. Validation: affected libraries compiled offline on the updated stack; focused policy, cold-selection and restore tests passed. Restore and protocol regressions are included; database integration, full tests and KVM validation remain with CI.
zibi-pplx
force-pushed
the
codex/compatible-restore-consumers
branch
from
October 21, 2026 13:52
d4872f5 to
92481ec
Compare
This branch has not been deployed
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.
Restore prefers the snapshot producer when allowed and usable, then selects a qualified compatible loader without requiring boot-kernel files or rewriting the snapshot manifest. Save the exact consumer before effects and resolve each new attempt from immutable producer evidence. Exact requests never silently upgrade, and adding an allowed environment does not change a usable source.
Document policy defaults, cohort rollout constraints, independent policy freshness and the difference between revocation and lifecycle retirement. A failed restore can leave a consumer recorded for a later exact stop/start. Resident-VM incident handling and incompatible upgrades are separate work: preserve matching disk/checkpoint rollback data and require explicit memory-loss consent; retention never permits a revoked runtime.
Validation: affected libraries compiled offline on the updated stack; focused policy, cold-selection and restore tests passed. Restore and protocol regressions are included; database integration, full tests and KVM validation remain with CI.