Reduce stored record size with opt-in reference sharing - #31
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.
Repeated input and freshness references can dominate the size of stored Result and Evidence records. Add opt-in reference sharing within each record while restoring the original logical JSON before validation, hashing, and workflow decisions.
The CLI supports inspection, verification, dry runs, resumable migration, export, and migration back to plain JSON. Existing projects keep their current format until explicitly migrated. Storage operations use cooperative locks and atomic publication, including the existing Windows replacement behavior. Schemas, role instructions, and user documentation describe the compatibility and rollout requirements.
Release candidates now accept a unique release ID so updated binaries can be published without replacing an existing release tag. Regression coverage checks versioned candidate generation and rejects unsafe identifiers.
Validation: repository regression suite, format and Clippy checks, storage round trips, migration interruption and reversal, CLI/MCP continuity, and release/bootstrap checks. Native platform builds will also run in the release candidate workflow.