Task: Measure report processing and record a baseline

Instrument the pipeline and record a baseline, so that the architecture's claims about cost can be checked rather than asserted: which step dominates, whether scope reads are selective, whether the artifact digest is repaid by cache hits, and whether ingestion can keep up with execution.

• The measurements listed in Report processing data characteristics are collected and recorded on the task.
• Each measurement is recorded against the decision it was meant to inform, including any that contradict the design.

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