feat(validation): persist review evidence and routing#91
Merged
Conversation
Add typed validation-review results, responsive screenshot evidence, root-controlled cyclical transitions, migration backfill, and deterministic regression coverage. Co-Authored-By: OpenAI Codex GPT-5 <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Jul 14, 2026
Infer the fixture return type so the validation evidence slice does not depend on the later Eve reviewer context module. Co-Authored-By: OpenAI Codex GPT-5 <noreply@openai.com>
ncolesummers
marked this pull request as ready for review
July 16, 2026 15:27
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.
Summary
loopworks.screenshot_evidence.v1and typed validation-review result contractscommit,development, andtest-writingroutes only through the root transition boundaryWhy
Issue #49 needs a deterministic evidence boundary before an LLM reviewer can run. This base slice establishes the durable contracts, validation capture lane, and root-controlled transition policy without yet adding the Eve sibling runtime.
Stack
Merge in order. Later PRs use the preceding branch as their base and can be retargeted to
mainafter each dependency merges.Validation
bun run validatebun run buildbun run test:e2e:validation-evidence— 66 responsive/browser/a11y cases across 390x844, 1280x832, and 1440x960Part of #49.
Co-authored with OpenAI Codex (GPT-5).