Repository navigation
Release ACC v1.0.6 reference-risk correction - #15
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.
The reference checker previously returned low for GET with explicit execution.readonly:false and omitted risk.level, contrary to the existing OpenAPI binding. This release preserves explicit false, retains the original 26 vectors, and expands coverage to 48 vectors with a complete 24-case risk-precedence matrix.
No ACC Core semantics, schema rules, declaration family, or CLI source change. Existing published evidence indexes and guidance are retained and updated for the new corpus. The repository lockfile updates fast-uri 3.1.8 to compatible 3.1.9 after the existing audit gate identified upstream advisories; direct dependency ranges are unchanged.
Validation: npm ci; npm audit --audit-level=low (0 vulnerabilities); npm run check (48 vectors, 24 tests); normal npm pack; clean tarball installation and CLI valid/JSON/strict-invalid smoke tests; consumer audit (0 vulnerabilities). The npm version alignment is not a runtime security fix, and the checker result is not deployment certification.