fix: reconcile active prepared replacement cutover (#242) - #279
Merged
Merged
Conversation
This was referenced Sep 26, 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.
Closes the #242 control-plane gap reproduced during the live M5 HerdR cutover.
A coordination-bound cutover in PREPARED state already has exact current/expected identity, immutable carrier authority, and an approved finish pair. If an external bounded deployment replaces the process with the exact expected source/build/capability while the carrier is still valid, current main unnecessarily rejects terminal finish until expiry even though the same exact observed-replacement path is supported after expiry and in the legacy path.
This change permits only that exact active case:
Verification on exact head 7d427d9:
Refs #242. Does not grant deployment/merge/acceptance authority.