verify-seed-integrity

Prevent orphan seed files by validating that every seed-data definition is imported by seed-test-new.ts orchestration. This ensures all seed files remain synchronized within your single source of truth infrastructure.

Align Phase 0 truncation targets with seed inserts by verifying their synchronization during validation. This maintains idempotency and prevents data drift when running e2e backend testing workflows locally or in CI.

Avoid hard-coded expected counts in verification.ts to promote data-driven checks. Hard-coded expectations cause seed infrastructure integrity drift and fail to validate dynamic data accurately across testing environments.

Run seed integrity validation in both CI and local development environments. It guards against drift when seed data changes or workflows are updated, emitting a pass or fail signal for subsequent steps.

A single source of truth for seed data ensures definitions, test orchestration, and verification checks stay in sync. This infrastructure validation targets orphans, truncation alignment, and hard-coded expectations.

Run seed infrastructure integrity validation after updating any seed data or related seed workflow files. This confirms SSOT integrity and prevents orphan seeds or truncation misalignment before subsequent steps.