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

nvim-core/src/instructions.md

@@ -2,48 +2,22 @@
 
 When connected to this Neovim MCP server (`win-nvim`), you have powerful tools to interact directly with the active Neovim editor.
 
-## The Consolidated Tool Arsenal (v2)
-The server consolidates granular Neovim operations into 7 smart domain tools:
-- **`nvim_buffer`**: Buffer and file management.
-  - `action: "open_file"`: Open file in buffer (args: `file`, `line`, `col`).
-  - `action: "open"`: Open buffer (args: `bufnr`).
-  - `action: "close"`: Close buffer (args: `bufnr`, `force`).
-  - `action: "reload"`: Reload buffer from disk (args: `bufnr`).
-  - `action: "save"`: Save buffer to disk (args: `bufnr`).
-  - `action: "list"`: List all loaded buffers.
-- **`nvim_window`**: Window split and focus management.
-  - `action: "split"`: Split window (args: `direction: "horizontal" | "vertical"`, `file`).
-  - `action: "close"`: Close window (args: `winnr`).
-  - `action: "list"`: List open windows.
-  - `action: "get_active"`: Get active window details.
-  - `action: "set_active"`: Set active window focus (args: `winnr`).
-- **`nvim_view`**: Editor viewport and navigation.
-  - `action: "get_active_buffer"`: Get active buffer details.
-  - `action: "get_cursor"`: Get current cursor line/col.
-  - `action: "goto_line"`: Jump cursor to line (args: `line`, `col`).
-  - `action: "get_viewport"`: Get visible line range in viewport.
-  - `action: "get_messages"`: Get Neovim command-line messages.
-- **`nvim_diagnostics`**: LSP diagnostics querying and publishing.
-  - `action: "get"`: Get diagnostics (args: `bufnr`, `severity`).
-  - `action: "set"`: Set buffer diagnostics (args: `bufnr`, `diagnostics`).
-- **`nvim_visual`**: Visual highlighting, extmarks, and quickfix.
-  - `action: "get_selection"`: Get current visual selection text and range.
-  - `action: "highlight_lines"`: Highlight line ranges (args: `bufnr`, `hl_group`, `start_line`, `end_line`).
-  - `action: "set_extmark"`: Place virtual text or sign extmarks (args: `bufnr`, `ns_id`, `line`, `col`, `opts`).
-  - `action: "set_quickfix"`: Populate quickfix list (args: `items`, `title`).
-- **`nvim_execute_lua`**: God Mode arbitrary Lua evaluation.
-  - Arguments: `code: String`.
-- **`nvim_system`**: System diagnostics and connection heartbeat.
-  - `action: "ping"`: Heartbeat test.
-  - `action: "status"`: Server and socket bridge health status.
+## The Consolidated Tool Arsenal (v3)
+The server consolidates granular Neovim operations into 5 smart mega-tools:
+- **`nvim_buffer`**: Buffer and file management. Actions: `read`, `replace`, `save`, `undo`, `redo`, `create_scratch`.
+- **`nvim_workspace`**: Window split and focus management. Actions: `list_buffers`, `list_windows`, `focus`, `split`, `cwd`.
+- **`nvim_intelligence`**: Code intelligence and LSP. Actions: `hover`, `definition`, `references`, `outline`, `query`, `diagnostics`, `rename`, `code_action`.
+- **`nvim_ui`**: Visual highlighting, diff previews, and ghost text. Actions: `highlight`, `ghost_text`, `clear`.
+- **`nvim_exec`**: Escape hatch for raw evaluation. Actions: `lua`, `vimscript`, `terminal`.
 
 ## 1. Using Consolidated Domain Tools First
-Always prefer the specific consolidated tools (like `nvim_buffer`, `nvim_window`, `nvim_visual`, etc.) over writing raw Lua scripts. These tools are strongly typed, tested, and safe.
+Always prefer the specific consolidated tools (like `nvim_buffer`, `nvim_workspace`, `nvim_ui`, etc.) over writing raw Lua scripts. These tools are strongly typed, tested, and safe.
 
-## 2. Lua God Mode (`nvim_execute_lua`)
-If you need to access *any* Neovim API that does not have a dedicated tool (e.g., complex buffer edits, changing options, custom LSP interactions), you MUST use `nvim_execute_lua` as your escape hatch.
+## 2. Lua God Mode (`nvim_exec` with action `lua`)
+If you need to access *any* Neovim API that does not have a dedicated tool (e.g., changing options, setting autocmds), you MUST use `nvim_exec` with action `lua` as your escape hatch.
+**CRITICAL**: `nvim_exec` is restricted to **READ-ONLY** queries. Do NOT use it to mutate editor state.
 
-### CRITICAL RULES for `nvim_execute_lua`:
+### CRITICAL RULES for `nvim_exec` (`lua`):
 1. **Never Block:** Never use interactive prompt functions or interactive confirmation flags in substitutions (e.g., `%s/old/new/gc`). This will cause the headless MCP bridge to deadlock forever.
 2. **Visual Feedback:** Always trigger a notification using `require("notify")("Antigravity: [Action]", "info", { title = "Antigravity" })`.
 3. **Auto-Save:** If you modify a file buffer, always save it using `vim.cmd('write')` within the same Lua script so external tools can see the changes, unless you explicitly want to pause for manual human review.
@@ -57,4 +31,3 @@ While the headless background instance is great for autonomous, routine tasks, i
 
 ## 4. Tool Schema Discovery
 Do **NOT** grep or search the Rust source code to find tool schemas or arguments. All lazy-loaded MCP tool schemas are automatically cached as JSON files on your disk. To understand a tool's arguments, directly read `~/.gemini/antigravity-cli/mcp/win-nvim/<tool_name>.json` (or linux-nvim).
-