Task: Close the gaps the synthetic journeys found

The subjects the four journeys need exist, with the scoping and the keys the screens ask for.

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

• The FX feed screen needed two of these gaps closed, and Build the FX price feed screen closed them: the GMM component list filters by fx_spot_config_id, and the FX feed list searches its pair, source name and ORE key and sorts on them. The other parent filters the journeys need are still open here.

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.