docs(readme): show what search_notes actually returns

[AlexMost]

Why

search_notes is the flagship tool, but the README only ever talked about it — six prose mentions of "hybrid search" and not a single call or response. Meanwhile #107 gave query_notes, an auxiliary tool, the only worked example in the file. This inverts that asymmetry.

What changed

New section — 🔭 One search, both legs, placed ahead of the query section:

• An array query. Up to eight queries per call for synonyms, jargon, and translations, with the cross-language property spelled out — a note in one language found by a query in another. Nothing in the README hinted this was possible.
• A real match object, showing found_in: ["semantic", "lexical:title"] alongside its per-leg evidence. The provenance array is the most convincing artifact the server produces: it shows both legs ran and fused, which no amount of prose about "hybrid" conveys.
• blocks[] with line ranges. The tagline promises "low-token retrieval" and the README never showed where that comes from — the assistant pulls the matched section, not the whole note.
• Two properties that are easy to miss: RRF lifts a note found by several legs while keeping it a single entry (no caller-side merging, no double-counting), and the tool degrades to its lexical leg while the index builds, reporting semantic_status, rather than failing.

Regroup. The pre-filter section documents a search_notes parameter but sat after query_notes. It now follows the section it describes: search → its filter → structured queries. Section text is unchanged; only the order moved.

One deletion. The → See docs/guide/finding-notes.md pointer above these sections is gone — each of the three sections now carries its own precise reference link, so it had become a vaguer duplicate of the three below it.

Deliberately left alone: the 🧠 hybrid-search bullet and the "Two superpowers" table. They work as the short pitch; the new section expands on them rather than repeating them.

Verification

• npm test — 1288 passed (104 files)
• npm run lint, npm run typecheck — clean
• prettier --check clean (also via pre-commit hook)
• Checked every anchor the new and moved text links to: #search_notes and #query_notes resolve to headings in finding-notes.md, and the moved pre-filter link still resolves to ### Pre-filter (\filter` parameter)`.

Docs-only, not planned ahead, so no issue trailer.

🤖 Generated with Claude Code