Task: Scaffold story: Align the web palette with the reviewed scheme

The story rides one pull request: the scaffold documents and the palette change are small enough that splitting them would double the ceremony and prove nothing. The scaffold task is closed on the branch it opened.

(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 story is in the sprint on one branch with both tasks closed there. The palette change and the formatter repair ride the same pull request, whose summary names each.

The design note is not written: this story changes the theme, not a screen, so there is no prototype to argue beside it.