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 command handling implementation so it accepts first operations, recognizes safe repeats, and rejects key reuse with a different payload.
Evidence
- Affected surface: Full-stack backend focus / migration rollout.
- Observed failure family: enforce idempotent operations.
- Scope policy: qualityState must equal verified.