feat: add replay-verified JSON reduction - #10
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.
What changed
Why
This combines minimal failure reproduction with Evidrift's existing contract-drift evidence in one flagship developer tool. The workflows stay deliberately separate: ReproMin replays only explicit local fixtures, while
evidrift checkand MCP remain network-free.Validation
npm run verify— 89/89 tests, smoke test, and repository Receipt check passednpm run release:check -- v0.4.0npm auditagainst the official registry — 0 known vulnerabilities at test timeLimits
ReproMin does not claim a global minimum, root cause, harmless side effects, or correctness beyond the selected status plus error identity. The reproduction fixture should use synthetic data and a disposable local target.