Task: Catch the artefacts and the id link up

The gate is green on main: the shell library tangles to what is committed, the ER diagram matches the schema, and the site builds.

• The shell library tangles to exactly what is committed.
• The committed ER diagram matches the schema.
• No document links an id that no document defines.

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

Main's gate is green again.

• The shell library tangles to exactly what is committed. Two report_operations commands had gained a parameter in their recipe.
• The ER diagram carries fixings_storage_key, a column the schema had gained and the diagram had not.
• The asset class catalogue's id is spelled the way its own document defines it, so design.org resolves the link and the site builds.