feat: expose current persisted evidence review state - #21
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Saved reviews previously appeared only in audit history while evidence reads still showed the original unreviewed fixture. List, detail, and citation-export routes now project the latest persisted review metadata by event ID using one grouped query. A subsequent disputed or human-reviewed event replaces the displayed review state without changing origin or deleting history.
Only review fields are projected; fixtures remain synthetic and excluded from citation export. With no database configured the demo still works. Configured storage failures return 503 rather than stale review state. Research gaps remain fixture-based.
Validation: local Ruff passed, pytest 30 passed / 2 PostgreSQL tests skipped; documentation audit reports zero issues and all 68 Mermaid diagrams parse. Extended PostgreSQL CI coverage checks successive statuses, backdated review timestamps, record isolation, and recovery through a fresh application instance.