Repository navigation
fix: reject immutable causal receipt conflicts terminally - #4361
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
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.
A changed
execution-causal-admission/1fact already fails the schema-14 immutable guard, but the receipt drain previously classified that exact failure as storage unavailable and left an accepted receipt pending. The scoped drain now classifies the immutable error as terminalsemantic-conflict. A fresh changed receipt becomes rejected, exact replay returns the same rejection, and the original canonical declaration and accepted receipt remain unchanged. Unknown kinds still fail parsing before a durable receipt exists.The focused CLI regression covers the receipt path and preserves the receiver plan's distinction between source-built, generic local evidence and packed or installed qualification. The first focused run restored and built successfully but its test host aborted before executing tests because roll-forward was disabled for the installed .NET patch. A fresh test-only run against the same pinned build passed both named causal CLI tests (2/2); it performed no restore or rebuild. The original aborted result remains retained.
This source repair does not install a receiver, enable producer emission, or establish native collector provenance.