0.1.15

Central Vault Sync 0.1.15

Vault-binding clarity and rate-limit diagnostics update.

Changed

• Plugin settings now show the bound server vaultId after pairing.
• Unpaired settings explicitly require selecting or creating the intended server vault in WebObsidian before generating a code.
• Pairing-code help clarifies that a device name never creates a vault; the code binds the local vault to the server vault displayed by WebObsidian.
• Rate-limit errors now include the server-advertised retry delay when available.

Safety

• Pairing remains one-use, vault-bound, revocable, and stored through Obsidian SecretStorage.
• Revision-aware writes, durable queues/apply intents, SHA-256 verification, conflict copies, and unsaved-editor protection are unchanged.

This is a normal GitHub release for Community directory review.