Hand migrated special prices over to Commerce
What It Does
The schema migration converts former special prices to local-audience cells and preserves qualification context in handover rows. Those rows support the documented Commerce realization step; they do not establish a queue or worker.
The Flow
When Something Fails
Migration rollback depends on the runner's transaction. Later HTTP edits reject a resubmitted migrated audience missing from an existing Commerce register, even when only descriptive fields changed. Domain saving admits audiences differently. Commerce retries, compensation and alerts remain unverified.
Open Design Questions
Product must settle held-audience editing during realization. Commerce must supply a consumer contract covering completion, replay and failure before the downstream hop can be treated as implemented.