Task: Discuss the _config suffix for the curve configuration tables

Decide with the operator whether the curve configuration tables take a _config suffix. A row holds the recipe for building a curve, never the curve's data, but names such as yield_curve, fx_volatility and curve_definition read as if they held data.

• The operator has decided whether to rename, and which tables the rename covers.
• If the decision is to rename, a follow-up task holds the rename and its migration.

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

Raised by the operator during step 4b of Round trip the curve configuration: a curve has data, a curve configuration has only the shape of that data, and the table names should not blur the two. The operator asked for this conversation to wait until the curve configuration work reaches it, so it sits last in the story.

Tables to cover, as of step 4a: curve_definition, yield_curve, equity_curve, default_curve, inflation_curve, commodity_curve, intraday_power_curve, curve_security, fx_volatility, yield_volatility, base_correlation, curve_correlation, and the step 4b to 4d tables. The lookups (curve_segment_type, day_counter, curve_section) and curve_configuration itself already say what they are.

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.

Decided by the operator on 2026-10-03, after the curve configuration round trip closed: the per-entry curve configuration tables take a _config suffix (yield_curve_config, fx_volatility_config and so on), matching curve_volatility_config. curve_definition keeps its name, because it is the header row other documents refer to. Child tables (segments, quotes, terms, factors, price segments, smile parameters) and the tables whose names already say configuration keep theirs.

The rename is Rename the curve configuration tables with a _config suffix.