Repository navigation
Preserve exact shared checkpoint history in 0.2.44 - #58
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.
Long native tool conversations duplicated the same request history in checkpoint records, so a valid six-turn conversation could exceed the encoded snapshot budget. Version 3 stores that shared history once and reconstructs the exact canonical record before hash and credential checks. Existing v1/v2 snapshots remain readable, and size and digest refusals are reported separately without exposing record text.
The source profile advances to V13 with fresh native 250-case and SQL54/24/6 proof. All eight historical profile literals and seals are preserved. The published runtime is byte-identical to the qualified 0.2.44 candidate across all 655 source inputs, including the 22 loader inputs, 35 admission modules, and 315 templates. Four test-only current-version expectations and release documentation are updated separately.
Capacity remains bounded at 192 KiB encoded, 8 MiB raw, 256 KiB per WAL envelope and 4 MiB retained checkpoint/consume evidence per run. Chunked content-addressed overflow remains pending. Core 0.2.44 intentionally retains the unchanged Studio 0.2.42 source, assets and captures.
Validation:
Merge and release remain held for final source review and all required public checks. This PR does not claim generated CRM completion or unlimited checkpoint storage.