0.1.0

Scriben for Obsidian: meetings in, chosen notes out

Obsidian has no cloud API and no OAuth — the vault is a folder on the user's
machine — so the only shape that can sync automatically is a plugin running
inside Obsidian. A URL-scheme share needs a human tap every time and cannot run
after a recording finishes.

Two directions, and the second is off by default:

  Scriben -> vault  each recording becomes one markdown note with frontmatter,
                    a summary and unchecked action items.
  vault -> Scriben  only folders the user names, so the agent can answer with
                    their own context.

Three decisions worth reading the tests for:

The plugin owns the region between two markers and nothing else. Anything the
user writes above or below it survives a re-sync, and a file they created at our
path is appended to rather than replaced. A plugin that rewrites whole files
eats the annotation someone added under the summary, which is the entire reason
they filed the meeting in their vault.

Filenames carry the note's permanent ref, never its title. A re-summarised
meeting updates in place instead of filing a second copy, and a retitled note
keeps its old path so existing wikilinks keep resolving.

Nothing outside the named folders is ever sent, and the default is empty. A
folder whose name merely starts with a shared one is not in scope — the naive
prefix check would have uploaded MeetingsPrivate/ to anyone who shared
Meetings/, and there is a test that fails if it is reintroduced.

No node:crypto and no Buffer anywhere: neither exists on Obsidian mobile, and
this plugin is not desktop-only. Fingerprinting is plain JS so the same code
runs on a phone, a laptop and in the tests.

20 tests, no telemetry, no analytics.