vs-searchlisted

# vs-token-safer search routing Code search runs through an OFFICIAL language server's index (clangd for C++, a Roslyn-based LSP for C#) and the result is token-capped to a compact `file:line` list — no source bodies. No IDE needs to be open; the engine is spawned headlessly. Karpathy-style rules: do the listed thing, do not improvise. ## Tools (MCP server name: `vs-search`) - Symbol / class / function / type / variable → `search_symbol` (args: `q`, `projectPath`, `backend`, `maxResults`). Never `grep`/`rg` for this. - References / usages of a symbol → `find_references` (args: `symbol` NAME, or `path`+`line`+`character` — 0-based — `includeDeclaration`). Semantic, not a text match. `direction=callers`/`callees` + `depth` → a **multi-hop call hierarchy** (transitive callers = blast radius before an edit / callees) via LSP `callHierarchy`, instead of flat references. - Definition of a symbol → `goto_definition` (args: `path`, `line`, `character` — 0-based). The `kind` arg picks WHICH: `definition` (default) · `type_definition` (the type of an expression) · `implementation` (concrete impls of an interface/abstract/virtual — "who implements this?") · `declaration`. For every *usage* (not the definition) use `find_references` instead. - Type / signature at a position → `hover` (args: `path`, `line`, `character`). - Outline a file (its classes/functions) → `document_symbols` (args: `path`; `scope="directory"` → a signatures-only skeleton of every code file under a dir, to gr