What problem does it solve? Teams struggle to decide whether to keep, adapt, or replace existing code structures without objective evidence, often leading to unnecessary rewrites, parallel implementations, and architectural drift. ## Core Features & Use Cases - Dependency and Cycle Analysis: Maps module boundaries, detects circular dependencies, and flags layer inversions using tools like madge and ripgrep. - Duplication and Coupling Detection: Identifies parallel HTTP clients, competing state stores, god modules, and high-churn high fan-in files. - Keep/Adapt/Replace Decisions with ADRs: Produces justified verdicts per component and records decisions as Architecture Decision Records via the absorbed adr-generator reference. - Use Case: Before a large refactor touching multiple modules, run this review to confirm the change follows existing dependency direction, surface the riskiest files, and document the decision as an ADR. ## Quick Start Review the architecture of the src directory and tell me which components to keep, adapt, or replace with file-level evidence.