2b-layer-boundary-repair

Fix layer-boundary violations by applying deterministic, mechanical repairs to your Python codebase. This process targets architectural layers like entities and use_cases, handling missing directories and __init__.py placeholders without manual intervention.

The best way to repair missing architectural layer directories is using automated scaffolding generation. It creates required layer directories like interface_adapters and infrastructure under src/, and automatically adds __init__.py placeholders to ensure Python package recognition.

Yes, this layer-boundary repair approach supports typical Clean Architecture layers. It specifically targets layers such as entities, use_cases, interface_adapters, and infrastructure, creating missing subdirectories like gateways and presenters under interface_adapters.

Log architectural layer modifications by generating a structured todo.md file in the docs directory. This file lists all actions taken or proposed during the layer-boundary repair, providing a clear audit trail for subsequent codebase review.

Yes, you can preview layer-boundary repairs using the built-in dry-run mode. This mode identifies missing layer scaffolding and displays proposed changes without enacting them, ensuring you can validate modifications before applying them to the repository.