Task: Give the from-DQ step subjects constants

(Describe what user-visible-or-internal change this task produces.)

(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 four services now name a generated constant instead of a hand-written literal for every from-DQ trigger: refdata 47, dq 6, assets 1, marketdata 1.

Nothing was missing in the generator. It emits a subject constant for a message a codegen operation model declares, and none of these four declared its triggers there: refdata had no such model, assets and marketdata had one but did not name the trigger in it, and dq declared only the payloads and said in prose that the subjects stayed in the registrar. The protocol tables in each component are documentation that the generator never reads. So the fix was to declare them.

Each subject is declared once in a model and projected once into C++. The proof that nothing changed is a comparison rather than two passing runs: the check was run against a clean extraction of the previous commit and against this tree, and the subject sets are identical, 19 streams, 17 consumers and 87 subjects in both, with nothing only before and nothing only after. All 55 constants were also confirmed equal to the target subject rows already seeded in DQ.

Live, the restarted services expose identical stream filters: refdata 94, dq 12, assets 2, marketdata 2.