2.0.2

Full Changelog: 2.0.1...2.0.2

2.0.1

Full Changelog: 1.3.2...2.0.1

1.3.2

Full Changelog: 1.3.1...1.3.2

1.3.1

Full Changelog: 1.3.0...1.3.1

1.3.0

1.3.0 — iCloud on Windows is syncing-but-risky, not local-only

Prompted by a direct question: does an iPad reflect into Obsidian on Windows?

It does. iCloud for Windows replicates the folder, so notes really do travel
between an iPad and a PC. But classifyDriveLocation only knew Google Drive,
OneDrive and Dropbox, so a Windows vault sitting in iCloud Drive fell through
to local-only — telling someone their working vault was not syncing at all
and to go and move it. Same failure shape as the iOS bug in 1.2.1: an
unrecognised path reported as a definite negative.

Reporting it as plainly fine would have been worse than the bug. Obsidian
documents that iCloud Drive on Windows can duplicate or corrupt files, and no
plugin can prevent that. So iCloud outside the Apple ecosystem gets its own
verdict: syncing true, ok false, and guidance toward Google Drive or Obsidian
Sync, with a note that the conflicts card is where the damage surfaces.

Matched by container path too, so a raw iCloud~md~obsidian path is recognised
wherever it turns up. On Apple the same path stays plain 'ok' — the warning is
about the platform, not the folder.

144 tests, 35/35 mutations, including one that reports it local-only again and
one that stops recognising the folder.

1.2.1

1.2.1 — never report a mobile vault as local-only

Found on a real iPhone: 1.2.0's new setup popup fired on iOS telling a
perfectly healthy iCloud vault to move itself into iCloud.

classifyVaultLocation's branches all key off markers that only appear in a
desktop path — Mobile Documents, iCloud~md~obsidian, /Users/. Obsidian on iOS
reports a sandbox path carrying none of them, so it fell through to the
catch-all local-only verdict. Before 1.2.0 that misread was buried in the
panel; adding a popup turned it into an interruption telling the user to
break a working setup.

Falling through now means "could not tell", not "local", on any mobile
platform. Apple and Android both return their unverifiable result instead,
which shouldWarnAboutLocation already declines to warn about. Desktop paths
are still trustworthy and keep the local-only verdict.

Verified on the device: popup gone, and the phone's beacon reports 1.2.1.

137 tests, 33/33 mutations, including one per platform that removes the
guard and reproduces the false local-only.