preflight

A cross-layer consistency scan identifies and reports synchronization issues across schema definitions, overlays, platform registries, validation constants, error handlers, and storage repositories before you make non-trivial codebase changes.

A preflight validation scan is a deterministic, audit-friendly check that reads your current codebase state, validates assumptions, and surfaces stale or missing files across schema, registry, and test layers to prevent risky edits.

Detect cross-layer inconsistencies by running a preflight scan that reads current states across schema definitions, overlays, platform registries, and storage repositories, validating assumptions and documenting synchronization gaps.

Run a pre-implementation consistency check before any non-trivial codebase modification to ensure schema definitions, validation constants, error handlers, and storage repositories are synchronized, guiding safe edits.

Yes, the preflight scan explicitly reads existing fixtures and error handlers, validating their assumptions against schema definitions and platform registries, and reporting inconsistencies to document findings for safe edits.

The preflight consistency scan is limited to identifying and reporting inconsistencies across codebase layers before changes; it does not perform edits itself, but documents findings to guide safe modifications.