docs(api-parity): clarify checkApiParity complements apiCheck#32
Merged
Conversation
…both checkApiParity compares the two committed dumps against each other and trusts they're current; apiCheck is what verifies each dump still matches its real source. They're complementary, not redundant — a green parity check over stale dumps proves nothing. Surfaced by the engineer who built the parity gate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
Adds a short subsection to
docs/api-parity.mdclarifying thatcheckApiParity(modules agree with each other) andapiCheck(each dump matches its source) are complementary gates — keep both, since a green parity check over stale dumps proves nothing.Docs-only — skips the build gate via the new
paths-ignore.🤖 Generated with Claude Code