Repository navigation
feat: release replay desks through verified recovery - #180
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.
A stack could not be archived while its source branch remained checked out in a replay desk, and the refusal offered no native way to release that desk. New replay desks are now registered and shown by worktree list. Stack archive names the new stack release-desk remedy.
Release previews bind the selected desk and snapshot to a plan digest. Apply requires that digest and confirmation that writers have stopped, preserves the tip, raw index, staged and working contents in verified local recovery refs, then removes the checkout while retaining the source branch. Legacy desks require explicit path selection. Unsupported data, changed identity, active ownership or stale inputs are preserved by refusal; interrupted removals resume from their recorded intent. Writer confirmation is an operator attestation.
The worktree list path retains observational diagnostics and the journal-mode refusal. Nested release previews and applies preserve the caller's authorization context; apply uses a separate nonce only for recovery-ref publication.
Validation: 34 desk and diagnostic fixture tests passed with a minimal PATH, including staged/unstaged recovery, legacy selection, identity changes, interrupted removal, retry after Git prune, and nested authorization. Twelve module/documentation checks and the version guard passed. Independent review READY on 40ddbb4. Version 0.47.22.