Repository navigation
Release Forge 0.2.43 with durable checkpoint continuation - #57
Merged
Merged
Conversation
ancongui
marked this pull request as draft
October 25, 2026 02:12
ancongui
marked this pull request as ready for review
October 25, 2026 04:43
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.
Checkpoint continuation could fail after dependency installation or as accumulated model/tool history grew. This release allocates command slots durably, restores fully completed canonical command receipts, compresses checkpoint history losslessly within an explicit 8 MiB raw bound, and streams canonical Git source identity independently of runner transport archives. Tracked source remains included even when ignored; generated ignored dependencies retain their separate transport rules.
Source listing and text search now return explicit continuation pages, while complete manifests hash every eligible file. Stable tracked deletions and deletion-only command changes retain their provenance. The release also stages full branding assets with a compact context, retains nine granted static tools and frozen design descriptors, preserves verified GitHub delivery links, and binds maintenance lifecycle/questions/owner answers to an exact native creation receipt. Backend 0.2.43 keeps the unchanged Studio 0.2.42 assets and captures.
Validation: