consumer-data-dictionarylisted

# consumer-data-dictionary - **Roadmap feature:** F040 (proposed; the roadmap-ledger row is deferred to integration time -- see research.md section 1.4; not yet a confirmed ledger entry). **On-disk spec:** `specs/101-consumer-data-dictionary/`. - **Authority category:** Product Module / `artifact-writing` (the F024 enumerated declaration -- see `docs/architecture/product-modules.md`). Today, "what does this column/measure mean" answers exist but are scattered across BUILDER-facing artifacts nobody wrote for a self-serve analyst: a gold column's business meaning lives as a mapping-decision `reason` string inside `mappings/<table>/source-map.yaml` (written for the mapping-gate reviewer, not a report reader); a measure's plain-language meaning lives as `formula_intent` inside `mappings/<table>/metrics/<Metric>.yaml` (already consumer-legible prose); and the handoff pack's own data-dictionary section exists to satisfy the Publish Ready gate, not to serve the analyst who later queries the published model. This skill is the COMPOSER that assembles those scattered, already-committed artifacts into ONE ordered, plain-language reference for the CONSUMER. It FILLS the dictionary; it originates no meaning and owns no truth. Every entry cites the committed source it came from; where no committed consumer-legible meaning exists, the entry is an explicit GAP, never invented prose. ## Boundary against neighbouring shipped work (read first) - **F013 BI Handoff Pack** (`templates/ha