Task: Import a run's configuration in one transaction

An import either stores the whole run or nothing.

• A failure while storing any document leaves no row of the import behind.
• A test forces a failure in the last document and finds the definition empty.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

Raised on 2026-10-04 from the open items left after Import a run's configuration from an ORE input directory and Produce the engine's input from the entities.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.