feat: emit verifiable rollback evidence - #5
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.
Outcome
AgentTX 0.2.0 adds a versioned, offline-verifiable rollback receipt and evidence contract while preserving the existing transaction CLI and programmatic exports. Receipts bind transaction identity, before/after workspace state, canonical patch metadata, rollback outcome, and verifier status; tampering and conflicting output fail closed.
Scope boundary
AgentTX is a Git-worktree transaction helper and verifier. It is not an OS sandbox and cannot roll back external side effects. Dirty, ignored, untracked, interrupted-command, native-Git, and conflict limitations remain documented.
Validation
809fd289573e14c29d4b629049eb414a6c30d5e1f9a044fd7ed63c91323b9408Publication is separate from this PR. npm
agenttxremains at 0.1.0; registry ownerali110vis visible publicly, but this environment has no npm authentication andwhoamireturns 401.