Repository navigation
test: prove workflow decisions through an independent MCP client (refs #848) - #877
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.
The independent MCP client proof covered agreements but did not exercise workflow launch decisions. A Python standard-library client now discovers pending proposals through attention and approves or rejects them over both supported protocol versions.
The journey verifies exact retries, stale opposite decisions, missing and invalid authentication, routine authorization refusals, output schemas, tool errors versus JSON-RPC errors, and recovery in a fresh interpreter using retained proposal IDs. The isolated ExUnit wrapper verifies exactly one admitted run and never-attempted job, the original rejection reason, and no unrelated message dispatch. Documentation records the proof and its limits.
Validation: both protocol journeys under focused seeds 1, 12345 and 777; all five local gates; independent review. CI must pass on the updated PR head before merge.
Queues remain disabled. Retry comparison does not inject a transport failure, and client reconnection does not restart the server. #848 remains open for prompt/status/outcome journeys, actual server restart, attachments, remaining operator actions, stopping and delegation. No MCP schema or runtime behavior changes.
Refs #848.