Repository navigation
Finalize published EP process crash qualification - #324
Merged
Merged
Conversation
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.
Record the completed revision-26 EP-owned OI-2 process-crash subset in the existing canonical lifecycle/roadmap documents. The published 2.3.104 PURGE partial-deletion failure remains GAP_PROVEN historical evidence. The protected correction (#322) was included in exact-main 2.3.105 release source ad44263; the published wheel digest 22dd1e49... agrees with the RELEASE_COMPLETE receipt. A real partial-deletion SIGKILL on that wheel recovered the same operation to PURGED with tombstone, identical replay and unchanged sibling; all 15 PRESERVE/RESTORE/PURGE lifecycle cells passed under Python 3.14. The filesystem-only service adapter is explicitly bounded. This changes no parent OI-2 state, creates no node and claims no physical reboot or installer acceptance.