Repository navigation
Integrate compaction and reliability checkpoint for beta.4 - #324
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.
Purpose
Integrate the requested compaction and reliability development checkpoint into dev for the next experimental beta. This is not a claim that the complete readiness specifications are accepted.
Changes
Verification
Focused compaction/workflow/configuration/backend/cancellation/upgrade tests passed during implementation. Latest shell, approval and context checks passed, along with package typechecking and staged diff checks. No database migrations or real-user installer runs are included.
Known gaps
See docs/beta-integration-readiness.md. Remaining work includes safe automatic shell approval, durable cold-restart cancellation, Windows deferred channel changes, actual multi-client CLI coverage, live-provider canaries and human/native acceptance. Release remains gated separately by build, security, artifact and platform checks. GitHub reported one high and one low default-branch vulnerability; these are not waived.