ln-642-layer-boundary-auditor

Detect architectural layer violations by parsing architecture documentation and scanning code files to identify misplaced I/O operations. This auditor flags improper cross-layer calls, like direct database access from the UI layer, enforcing strict adherence to defined layer rules.

Cross-layer consistency issues include incorrect transaction boundary ownership and mixed session management implementations. Scanning code files against architecture documentation detects these mismatches, such as mixing dependency-injected sessions with local ones, ensuring improved software maintainability.

Audit pattern coverage for HTTP client abstractions by scanning code files against defined layer rules to verify consistent application. This identifies inconsistencies and enforces standard architectural patterns uniformly across the codebase for better software maintainability.

Yes, the layer boundary auditor requires architecture documentation to run. You must specify the architecture documentation path so the tool can parse defined layer rules and accurately detect cross-layer consistency issues and I/O violations within the codebase.

Check transaction boundary ownership by scanning code files against parsed architecture documentation. This detects ownership mismatches and cross-layer consistency issues, verifying that transaction boundaries correctly align with their designated architectural layers for improved maintainability.

Mixed session ownership between DI and local implementations occurs when dependency-injected and local sessions are used inconsistently across layers. Scanning code files detects these session ownership mismatches, enforcing cross-layer consistency and adherence to defined layer rules.