Analyze the blast radius of changing specific files. Returns which files would be directly and transitively affected, with a risk score (0-1). Use BEFORE committing multi-file changes to understand what might break. Does NOT modify any files.

Get the import and importedBy relationships for a specific file. Shows what this file depends on and what depends on it. Use to understand coupling before refactoring a file.

Return strongly connected components with more than one file from the current dependency graph. Use it to inspect circular dependencies before refactors or release gates.

Pre-commit safety gate. Analyzes specified changes and returns a PASS/WARN/BLOCK verdict with reasons. Use as a bounded decision aid before committing multi-file changes. BLOCK means current impact is too risky. WARN means human review recommended. PASS means low-risk.

Rebuild the dependency graph from scratch. Call this after significant file additions/deletions, or if analyze_impact results seem stale. Returns graph statistics including file count, edge count, build time, and any circular dependencies detected.