Repository navigation
Release Forge 0.2.42: explicit checkpoint recovery and provider contention - #56
Merged
Merged
Conversation
ancongui
marked this pull request as ready for review
October 24, 2026 21:21
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.
A checkpoint whose remote publication outcome is uncertain can now be completed through a new, explicitly authorized native request. The original unknown request stays immutable; recovery reuses the retained AI text, checks current authority and source, and confirms the exact branch and draft review with remote revision checks.
This release also keeps later unknown publication intents visible in status, handles excluded generated caches consistently at checkpoint validation, refreshes natural-language status across lifecycle transitions, and waits for short provider contention before dispatch. Provider connection configuration is rechecked after acquiring its lock. A narrowly bounded Darwin child-reaping fix preserves genuine permission failures.
The new v9 source profile is registered with fresh native and PostgreSQL evidence. All four historical profile literals remain intact. The public version, docs, 544 screenshots and packaged Studio assets are regenerated for 0.2.42. See the release notes for the full scope.
Validation:
ghcr.io/fireflyframework/firefly-forge:v0.2.42resolves tosha256:ba3a9a7eb9241f8e948eae28aba850782f5c47939b31e5e66aa0076142cca348with exact source/revision/version labels. No image layers were downloaded.Qualification lineage is explicit: the paired native/SQL proof measures the pre-registration source. Registry adoption, public version/captures, test isolation and the separately tested SCM changes preserve all 21 loader inputs, 32 admission dependencies and 311 prompt entries. The proof is not relabeled as a measurement of later whole-source metadata.
This release does not claim complete live CRM acceptance or broad live-provider acceptance. Projects V2, the new response renderer, expanded checkpoint tools and the durable sandbox allocator are separate follow-ups.