Keep post-condition receivers on their replay boundary - #51
Merged
Conversation
rmcdaniel
marked this pull request as ready for review
September 2, 2026 22:46
This was referenced Sep 2, 2026
Merged
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
2 participants
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.
Addresses #50\n\n## What changed\n\n- record an explicit non-condition binding when a durable step separates a receiver from an earlier condition\n- prevent stale workflow sequence metadata from rebinding post-boundary signals and updates to a completed wait\n- add both an in-memory cold-replay regression and a checked-in Avro history fixture\n\n## Evidence\n\n- reproduced on origin/main: full terminal history incorrectly returned another condition wait\n- focused replay suites: 69 passed\n- full non-integration suite: 1,302 passed, 2 skipped\n- replay corpus validation: passed with one new fixture\n- replay corpus policy tests: 54 passed\n- Ruff and mypy: passed\n- Avro regression budget: passed