Repository navigation
feat: expose declared cross-file checks in artifact reports - #26
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
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.
Artifact reports now show the validated cross-file declarations and inspection limits alongside actual outcomes. Reviewers can inspect CSV summaries, reference bindings and keyed integer reconciliation without reopening the contract; scalar expected values and raw cells are omitted. Missing files retain the declaration list, invalid setup cannot infer one, and legacy baseline reports remain accepted.
HTML caps declarations at 128 and visible mappings at eight per declaration. Version 0.3.0 includes an original synthetic fixture for all three check kinds.
Validation: 650 tests passed, one existing opt-in Docker test skipped; types, lint, build and actual npm archive installation passed. The installed CLI generated a three-check report; a real offline browser flow passed at 390 px with zero axe violations and zero external requests. GitHub distribution remains distinct from npm registry publication.