0.1.16

Central Vault Sync 0.1.16

This review release makes initial pairing of large local vaults substantially faster and shows live aggregate progress.

Performance

• Scans and persists local reconciliation work in bounded checkpoints instead of rewriting state per path.
• Uses at most four concurrent blob uploads.
• Publishes up to 100 ordered operations per request when the server advertises safe stop-after-failure batching; older servers automatically remain at one operation per request.
• Removes acknowledged terminal operation batches atomically while preserving idempotent crash replay.
• Deterministic 10,000-file full-plugin benchmark: 403.6s → 8.7s median (46.24×), 10,000 → 100 operation requests, and 50,002 → 302 plugin-state writes.

Progress and recovery

• Status bar and Settings show aggregate recovering, manifest, scanning, uploading, publishing, applying, and finalizing progress.
• Reports item/byte counts, operation/blob request counts, elapsed time, and resumed retries.
• Progress never includes note content, private paths, credentials, or raw errors.
• Scan, upload, checkpoint, stale-marker, retry, and concurrent Sync-now paths preserve durable work.

Safety

• Local paths are scanned and checkpointed before manifest materialization.
• Pending paths and queued operations remain protected from remote replacement.
• Operations stay revisioned, ordered, vault-bound, and idempotent.
• Server rejection stops later batch rows so retained client sequences remain retryable.

Requires WebObsidian with ordered-batch-stop-v1 for batched publication. Older Protocol 1.0 servers remain compatible through the safe one-request fallback.