Task: Model the shared reference configuration

A run reaches the reference configuration it needs by foreign key, so reporting holds no copy of conventions, calendars, currencies, counterparties or netting sets.

• Each reference set the taxonomy lists has a model and an owner, and the report definition references it by key.
• No reference configuration is duplicated into reporting.
• The run store imports and exports the currency configuration and calendar adjustments a run document names, as world data the import adds only when the tenant lacks it, so a package holds every file its run document names.

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