Add real API consumer fixtures for coordination acceptance - #3
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.
The previous coordination exercise paired an API with a static brochure site, so its client could not demonstrate compatibility. Add dependency-free API and actual HTTP client fixtures with declared suites, plus an external pair verifier for exact worked commits.
The verifier checks positive/fractional/negative results and removal of the old endpoint. Sensitivity controls reject the unchanged pair and an API-only rename; a matching pair passes. This prepares a valid live exercise and does not claim that the coordination has completed.
Validation: both fixture suites; real HTTP pair and negative controls; lint; 1,411 runtime tests. Script suite initially lacked this worktree's web dependency metadata; restoring that dependency link made the failed deployment-package check pass (remaining 99 checks passed, one existing skip).