feat: wire impact analysis into audit command

[jonathanpopham]

Context

PR #25 added api.Client.Impact() which calls POST /v1/analysis/impact — the dedicated impact analysis endpoint with risk scoring, affected functions/files, entry points, and diff support.

The audit command currently runs its own domain coupling analysis but doesn't use the dedicated impact endpoint. It should incorporate impact analysis results to produce a more complete health report.

Proposal

Add an impact analysis section to the audit health report:

• Run impact analysis (global mode, no targets) alongside the existing checks
• Surface the most critical files with their risk scores and dependent counts
• Flag any critical risk files in the recommendations section
• Include cross-domain dependency warnings when available

Example output addition

## Impact Analysis

| File | Risk | Direct | Transitive | Domains Crossed |
|------|------|--------|------------|-----------------|
| AuthConstants.java | critical | 110 | 280 | 3 |
| UserRepository.java | high | 45 | 120 | 2 |

References

• api.Client.Impact() — internal/api/client.go
• Impact types — internal/api/types.go (ImpactResult, BlastRadius, etc.)
• Audit handler — cmd/audit.go / internal/factory/health.go
• Blast radius PR: feat: wire blast-radius to /v1/analysis/impact endpoint #25

[coderabbitai]

🔗 Related PRs

#20 - feat: supermodel factory — AI-native SDLC orchestration [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!