Task: Prove a run on generated trades and market data

A report runs to completion on data the system generates rather than on data seeded by hand: a bond book, the counterparties it names and the market data its trades need. What the generated data cannot yet express is written down, because that gap is what a gather must respect.

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

• Two PRs merged on a branch named for this task, and neither delivers it: the one that tells one analytic's failure from another's, and the one that collapses a batch's repeated reasons. Both repair how a run's errors are recorded, not how a run is fed, so the task states no PR of its own and stays open.

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.