Task: Say the run failed in one sentence

(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 row that says a run failed says it in one sentence. The engine's long account, with the reasons it repeats, stays on the instance as the run's output message, and the reasons are the rows beside it.

A reason that runs past two hundred characters is cut there, so the row stays a sentence rather than a paragraph.

Proven by the reporting suites: a failure carrying the engine's five-line account stores "The run's compute job failed with outcome 3: The engine's analytic failed." and nothing of the lines that follow.