Repository navigation
Prepare 0.2.45: preserve authority across durable recovery - #62
Merged
Merged
Conversation
ancongui
marked this pull request as draft
October 25, 2026 21:36
ancongui
marked this pull request as ready for review
October 26, 2026 16: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.
A worker restarting after native readmission now records recovery for its current intent or claim. An already held task can receive a missing annotation without rewriting its state or replaying work; earlier claims remain historical. Unresolved Bridge outcomes refuse before provider configuration, routing, or mode preparation, while the existing transaction checks remain in place.
The 0.2.45 source also covers finite native recovery, original model selection, current-fact issue communication, complete project/campaign pages, and streamed checkpoint admission. Original configuration snapshots, unknown outcomes, command history, spent budgets, and all historical profiles remain preserved. Future framework-knowledge work is excluded.
Validation remains separated by scope:
Fresh exact-head CI is green: Verify python, studio, documentation, container and check, plus Documentation build; PR documentation deployment is skipped. The independently reviewed Native250, 132 distinct SQL nodes, strict documentation and package proofs qualify this scoped recovery release. Actual retained-CRM repair and delivery, live external-provider quality and full product acceptance remain separate and incomplete. The later read_run_evidence/EvidenceQuery tool-contract failure and future framework-knowledge work are excluded from this PR.