docs: complete final doc sweep for Dashboard UI REST APIs and query_graph_path

instructions.md

@@ -18,10 +18,10 @@ You do not need to memorize JSON schemas for these tools; they are strictly defi
 - **When to use:** Use this whenever you make a non-trivial architectural, environmental, or tooling decision (e.g. choosing a specific framework, a specific deployment flag, bypassing a rule with a workaround).
 - **Behavior:** This permanently stores the context, decision, and consequence of *why* something is done the way it is, preventing future agents from second-guessing or reverting it.
 
-## 10. Graph Refactoring & Maintenance
-- **Tools:** merge_entities, ind_orphans
-- **When to use:** Run ind_orphans periodically or when you notice graph clutter to safely delete unused nodes. Use merge_entities when you notice duplicated semantic concepts (e.g. API_Gateway vs APIGateway).
-- **Behavior:** merge_entities will safely combine their observations and automatically remap all relations pointing to or from the deleted duplicate.
+## 10. Graph Refactoring & Algorithms
+- **Tools:** merge_entities, find_orphans, query_graph_path
+- **When to use:** Run `find_orphans` periodically or when you notice graph clutter to safely delete unused nodes. Use `merge_entities` when you notice duplicated semantic concepts (e.g. API_Gateway vs APIGateway). Use `query_graph_path` when you need to understand how two completely different architectural components are related (e.g. "How does the Frontend connect to the Database?").
+- **Behavior:** `merge_entities` will safely combine their observations and automatically remap all relations pointing to or from the deleted duplicate. `query_graph_path` executes a breadth-first search to find the shortest relational path between nodes.
 
 ## 11. Dynamic Learned Preferences
 - **Tools:** learn_preference,