Repository navigation
Validate optional documents through package discovery - #629
Merged
Merged
Conversation
3 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
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 standalone documents validator and registers it for generic
check-packagesdiscovery. Findings identify the DOCS rule, severity and record file; undeclared repositories do not run documents validation. The version contract explicitly preserves two-part numeric strings and accepts full SemVer without normalizing stored values.Verification covers npm-packed installation, DOCS-001–007 positive and negative cases, core validation before and after package removal, byte-identical undeclared validation, and coexistence with ReqIF. Generic package tests, ReqIF integrity, ingest pipeline integrity, notation lint and 115 notation/release tests pass.