Repository navigation
fix: preserve accepted conflicting version evidence - #9
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
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.
Conflicting accepted Next.js versions previously collapsed to identical reports: 16.4.0/16.4.1 and 16.3.0/16.4.2 lost their exact candidates. Retain bounded validated observed_version on each evidence source, project it in HTML and CSV/JSON, and align schema, methodology, examples and generated standalone/checksums. Conflicts remain unknown with exploitability=not_tested; malformed, qualified and URL-shaped raw input stays excluded.
Validation: 91 offline synthetic unit tests pass (4 Windows platform skips), build consistency check, actual CLI help, synthetic HTML example generation and git diff --check pass. Regression cases cover distinct conflicting pairs, per-source association across all formats, mixed invalid/valid evidence and schema rejection of unsafe values. No target scans or runtime execution. Hosted CI and actual final-head Copilot review remain merge gates.
Fixes #7