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

agent-rules/nvim_editing.md

@@ -16,9 +16,9 @@ File edits must use EXACTLY one of two paths:
 ## 2. Strict Tool Adherence (No Raw Lua RCE)
 You must strictly use the specialized, sandboxed Neovim MCP tools:
 - `nvim_buffer`: For reading, writing, saving, and creating scratch buffers.
-- `nvim_window`: For creating splits and focusing panes.
-- `nvim_visual`: For highlighting diffs, adding ghost text, and showing previews.
-**DO NOT** use `nvim_execute_lua` to mutate editor state. It is restricted to **READ-ONLY** queries.
+- `nvim_workspace`: For creating splits and focusing panes.
+- `nvim_ui`: For highlighting diffs, adding ghost text, and showing previews.
+**DO NOT** use `nvim_exec` (action `lua`) to mutate editor state. It is restricted to **READ-ONLY** queries.
 
 ## 3. Headless Quarantine
 Headless mode (`nvim --headless`) is strictly banned for interactive edits. 
@@ -26,7 +26,7 @@ Headless mode (`nvim --headless`) is strictly banned for interactive edits.
 Headless instances are allowed ONLY for non-interactive background batch processing (e.g., project-wide formatting or linting).
 
 ## 4. UI Presentation & Chat Console Minimization
-Never output large plans, context blocks, or architectural discussions to the chat console if Neovim is running. You MUST use the `nvim_buffer` and `nvim_window` tools to open a vertical split (e.g., `Antigravity_Plan.md` scratch buffer) and present the markdown natively. Reserve the chat console strictly for brief confirmations.
+Never output large plans, context blocks, or architectural discussions to the chat console if Neovim is running. You MUST use the `nvim_buffer` and `nvim_workspace` tools to open a vertical split (e.g., `Antigravity_Plan.md` scratch buffer) and present the markdown natively. Reserve the chat console strictly for brief confirmations.
 
 ## 5. Visual Cues & Auto-Save
 When manipulating buffers via MCP: