Repository navigation
Add reusable HTTP MCP/backend campaign read checks - #248
Merged
Merged
Conversation
12 tasks done
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.
Adds a reusable, opt-in HTTP MCP read campaign harness so future capabilities can be checked through the gateway against independent backend reads. The runner validates the released tool catalog and input schemas, uses explicit external credential profiles and typed fixture assertions, and writes sanitized, hashed evidence outside the checkout. Includes a placeholder read plan, documentation and a credential-free CI job.
Validation: 18 offline tests pass, including Unicode-escaped secrets in duplicate MCP JSON text and signed tokens in HTML-escaped links. The generic runner also completed two owned-fixture MCP/API parity checks. The current head passed hosted .NET, layout/references, public disclosure, offline harness, incident receiver/provider acceptance, and external PostgreSQL Compose checks (validation run 39389362425). Optional acceptance and release jobs were skipped by their normal workflow conditions. This is the reusable read foundation and does not claim completion of the full beta.8 campaign.
No application C# or deployed configuration changes. Private credentials, endpoint profiles, campaign captures, and fixture identifiers are excluded.