Task: Correct the engine settings scenario

The engine settings scenario describes what the screens do, so a failed step names a defect.

• The list step expects the rows of every party the person sees, with the Party column, and a UK session for the two UK rows.
• The French step says how to set the language until a selector exists.

(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 scenario expects the rows of every party the person sees at the group party, and the two UK rows at the UK party. Steps 3 to 11 start in the UK party, because a row changes only in its owning party. The French step says how to set the language until a selector exists. The names in the steps follow the new purpose names.