Task: Rename the configuration screens and their words

Every configuration screen, card, journey and translation uses the standard's name for its kind, and no two kinds share a word that makes them read as the same thing.

• No screen title, card or lead uses a bare kind name: each carries the standard's name and its one-line definition.
• The pricing engine page's Settings tab is renamed Parameters. Superseded: the final design has no Parameters tab, because the global parameters have their own tab. The record page has Details, Global parameters, Products, Reports and History, and the apply task built it.
• The English, French and Portuguese strings agree.
• The journeys and the prototypes use the same words as the screens.

(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 two screens and their words are renamed. #3727 renamed the area cards, the list and the record page titles, the journeys and the English, French and Portuguese strings. The screens are Product pricing and Engine run settings, and no card or title uses a bare kind name.

The task asked for the Settings tab to become Parameters. The final design has no Parameters tab: the global parameters have their own tab, and the record page has Details, Global parameters, Products, Reports and History. The apply task built that page. The line is recorded as superseded rather than met.