A high-traffic UI flow produces inconsistent ordering between initial load and refresh. The affected area is reactive form.
Repair the reactive form data migration implementation so it selects safe work under row and risk capacity while explaining skipped candidates.
Evidence
- Affected surface: Angular / reactive form.
- Observed failure family: plan migration batches.
- Scope policy: tenantId must equal tenant-primary.