Import a template file as a draft

Lands the template built, baked and previewable, and NOT published — the slow, failure-prone half moves onto the per-row publish switch where it can fail without costing the import. Returns how the platform read every column of its data: a date stored as text profiles as a dimension, which empties every trend and silently costs the template its place in the gallery, and 5 of 9 entries failed the first live seed for exactly that.

The data lands where the rest of the catalog's data already lives, NOT in the workspace the operator is standing in — a curated template is system content, and a sample inside a customer workspace is one they can delete. Re-importing a slug that exists updates it in place, keeps its filing, and says whether its data was reused (identical bytes resolve to the dataview already here) or landed.

created says which of the two happened — a row added, or a row that already existed shipped anew. The response is the same shape either way and the row itself cannot tell them apart, so a caller offering to undo the import has to be told: on an update there is nothing to undo, only the template that was here before.