graph-explorerlisted

# graph-explorer Purpose: Load the graph_os toolset (`cos_graph_*` MCP tools) and use it deliberately before any non-trivial code edit. The graph is the third retrieval layer (CLAUDE.md Three-Layer Retrieval) — use it when tree-grep or past-memory searches return noise. Read when: Editing `src/core/**` or `src/cli/**`, producing a rename plan, auditing API/MCP contracts, answering "what depends on X". Skip when: You already know the blast radius, or the change is a self-contained one-file edit with no callers. ## Decision ladder 1. **Need to know "what calls this?"** → `cos_graph_references(uid)`. 2. **Need surrounding context before editing?** → `cos_graph_context(uid_or_name, depth=1)` (Implementer pre-impl step). 3. **Planning a refactor?** → `cos_graph_impact(uid, depth=3)` (Analyst dependency map) groups edges by risk tier. 4. **Renaming a symbol?** → `cos_graph_rename_plan(uid, new_name)` before any `Edit` — returns call-sites, doc refs, tests, string literals. 5. **API / contract audit?** → `cos_graph_contracts(kinds=["http","mcp"])` (Documenter + Deployer). 6. **Tracing a fault?** → `cos_graph_trace(entry_uid)` (Debugger fault isolation step). 7. **"Is anything similar?"** → `cos_graph_similar(uid, top_k=5)`. 8. **Shortest dependency path?** → `cos_graph_path(source, target)`. 9. **Need a diagram?** → `cos_graph_export(format="mermaid", root_uid=...)`. 10. **Pre-commit self-review?** → `cos_graph_detect_changes(files=[...])` — call BEFORE `make verify`. > **Meth