io.github.maxkuminov/obsidian-mcp

Eight changes since v0.10.0, and the first release whose version number promises the tool contract: `hybrid_search` and `semantic_search` pages carry `confidence: ok | low`, shipped off (#389); chunks have a 200-character minimum and end on word boundaries, `CHUNKING_VERSION` 2 (#390); tags are in the keyword vector and `matched_in` gains `tags`, migration 035 (#391); the docs recommend Qwen3-Embedding for local embeddings and describe the reranker reference setup (#405); `tools/list` follows the credential, so a read-only OAuth grant lists 19 tools, and the 28-tool contract fixture is frozen (#358); the OAuth server accepts Client ID Metadata Documents with DCR as the fallback, migration 036 (#357); the search-evaluation harness gains a mechanical `gate` step (#411); and `rerank=true` sends each note's embedded text for up to four of its fetched chunks and scores the note on the best of them, with `RERANK_MAX_DOCUMENTS` (#402).

## Upgrade notes

- **Two migrations, 035 and 036**, run by the init container on Kubernetes or by `make deploy` on compose (which stops the app first). Neither refuses startup or needs `make reset-embeddings`. With `Recreate`, a direct upgrade from v0.10.0 is one downtime window.
- **Before upgrading, run the 035 preflight.** DEPLOYMENT.md, "Upgrading across migration 035", has a read-only statement (counts and ids only; a one-config and a multi-config form). `flagged` must be `0`. A flagged note is shortened (body or tags) and re-indexed by the current image first.
- **035 (tags in the keyword vector)** rewrites every tagged vector once, in SQL, under the index generation lock: about 30–40 seconds for 4,265 synthetic notes of 1,800 words with three tags each, added to the `Recreate` gap. It is all or nothing, with a size preflight that aborts naming row ids before any UPDATE. **Under `Recreate` an abort is downtime** until the image digest is reverted. If you migrate by hand, stop the app first: an old-image process that writes a vector after 035 commits writes it without tags. Nothing is re-embedded. `make rebuild-tsvectors` afterwards is optional (it makes shifted body positions byte-exact). Rollback: `alembic downgrade 034` with the new image, then the old image.
- **036 (CIMD)** adds `oauth_clients.client_id_metadata_url` and the CHECK `ck_oauth_clients_cimd_shape`, with no backfill, in seconds. **Its downgrade refuses while any CIMD client row exists**: delete those clients on the panel's OAuth page first (their grants go with them, and their users reconnect).
- **Connectors switch to CIMD on their next fresh connection.** The AS metadata advertises `client_id_metadata_document_supported: true`; claude.ai, Claude Code and ChatGPT then send an `https` `client_id` instead of calling `/register`. Existing DCR grants are untouched, and DCR stays the fallback for a client that sends no URL. Claude Code can now complete on a loopback callback.
  - The consent page names the application by its document URL's host, shows the full URL and "First approved", and does not render the document's self-declared `client_name` (panel-only). An all-loopback client gets an extra warning. Its CSP `form-action` gains `http://localhost:*` and `http://127.0.0.1:*`.
  - Every authorization redirect carries `iss` (RFC 9207). `resource` (RFC 8707) is classified in the security log and never refused; enforcement is #404, after 14 consecutive days with no `resource_class: unexpected`.
  - The server fetches each client's metadata document over `https`, through the `import_from_url` SSRF policy. An egress policy that blocks public HTTPS breaks CIMD (`invalid_client`; `client_metadata.fetch_failed` or `client_metadata.ssrf_refused` in the log).
  - Rollback lever: `OAUTH_CIMD_ENABLED=false` and a recreate, no rebuild. Clients fall back to DCR, and CIMD grants keep refreshing.
- **Read-only OAuth grants list 19 tools.** A grant without `readwrite` no longer lists the nine write-required tools (`create_note`, `edit_note`, `mov