Repository navigation
fix(recovery): verify current checkpoint custody on readback - #275
Merged
ebarti merged 6 commits intoNov 1, 2026
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.
Checkpoint readback could advertise an old acknowledgement as resumable after the run budget, owner, workspace, candidate branch, index, evidence or session content changed. Check current facts under existing resource/writer custody, preserve the original acknowledgement, and keep restore as the authoritative admission boundary.
Retained evidence uses opened files without following links, bounded reads, and revalidated metadata and parent identity. Missing reconstructible files remain eligible for restore. Changed, inaccessible or unverified existing state produces a blocker and is preserved; strict retained verification keeps its missing-file refusal.
This is a bounded contribution to #239. The integrated recovery scenario uses real local Temporal with a fixture provider and controlled remote/effect boundaries. Complete native descendant settlement, real-provider continuation and integrated running pause/resume remain open under #242 and #245. No active installation or delivery was changed.
Validation of unchanged integration tree
8e29a2898fea5c4f330b3e714875bf46a52c2bee(current headc8f7f581b783ad3692817a99358572fe5edc0b07), based on #276: