docs(nvim-core): prune obsolete tool names from configuration and docs

mcp_tools_review.md

@@ -10,7 +10,7 @@ Our current MCP ecosystem is highly advanced, utilizing a **Dual-Transport Leade
 *   `process_logs`: Direct file seeking and daemon log management (`watch`, `get`, `clear`). Prevents LLMs from reading multi-megabyte log files. **Score: A**
 
 ### 2. Neovim IDE Integration (nvim-core)
-*   `nvim_buffer`, `nvim_window`, `nvim_view`, `nvim_diagnostics`, `nvim_visual`, `nvim_execute_lua`, `nvim_system`.
+*   `nvim_buffer`, `nvim_workspace`, `nvim_intelligence`, `nvim_ui`, `nvim_exec`.
 *   **Review:** Exceptional human QoL. The agent interacts with the code where the human's eyes actually are. Ghost text and diagnostic extmarks provide an IDE-like experience usually reserved for closed-source tools like Cursor. **Score: S-Tier**
 
 ### 3. Clipboard & Workflow
@@ -37,7 +37,7 @@ To push the system to the absolute bleeding edge of autonomous coding, I propose
 *   **The Solution:** Using Tantivy and BERT embeddings in our backend. We index the AST blocks of the codebase in the background. The LLM can query *"Where is the auth token validated?"* and get the exact 3 relevant functions instantly.
 *   **Impact:** Massive token cost reduction (no blind file reading). Instant T2R for codebase exploration.
 
-### 3. `nvim_system` terminal execution (Interactive Execution QoL)
+### 3. `nvim_exec` terminal execution (Interactive Execution QoL)
 *   **The Problem:** When the agent runs a background terminal command (`cargo build`, `npm run dev`), the output is hidden from the human, and interactive prompts cause the background task to hang indefinitely.
 *   **The Solution:** Dispatch to Neovim terminal splits where the human can watch the tests run natively, interact with prompts, see ANSI colors, and interact seamlessly.
 *   **Impact:** Massive Human QoL.