Add evaluated visual verification routing and model harness#7
Draft
theclaymethod wants to merge 3 commits into
Draft
Add evaluated visual verification routing and model harness#7theclaymethod wants to merge 3 commits into
theclaymethod wants to merge 3 commits into
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
Artifacture needs empirical evidence before assigning visual verification to a smaller model or increasing screenshot batch size. The corpus is now useful for seed development and contract testing without pretending synthetic fixtures are enough to qualify production routing.
Explicit limitations
Validation
npm test— 89/89 tests passednpm run ve:eval— 180 seeded violations, 7 clean fixtures, and 9 design-system cases passednpm run ve:checknpm run check:manifests