Create a task and its full step list in one call. The operation is wrapped in a database transaction. Any validation failure rolls back the task and all previously-saved steps.

Body shape: { "task": {...}, "steps": [...] }. The task's steps ordering array is derived server-side from the position of each step in steps[]. Any caller-supplied task.steps is ignored.

Steps are saved under the SCENARIO_PASTE scenario. Observation steps may include a feedback value with linked: true and an embedded taskJson object; the server auto-creates the linked subtask and wires it up.

Required fields:

• task.name
• task.product_id
• steps (array, may be empty)

No idempotency mechanism. Retrying a failed network request may create a duplicate task. Retry only after explicit failure (status >= 400).