Task: Name the Acme engine settings by purpose

A person reads the name and the description of an Acme engine settings configuration and knows what it is for, for example intraday risk.

• Every Acme engine settings configuration has a purpose name and a description that states the purpose.
• The Acme seed generator derives the names, so a regenerated dataset keeps them.

(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.

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.

The Acme engine settings are named for their purpose: "Exposure simulation" (four threads) and "Valuation and risk" (one thread), one pair for each party that has them. The description states the purpose and the thread count, and no longer lists the reports. The generator derives the names and descriptions from one table, so a regenerated dataset keeps them. The ids derive from the names, so they changed.