ccg-analyzelisted

# ccg-analyze — Code Analysis Graph-based analysis for **change impact, call flow, dead code, module structure** — anything about "relationships." ## Intent → Tool Mapping | User intent | Tool | Notes | | ------------------------------------ | ------------------------------------------------ | --------------------------------------------- | | "Impact of changing this function?" | `get_impact_radius` (start with depth 3) | Widen to depth 5 if too narrow | | "Trace call flow from this function" | `trace_flow` | If broken at interfaces, see workaround below | | "Who calls this function?" | `query_graph` (callers_of) | | | "What does this function call?" | `query_graph` (callees_of) | | | "Risk of this change" | `detect_changes` + `get_affected_flows` | git diff-based | ## trace_flow Limitations & Workaround If `trace_flow` returns **only 1–2 starting nodes**, it broke at an interface dispatch boundary (Go's `h.deps.X.Method()`, Python duck typing, etc.). **Workaround**: ``` 1. Confirm starting point via trace_flow 2. Manually expand graph with callers_of / callees_of 3. When you hit interface methods: