fix: harden upstream sync recovery - #3
Merged
Merged
Conversation
3metaJun
force-pushed
the
fix/harden-sync-upstream-recovery
branch
from
September 10, 2026 19:07
aad9649 to
7d17ecc
Compare
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.
The crash-recovery path could mistake a reused PID for a live sync and could wedge forever when a user edited a target after a crash. This PR records host/platform/process-start identity, fails closed for unverifiable cross-runtime owners, quarantines unexpected user edits before rollback, treats COMMITTED as authoritative for cleanup, and validates reserved journal targets and takeover initializers. README documents serialized readers and Windows process-crash-only durability. Verification: npm test (72 pass, 1 existing Unix-only skip); WSL Node 18 sync tests (24 pass); npm run check-package; npm pack --dry-run; git diff --check.\n\n---\nAgent: GPT-6 via Codex