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