Skip to content

fix: harden upstream sync recovery - #3

Merged
3metaJun merged 1 commit into
mainfrom
fix/harden-sync-upstream-recovery
Sep 10, 2026
Merged

3metaJun merged 1 commit into
mainfrom
fix/harden-sync-upstream-recovery

Conversation

@3metaJun

Copy link
Copy Markdown
Owner

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

@3metaJun
3metaJun force-pushed the fix/harden-sync-upstream-recovery branch from aad9649 to 7d17ecc Compare September 10, 2026 19:07
@3metaJun
3metaJun merged commit aa824da into main Sep 10, 2026
9 checks passed
@3metaJun
3metaJun deleted the fix/harden-sync-upstream-recovery branch September 10, 2026 19:09
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