Repository navigation
fix: recover unpublished checkpoints without collecting again - #291
Merged
Merged
Conversation
Contributor
|
🦞👀 Pull request received. I will update this pull request when review starts. |
vincentkoc
marked this pull request as ready for review
October 17, 2026 16:32
This was referenced Oct 17, 2026
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.
What Problem This Solves
Checkpoint saves can outlive their step budget, leaving retained state unpublished even after native ingestion succeeded.
User Impact
Saves now use one shared deadline with safe phase timings. A reviewed manual recovery can verify an existing publisher checkpoint twice and publish its private archive without collecting or uploading the state again.
Why This Change Was Made
The save owner removes one redundant intermediate integrity pass while preserving pinned source facts and authenticated full-state readback. Recovery requires the original native-success/checkpoint-failure/archive-skipped evidence, a successful diagnostic, unchanged parent custody, and an archive containing no external media or embedding payloads.
Offline native export runs before any promotion. Its original producer identity is preserved, recovery provenance is recorded separately, and the verified direct-child commit is published once with an exact-parent lease. Uncertain outcomes hold without retry.
Runtime/workflow LOC: +448/-75 (net +373); tests: +522/-5. The added owner boundary is explicit retained-publisher admission and publication; no schema, collection, cloud, or scheduler change.
Evidence