Fix MCP hangs and add logging

instructions.md

@@ -118,3 +118,14 @@ When instructed to restart, update, or stop the mcp-memory-server binary, never
   - **WebSockets (/ws):** Used strictly by external UI clients (e.g., dashboard.html) or the mcp-memory-stub proxy.
 - **Behavior:** Both transport layers route into the exact same central handle_request pipeline. Do not build feature logic that only works on one transport protocol.
 
+
+
+## 15. Neovim Integration & God Mode
+The project contains two MCP binaries (win-nvim and linux-nvim) that bridge JSON-RPC over stdio directly to the active Neovim instance (using ctive_nvim.txt for Last Focused Wins telemetry). 
+- These binaries expose basic tools (
+vim_get_cursor, 
+vim_get_active_buffer, 
+vim_list_buffers, etc.).
+- **God Mode**: They also expose 
+vim_execute_lua. This is the ultimate fallback tool. If you need to access *any* Neovim API that does not have a dedicated Rust tool (e.g., getting LSP diagnostics, evaluating a visual selection block based on modes, setting registers), you MUST write a short Lua script and pass it to 
+vim_execute_lua. Do not attempt to recompile the Rust server to add new basic tools; use the Lua escape hatch dynamically.