v0.2.0 (superseded by 0.2.1)

v0.2.0 Release Notes

Adds an optional second brain: StudyLoop can publish your study plans, today's
next action and your due reviews into a place you already read.

Nothing about this release changes what StudyLoop does if you do not configure
it. There is no second_brain: section in a fresh config, and without one no
provider module is imported, no file is written, and the wind-down protocol says
nothing about it.

What is new

• studyloop brain — status, publish, pull, enable and template.
  publish writes a projection of a plan, of today, and of your due review
  cards; pull reads one note of yours back when you ask it to.
• Obsidian, by writing plain files. Notes land in the folder you name inside
  the vault you name. StudyLoop overwrites only files carrying its own
  studyloop: frontmatter marker, never follows a symbolic link out of the
  vault, and republishing an unchanged plan writes nothing at all.
• Your plan document stays the only source of truth. No backend, command or
  agent path writes back to it. Your own notes for a plan live in a sibling
  .notes.md file that StudyLoop only ever reads.
• An Obsidian template (studyloop brain template --install) mirroring the
  plan document's sections, so a plan you write by hand and one StudyLoop
  published look the same. Templates carry no ownership marker: a note you make
  from one is yours.
• xTiles, stage 1. Your assistant moves today's study and your whole plan
  into xTiles over its MCP connector. The Second Brain guide ships the three
  prompts, and studyloop install agents installs an opt-in wind-down skill.
  There is no programmatic xTiles client yet, and StudyLoop stores no xTiles
  credential.
• One skill, installed once. The wind-down skill lives in
  ~/.agents/skills/ and is symlinked into each harness that documents a skills
  directory, so there is one file to read and one file to update.
• studyloop config init offers to enable it after you accept a vault. It
  defaults to no, and declining writes nothing.

Honest limitations

• Obsidian is the only provider with a programmatic backend. xTiles goes through
  your assistant, so what reaches xTiles is whatever your assistant sends.
• A projection you hand-edit is replaced on the next publish, with a warning
  naming the file. Personal notes belong in the sibling .notes.md.
• The vault boundary is enforced on every write, but a component of the path
  above the vault folder could in principle be replaced between the check and
  the write by someone who already has write access to your vault. This is a
  documented limitation, not a fixed one — see ADR-0010.
• The wind-down offer's pacing is a property of a language model, not of code.
  Static guards prove the offer is present and conditional; a recorded
  transcript is what shows it is offered once.
• The 0.1.0 limitations still stand: install is from a source checkout, and the
  Web UI is a laptop and tablet layout.

Withdrawn before release

An adapter for the official Obsidian CLI was built during development and
removed after a three-model review. It resolved its target by vault name, so a
second vault with the same name could receive the note, and it passed note text
as a command-line argument where another user on the machine could read it.
Writing the file directly is all this feature ever needed.

The keys use_cli, vault_name, template and daily_note now raise a
configuration error rather than being ignored. daily_note used to append a
line to your own daily note, and anyone who set it should be told it stopped.

Upgrade

Nothing to do. If you want the layer:

studyloop brain enable obsidian --vault ~/Obsidian/YourVault
studyloop brain publish
studyloop doctor

Verification

Run just release-check for the current automated release gate, just e2e for
the browser suite, and just docs for the strict public-documentation build.
The release decision cites the generated evidence from those runs, and the
multi-model review record under reviews/2026-09-03-second-brain/, never a test
total copied into this note.