0.1.0 — first cut

One-way mirror of your Javis wiki into an Obsidian vault.

Every wiki page becomes a markdown file with working wikilinks, backlinks,
graph view and search. The server never sees your edits, and the plugin never
deletes a file.

Requirements

• Obsidian 1.11.4+ (the plugin keeps OAuth tokens in app.secretStorage)
• Desktop only — the OAuth flow binds a loopback listener on 127.0.0.1
• A Javis account

Install

This repo is private, so BRAT cannot reach it. Install manually:

1. Create <vault>/.obsidian/plugins/javis-wiki-sync/
2. Copy main.js and manifest.json from this release into it
3. Reload Obsidian, enable Javis Wiki Sync in Community plugins
4. Open settings, set your server URL, click Connect

Try it on a scratch vault first. It creates nine folders at your vault root.

What it does

Pages land in Sources/, Entities/, Concepts/, Topics/, Comparisons/,
Questions/, Syntheses/, Decisions/ and Gaps/ at the vault root, because
Obsidian resolves [[Concepts/Foo]] from there and the link text arrives
already correct.

Generated content sits between %% javis:generated:start %% and its matching
end marker. Everything outside those markers is yours permanently — the
plugin replaces the block wholesale and never merges, so there is no merge step
to go wrong.

Set javis_sync: false in a note frontmatter to adopt it. The plugin stops
copying that page down immediately; no write-back needed.

Safety properties

• Never unlinks. The vault adapter exposes no delete or trash method at all.
  A deleted page is tombstoned in place with a banner.
• Losing plugin state costs a rescan and nothing else. Per-page state lives
  in that page frontmatter; the cursor rebuilds from max(javis_rev) across the
  vault.
• Tokens never touch data.json. That file lives in the vault and would
  replicate a refresh token to every device you sync to.

Not in this release

Write-back to the server, transcripts, daily notes, stub files for unresolved
links, file deletion, a conflict UI, mobile.

Status

289 unit tests, clean typecheck and build. The end-to-end runbook has not been
run against a real vault yet — hence the pre-release tag. See the Phase 1
design spec in javis-server/docs/superpowers/specs/.