Repository navigation
fix: preserve foreign live lanes during stack capture - #177
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.
Capturing a lane's commits could mark it captured before checking its lease, then remove another owner's active checkout. Keep foreign lanes with live or unverified leases unchanged while recording the intended stack ownership, and name the owner in the kept-lane diagnostic.
Apply the same protection under the registry lock before ledger recovery, moved-path repair and pending cleanup in stack add, capture and classify. Same-owner capture and explicit release/GC retain their existing behavior. Update the guides, including removal of a residual raw-push fallback suggestion.
Validation: 11 regression fixtures verify registry, lease, checkout files/modes, index, branch and recovery refs, including a moved pending lane and an interrupted release. Existing lifecycle/preflight regressions and 12 module/documentation checks pass. Version 0.47.19; independent review READY on the exact head. Merge requires 20/20 CI.