chore: fix clippy warnings, add embedding/omni_patch, update telemetry, and ignore temp files

instructions.md

@@ -92,9 +92,14 @@ When shifting context rapidly (e.g. from building a feature to fixing a prod bug
 - **load_context_workspace:** Retrieve a saved workspace to instantly restore your context when returning to that task.
 - **list_context_workspaces:** List all saved workspaces in a project.
 
-## Omni-Search (Global Vault Search)
-When you remember a vague keyword but don't know which specific vault it's stored in.
+## Omni-Search (Hybrid Vector Search)
+When you remember a vague concept, keyword, or architectural pattern but don't know which specific vault it's stored in.
 - **omni_search:** Searches across the Knowledge Graph, Tasks, Snippets, ADRs, Tech Debt, Memos, and Error Fixes simultaneously.
+- **Semantic Superpower:** This tool utilizes **Hybrid Vector Search** (BM25 + Vector Embeddings). You do not need exact keyword matches. You can query conceptually (e.g., "database lock issues" or "how is auth handled") and the engine will return semantically relevant context.
+
+## Terminal History & Telemetry
+To maintain an audit trail of shell commands and execution contexts.
+- **Context:** The server actively tracks Terminal History. Commands executed in the user's shell are logged to the memory server and visible in the dashboard UI. While you don't call an MCP tool for this directly, be aware that complex shell actions and their outcomes are persisted for historical auditing and UI visibility.
 
 ## Project Health Dashboard
 When starting a new session, get a numerical aggregate of the project's current state.
@@ -112,4 +117,5 @@ The project contains two MCP binaries (win-nvim and linux-nvim) that bridge JSON
 - **God Mode**: They also expose `nvim_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 `nvim_execute_lua`. Do not attempt to recompile the Rust server to add new basic tools; use the Lua escape hatch dynamically.
 
 ## 16. Tool Schema Discovery (Lazy Loading)
-Antigravity automatically caches all MCP tool schemas to your disk to save tokens. Do **NOT** grep or search the Rust source code to find tool schemas or arguments. To understand a tool`s arguments, directly read `~/.gemini/antigravity-cli/mcp/<server_name>/<tool_name>.json`. For simple tools, confidently guess the arguments instead of reading the schema to save time.
+Antigravity automatically caches all MCP tool schemas to your disk to save tokens. Do **NOT** grep or search the Rust source code to find tool schemas or arguments. To understand a tool`s arguments, directly read `~/.gemini/antigravity-cli/mcp/<server_name>/<tool_name>.json`. Do NOT guess arguments. ALWAYS read the schema if you are unfamiliar with a tool to prevent invalid argument errors.
+