Task: Implement report post-processing

Ingest the engine's results: unpack the output archive, parse the tabular files, and bulk load them into a result store shaped for the queries that will read it, with provenance separated from measures.

• Each analytic family has one narrow table, and no result is stored as an entity-attribute-value row.
• Ingestion loads a parsed file in bulk rather than writing row by row.
• A repeated ingestion of the same output does not double the rows.

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