0.1.2

A meeting note structured the way it gets read back

The synced note was a title, a summary and a flat list of action items. Opening
one the next morning, the thing you want first is what was decided, then what
you owe, then what is still unresolved — and none of that was distinguishable.

Sections now follow that order and empty ones are omitted rather than printed as
bare headings, which fills Obsidian's outline with dead entries and makes the
note look broken.

Three things the vault can do that a transcript cannot, now done:

  - People are wikilinks. The meeting appears in a person's backlinks without
    anyone filing it there, which is the whole reason to keep meetings in a
    vault at all.
  - `date:` is a bare yyyy-mm-dd, so Obsidian parses it as a real date property.
    Quoted, or left as a full ISO timestamp, it is only a string and silently
    drops out of every dated query.
  - What Scriben remembers about the meeting is written into the note, so the
    memory is readable where the meeting is, not only inside the app.

Action items carry an owner and a due date when the server sent them, and grow
neither an empty @ nor an empty date when it did not. Boxes are never
pre-ticked: Scriben has no completion state, so a tick would be a claim we
cannot back — and the box being the user's means ticking it survives a re-sync.

Also halves the round trips: get_summary already returns action_items, mentions
and flagged, and the plugin was asking a second tool for what the first reply
had already sent.

28 tests.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>