ln-642-layer-boundary-auditor

Auditing layer boundaries detects cross-layer inconsistencies by scanning your codebase for I/O violations outside the infrastructure layer. It reads your architecture file, checks pattern coverage for HTTP client abstractions, and returns violations with file paths and line numbers.

Transaction boundary ownership issues in clean architecture involve commit and rollback logic leaking across inappropriate layers. The auditor detects these cross-layer consistency violations to ensure transaction control remains properly scoped within your domain or infrastructure boundaries.

Auditing session ownership involves scanning the codebase to detect inconsistencies between dependency injection and local session usage. The layer-boundary auditor identifies these cross-layer violations and generates an audit report containing file paths, line numbers, and code context.

Yes, the layer-boundary audit supports hexagonal architecture projects. It also applies to layered and clean designs, using a domain-aware mode to evaluate cross-layer consistency and output findings to an audit report tailored to your project structure.

Generating a cross-layer violation report requires running the auditor against your codebase to scan for I/O boundary violations, transaction ownership issues, and error handling duplication. The resulting report details file paths, line numbers, and code context for each violation.