0.2.0 — upload your own notes

Adds the other direction: notes you write yourself can now go into your
Javis wiki. The download side works as it did in 0.1.1.

New: upload your own notes (optional, off by default)

Nothing is uploaded until you add a folder under Settings → Javis Wiki
Sync → Upload your notes.

• What is sent. The full text of every .md note in the folders you select,
  including subfolders, plus each note's path and title. Nothing outside those
  folders. The nine wiki folders, the vault root and .obsidian/ cannot be
  selected.

• What happens to it. Your Javis server stores the text and distills it
  into wiki pages. Those pages come back into this vault on the next sync.

• Edits follow. Edit a note and the wiki is updated from the new text,
  including anything you removed.

• Deleting takes it back out. Delete a note, or move it out of the selected
  folders:

  • its stored text is deleted from the server;
  • pages only that note produced are removed;
  • pages it shared with other sources are rebuilt from those sources.

  Pages created before this feature existed can't be rebuilt, so they are
  marked instead and may still mention the note. Nothing in your vault is
  ever deleted.

• One line is written into each uploaded note: javis_source_id: <uuid>.
  It's inserted as a single line of text, and the rest of your properties
  (comments, quotes, lists, dates) are left byte for byte.

• Safety checks before anything is removed:

  • a note must be missing on two syncs at least five minutes apart;
  • an unreadable file, such as an iCloud file that is only in the cloud,
    counts as present;
  • a folder that suddenly lists nothing removes nothing;
  • a sudden empty or >80%-shrunk note is held;
  • a sync that would remove more than min(50, 20%, at least 5) notes holds
    everything.

  Held changes wait for Review pending changes in the command palette.

The README has the full details: what is sent, where, why, how it's stored,
and how it's removed.

Also changed

• Sign-in now targets the server's /wiki resource. Allowing uploads asks
  you to sign in once more and shows a consent screen that lists the new
  permission (wiki:write). If you never select a folder, you keep the
  read-only permission you have now.
• The plugin refuses a plain http:// server address unless the server runs on
  this computer.

minAppVersion stays 1.11.4, and the plugin is still desktop-only.

Requires

The Javis server changes from this release are deployed at mcp.javis.is:
the upload routes, the wiki:write scope and the /wiki resource. The earlier
server-side token handling stays compatible for one release, so 0.1.1 keeps
syncing.

Upgrading from 0.1.1

Replace main.js and manifest.json in
<vault>/.obsidian/plugins/javis-wiki-sync/ and reload Obsidian. Your notes,
settings and sign-in are untouched, and nothing is uploaded until you choose a
folder.

Why this is a pre-release

It has not been run in a real Obsidian vault, and uploads have not been
exercised end to end against the live server.

• What was tested: 602 unit tests (up from 290), a clean typecheck and
  build, and a contract check of the plugin's requests against the server's
  implementation.
• What was not tested: the settings UI and the Obsidian vault adapter have
  no automated tests, and nothing was tried alongside Obsidian Sync, iCloud,
  git or Remotely Save.

Try it on a scratch vault first, as with 0.1.0. It will be promoted to
Latest after the end-to-end runbook passes against a real vault.