Repository navigation
Retain stock coordinator detach after the final snapshot - #39
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.
When the stock coordinator disconnects after its final state update, the host now records a bounded
detachevent in its private journal. The pre-Arm qualifier can reject that recorded invalidation without waiting for another snapshot. The record contains a closed refusal code, and the existing coordinator generation fence prevents old-stream cleanup from detaching a replacement session.Validation: 117 portable seed controls passed, including terminal invalidation refusals. A fresh Release build passed with zero warnings/errors and all eight actual controlled gRPC cases passed. Seven compiler-input and PE/PDB source joins were accepted through a separate read-only SDK directory-alias proof supplement. The original qualification attempt remains failed; no successful compiled phase was replayed or original verdict rewritten. Routine eligibility and operation-boundary fixtures passed (59 claim-generation cases).
Compiled implementation:
2e332259c5db590be63bb628e6c4de4b3c8e2291. The final commit changes only the owning-plan documentation; compiled source bodies remain identical. Actual native seed, browser Arm, requested-unit acceptance, publication and installed adoption remain pending; useful play is 0/6.