check-cross-layer

To verify cross-layer consistency after multi-layer code changes, run checks on touched modules to ensure data flow, imports, and constants remain intact across UI, API, service, and data layers.

Cross-layer architecture verification is a post-change safety net that identifies affected layers and files, signaling diffs and mismatch warnings to guide reviewers after multi-layer modifications.

Check constant usage and imports across UI, API, and service layers by running consistency checks that enforce type contracts and signal mismatches across the modified architectural layers.

Yes, this cross-layer verification works specifically for changes spanning multiple architectural layers, applying impact analysis and dimension checks to ensure no missed updates across touched modules.

The best way to validate data flow and type contracts after architectural modifications is to run post-implementation verification that signals diffs and enforces consistency checks across all affected layers.

Cross-layer mismatch warnings appear after modifying multiple files because the verification process detects broken type contracts, inconsistent imports, or disrupted data flow between the touched architectural layers.