0.1.17
Central Vault Sync 0.1.17
Fixes an HTTP 500 observed during a real large, deeply nested vault bootstrap.
Fix
- A directory marker can change while descendant files are being uploaded.
- The plugin now keeps every descendant marker durable until that exact parent marker has been safely prepared.
- On retry it publishes the parent directory before its child files.
- No note operation or content is discarded; interrupted work remains resumable.
Server-side defense
Updated WebObsidian servers validate create/mkdir parents and return canonical invalid_request instead of exposing a filesystem ENOENT as HTTP 500. The server never invents unrevisioned implicit directories.
Verification
- Added a regression that first proves stale parent work blocks its child, then proves retry commits parent → child.
- Plugin check passes 31 tests plus lint, typecheck, build, and policy checks.
- WebObsidian passes 94 server tests plus the full core/web/headless suites, typecheck, build, and API/docs lint.
Users affected by a revoked/failed pairing should update to 0.1.17, choose Unpair locally, generate a new code for the same intended server vault, and pair again. Existing accepted server revisions are preserved and the new pairing converges the remaining local paths.