Repository navigation
Preserve failed implementation changes as unverified Git checkpoints - #59
Merged
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.
An implementation can fail after the agent has changed files and every model response has already been consumed. That source previously had no supported checkpoint path. This change lets the authenticated project owner preserve it through the existing Git delivery queue, with an unverified commit and draft PR. The failed run, graph hold, task attempt and consumed responses remain intact.
The server checks the complete recorded completion chain, the latest stored source frontier, current Git consent, actor permissions, ownership and settled command/tool effects. Only supported read-only source calls may follow that frontier. It validates delivery summaries and draft references against their native receipts before each Git phase. Unknown effects remain held; historical runtime contracts are rejected.
The API, Python client and guide cover candidate review and explicit source-only consent. Current journal custody bounds remain 10,000 records/16 MiB; this PR does not remove enterprise capacity limits or authorize graph restoration.
Validation: