docs: Update guidelines and effective discourse for MCP tools

EFFECTIVE_DISCOURSE.md

@@ -43,7 +43,25 @@ Keep your workflow entirely within your editor rather than copy-pasting code blo
 *   **Do say:** "Push this refactor to my active Neovim buffer as ghost text so I can review it in-line."
 *   **Tool Triggered:** `nvim_set_preview` (via `win-nvim` or `linux-nvim`)
 
-## 8. Graph, Memory & Decay Management
+## 8. Structural AST Editing
+When asking the LLM to modify complex files, prevent indentation bugs and regex failures by guiding it to use tree-sitter.
+*   **Don't say:** "Search for `fn process()` and replace it with this string."
+*   **Do say:** "Use the AST node replacer to swap out the `process` function in `server.rs`."
+*   **Tool Triggered:** `replace_ast_node`
+
+## 9. Interactive Terminal Execution
+When asking the LLM to run commands that have prompts, long output, or ANSI colors.
+*   **Don't say:** "Run `cargo run` and tell me what the output is." (Hides output, hangs on prompts).
+*   **Do say:** "Send the `cargo run` command to my Neovim terminal split so I can interact with it."
+*   **Tool Triggered:** `nvim_send_to_terminal`
+
+## 10. Bird's-Eye Repository Exploration
+When the LLM is first analyzing a repository, don't let it run `ls -R` and guess.
+*   **Don't say:** "List the files in the directory and guess where the database code is."
+*   **Do say:** "Read the directory architecture to get a summary of what each file is responsible for."
+*   **Tool Triggered:** `read_directory_architecture`
+
+## 11. Graph, Memory & Decay Management
 Actively instruct the LLM to maintain its own memory constraints and organize data. The daemon automatically consolidates old sticky notes and snippets to prevent unbounded context growth.
 *   **Do say:** "Log this architectural decision in the knowledge graph."
 *   **Do say:** "Add a sticky note with the test database credentials for this session."