Skip to content

fix: validate capture projections before persisting ownership - #178

Merged
Yehonal merged 1 commit into
mainfrom
fix/capture-projection
Nov 16, 2026
Merged

Yehonal merged 1 commit into
mainfrom
fix/capture-projection

Conversation

@Yehonal

@Yehonal Yehonal commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

Capturing a commit could persist ownership and then fail when the complete integration was replayed. Pending control recovery could also create a manifest commit before capture refused.

Capture now proves the proposed stack and complete integration before writing, checks observed refs under Git transaction locks, and rolls back owned ref and metadata writes on handled persistence failures. It refuses pending control recovery with an explicit scoped remedy. Capture updates the selected manifest and ledger without automatically staging or committing control metadata; optional lane cleanup reports separately after a successful capture.

Validation covers conflicting cherry-pick and merge compositions, concurrent ref and lane changes, persistence rollback, the printed recovery command, commit-hook non-invocation, and interrupted Git transaction responses. All 15 capture fixture cases passed; the broader compatibility run passed 34 cases, with its remaining subprocess fixture corrected and verified separately. Three additional legacy capture checks and 12 module/documentation checks passed. Independent review: READY on 7b74ba3. Version 0.47.20.

@Yehonal
Yehonal merged commit 9060c42 into main Nov 16, 2026
38 of 40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant