0.2.1

Fixes for the findings raised by the Obsidian Community automated review of 0.2.0.

Requires Obsidian 1.6.6 or later (was 1.6.0). Remote deletions now always go through FileManager.trashFile, so they follow the vault's own "Deleted files" preference instead of sometimes bypassing it — that API landed in 1.6.6, and the runtime fallback that used to cover older builds has been removed.

Also in this release: platform detection uses Obsidian's Platform API rather than the user agent, the vault configuration folder is read from Vault#configDir rather than assumed to be .obsidian, and JSON responses are narrowed from unknown rather than flowing through as any.

Release assets now carry GitHub build-provenance attestations. Verify with:

gh attestation verify main.js --repo kadima-tech/kadima-obsidian-sync

Installation: copy manifest.json, main.js and styles.css into <vault>/.obsidian/plugins/kadima-sync/, then enable Kadima Sync under Settings → Community plugins.

0.2.0

First public release of Kadima Sync.

Connect an Obsidian vault to a Kadima account through a browser approval flow, and keep notes and files in sync across devices. Pairing is per vault, edits stay local-first with per-file revisions, and conflicts are preserved as separate files in .kadima-conflicts rather than overwriting local work. A synced vault is also readable from Draggen's Vault tab and Talebuddy's Obsidian sidebar tab.

Requires a Kadima account with an active paid subscription. See the README for the disclosures on network access, token storage, and what is synced.

Installation: copy manifest.json, main.js and styles.css into <vault>/.obsidian/plugins/kadima-sync/, then enable Kadima Sync under Settings → Community plugins.