v0.3.0

Folio can serve multiple MCP clients through one HTTP process bound to 127.0.0.1. Start it with serve --http PORT --token-file FILE; the private token stays outside process arguments and generated client configuration. Stdio remains available, including legacy MCP clients.

External note edits are discovered by a 15-second metadata census. Note and project writes retain their cross-process lock and atomic replacement, while index maintenance uses separate per-connection transaction ownership. Failed index refreshes after saved edits are logged and retried without reporting the saved edit as failed. HTTP refuses full rebuild-index requests immediately; use a separate stdio maintenance session. A first start with an empty or upgraded index may take several minutes before the HTTP listener is ready.

The old local note viewer is removed. --web and --web-port remain accepted with a deprecation warning and are ignored. Invalid crosslinks remain broken links, traversal through note/project names is refused, and batch task moves report invalid entries without stopping later valid moves.

Dependencies are locked to published releases, including sigil-json 0.16.1, sigil-mcp 0.18.3 and sigil-http 0.18.8, with the Sigil runtime family pinned to 0.22.15. Qualification passed 445 Sigil tests, authenticated HTTP/concurrency/external-edit checks, CLI and error isolation; the concurrent index regression also fails against the previous transaction implementation.