Story: Model the handcrafted ores.dq code and generate the artefact tables

Every handcrafted ores.dq table and function has a model, and the artefact tables generate from the same entities as their base tables, so the component keeps regenerating byte-identically. This is pass 1 of the ores.dq clean-up; pass 2 ran the Component Clean Standard over the tree and is done. The analysis behind the split is the investigation.

This story was split from Clean ores.dq to the component clean standard when that story was reworded to the clean-standard pass it delivered and closed DONE at the sprint 26 close on 2026-10-05; the pass 1 task moved here.

• Every table and function in create/dq is generated from a model, or recorded with the reason it is not.
• The 49 artefact tables generate from the same entity model as their base table, with the archetypes that drop the audit and bitemporal columns and add dataset_id.
• The seven orphan artefact tables keep their consumers, each checked by census rather than by generated marker, and the hand-written *_artefact_create.sql files are generated from a model or deleted with the reason recorded.
• dq regenerates byte-identically and stays in COMPONENTS_UNDER_TEST.

Closed on the tasks' state, in the sprint's bookkeeping pass: every task is DONE with its work merged, and the tasks carry the outcomes.