dhpk-gitnexus-impact-analysislisted

# Impact Analysis with GitNexus ## When to Use - "Is it safe to change this function?" - "What will break if I modify X?" - "Show me the blast radius" - "Who uses this code?" - Before making non-trivial code changes - Before committing — to understand what your changes affect ## Workflow ``` 1. gitnexus_impact({target: "X", direction: "upstream"}) → What depends on this 2. READ gitnexus://repo/{name}/processes → Check affected execution flows 3. gitnexus_detect_changes() → Map current git changes to affected flows 4. Assess risk and report to user ``` > If the context reports a stale index, follow `dhpk-gitnexus-guide` for the > single stale-index recovery path before continuing this workflow. ## Checklist ``` - [ ] gitnexus_impact({target, direction: "upstream"}) to find dependents - [ ] Review d=1 items first (these WILL BREAK) - [ ] Check high-confidence (>0.8) dependencies - [ ] READ processes to check affected execution flows - [ ] gitnexus_detect_changes() for pre-commit check - [ ] Assess risk level and report to user ``` ## Output Return a compact report containing the target symbol, index freshness, direct callers, affected execution flows, risk level, and next verification commands. Mark graph gaps, dynamic references, and external consumers as uncertainties instead of treating the graph as exhaustive. ## Verification - [ ] The target and direction used for `gitnexus_impact` are recorded. - [ ] Direct depen