Repository navigation
Compare immutable verification histories without rerunning checks - #49
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 history view now selects two saved Skill or artifact verifications and compares them without rerunning the CLI or changing the current selection, baseline, approved plan or draft. Scope/contract changes, incomplete or invalid evidence stay unavailable rather than becoming zero changes.
Fresh-baseline and saved-history Skill comparisons share the evidence-pairing classifier. A bounded projection sends counts and at most 32 code/reconciliation rows, with no raw messages, paths or cells. Early width checks precede schema parsing; read concurrency stays bounded.
Validation: 755 tests passed with one optional Docker reference skipped; types, lint and build passed. Native browser/API checks compared saved reports with their source directory offline, refused different scope, retained unrelated input, kept six stored files unchanged, did not invoke the CLI and rejected a missing session marker. No deployment or npm release.