dependency-direction-auditor

Use when reviewing import/dependency direction between layers, when infrastructure changes ripple into business logic, when domain code imports from controllers/routes/adapters or framework packages, or when testing business logic requires spinning up infrastructure. Trigger on "why do I need a database to test this?" or when tracing imports that cross layer boundaries. NOT for dependencies within a single layer,…