Part of #13
Blocked by: Define the template draft lifecycle
Question
Which authoring responsibilities belong to the client and which belong to the server across create, update, duplicate, save-from-workout, and merge—including the canonical draft payload, save transaction, idempotency, update concurrency, and whether merge is a first-class server operation or client-side composition?
Part of #13
Blocked by: Define the template draft lifecycle
Question
Which authoring responsibilities belong to the client and which belong to the server across create, update, duplicate, save-from-workout, and merge—including the canonical draft payload, save transaction, idempotency, update concurrency, and whether merge is a first-class server operation or client-side composition?