Skip to content

fix: make personal tracking writes atomic on failure - #174

Merged
Yehonal merged 1 commit into
mainfrom
fix/personal-tracking-atomic
Nov 16, 2026
Merged

Yehonal merged 1 commit into
mainfrom
fix/personal-tracking-atomic

Conversation

@Yehonal

@Yehonal Yehonal commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

A personal tracking update could replace its manifest and then fail while appending the private ledger, leaving a partially applied command. Prepare the complete manifest, event segment and checkpoint before publication, and restore this operation’s writes when publication fails. Preserve concurrent replacements and retain recovery images when restoration cannot safely finish. A cleanup error after successful publication reports an applied result with a warning.

The personal selection leaves the profile, shared ignore files, Git index, hooks, product files and refs unchanged. Fixtures cover ignored personal metadata with a different worktree root, preparation and publication failures, existing ledger contents and modes, unsafe profile aliases, concurrent replacement and cleanup failures. Process termination and power-loss recovery are outside this change.

Validation: 7/7 atomicity tests on the final commit; 18 existing tracking tests passed before the cleanup-only adjustment; 12 module-boundary and documentation tests; version-bump guard and generated site check; independent review READY on 7b623ef. CI must pass before merge. Version 0.47.16.

@Yehonal
Yehonal merged commit ef6c5a4 into main Nov 16, 2026
20 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