Lexical-semantic search over the vault (BM25 plus one wiki-link hop). Call it before answering any question about the user's decisions, patterns, gotchas or history, and before recording a new learning. Returns snippets already cited as path:line — repeat that citation in your answer. Notes under 01-raw/ are excluded unless include_raw.

Reads a whole note by its vault-relative path (e.g. 02-wiki/nestjs/auth-guard.md), with frontmatter, resolved links and broken links. Use it after vault_search when the snippet is not enough, or before editing the note.

Lists notes by metadata — tipo, tags, status, folder — without looking at content. Use it for inventory ("which projects are active?", "which notes carry the jwt tag?"), not to search by subject: for subject use vault_search.

Lists the notes pointing at the given note. Use it to gauge how connected a subject is, to find the MOC that indexes the note, or to weigh the impact of changing or renaming it.

Creates or replaces a whole note, with frontmatter guaranteed, and commits it to the vault's git. It replaces the entire file: to change one passage use vault_edit_note, and to record a learning use vault_learn, which picks the destination and propagates on its own.

Replaces ONE exact passage of an existing note and commits. Fails, without writing, if the passage does not appear or appears more than once — in that case send more context in old_text.

Records a learning in the vault. Call it whenever something non-obvious and reusable comes up during the session — an architecture decision, a pattern, a gotcha, a configuration trap — without asking first where to save it: the server decides on its own between appending to the existing note that already covers the subject and creating a new one (the bias is to create), and propagates on its own to the domain MOC and the daily note (and to the knowledge index when the domain is new), all in a single commit. Show the returned diff to the user.

Moves, renames, promotes or archives a note, fixing on its own every link that would otherwise start pointing somewhere else, migrating its entry between domain MOCs and committing it all at once. to is the full path with .md, so the four operations are one: 01-raw/inbox/rascunho.md → 02-wiki/nestjs/auth-guard.md promotes, renames and changes domain together. 99-archive/ counts as BOTH source and destination, which gives you archive and unarchive. A destination domain with no MOC requires confirm_novo_dominio. Show the returned diff to the user.

Deletes a note and commits, removing its line from the domain MOC. Refuses, without deleting, if the note has no committed version in HEAD (there would be no way to undo), if it is structural (MOC, daily note, index) or if it lives under 99-archive/. Notes pointed at by others require confirm, and the refusal lists who points at them — their links will break. The answer carries the exact command that undoes it.