Keep optional A2A card absence unknown for HTTP APIs - #202
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
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.
AG preflight cautioned Coppice’s ordinary HTTP
/api/vetendpoint solely because its optional A2A agent card returned 404. For a responsive HTTP endpoint with no applicable protocol probe, an absent card now remains unknown. Only reachability is scored; protocol, payment and task execution remain unverified.Existing malformed or unsigned cards still receive their checks. Missing cards on A2A endpoints and unreachable endpoints remain failures; the observed-MCP exception is unchanged.
Validation: the new regressions reproduced three false cautions before the fix; all 125 preflight, MCP transport and paid-evidence tests pass after it. Contract generation has no drift, and the diff check passes.