cross-layer-consistency

Detect Clean Architecture inconsistencies by running an automated cross-layer audit that uses parallel subagents to verify TypeSpec freshness, DI container bindings, import boundaries, and test coverage conformance across all layers.

Verify dependency injection bindings by applying a consistency check that searches for implementations and confirms DI container wiring for port interfaces. It flags missing bindings to catch infrastructure and presentation layer miswiring.

The best way to check TypeSpec generated output freshness is an automated consistency audit that verifies generated code is current and searches for duplicate or hand-written types indicating architectural drift.

Yes, you can automate pre-release verification by running a cross-layer consistency check that validates use-case wiring, presentation layer imports, and test mock shapes to catch breaking changes before release.

Yes, a cross-layer audit validates test coverage conformance by checking Tests↔Implementation alignment, confirming test existence, and verifying mock shapes against actual use-case and port interfaces.

Infrastructure code leaks into the presentation layer due to incorrect import boundaries. A cross-layer consistency audit detects these leaks by verifying presentation↔use case wiring and flagging unauthorized infrastructure dependencies.