test: exercise terminal Todo source witness on v3 wire - #4958
Merged
Merged
Conversation
Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>
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.
The terminal Todo lifecycle request now uses wire v3, but its authority-source test still invoked v1. On current
main, that case fails at the schema check before it can verify the registry witness requirement.This updates the test to reject v0–v2 explicitly and exercises malformed
registry_sourcevalues on the current v3 wire with the required operation identity. It changes no runtime behavior and restores the test's intended authority-boundary coverage.Validation: the focused Node test passes all 6 cases;
git diff --checkpasses; LoopX premerge runs 3 selected canaries with no failures; exact-scope quality receiptcqr_6548048f55b9932202d1is valid. Global CI is pending. The related product journey in #4945 remains independently reviewable; this PR only fixes a baseline test failure.