A cross-layer workflow passes unit tests but breaks when client, API, and persistence state arrive in a different order. The affected area is migration rollout.
Repair the migration rollout data migration implementation so it selects safe work under row and risk capacity while explaining skipped candidates.
Evidence
- Affected surface: Full-stack backend focus / migration rollout.
- Observed failure family: plan migration batches.
- Scope policy: qualityState must equal verified.