Task: Author the TaRF fact table

A target redemption forward's own terms have a table, and its target is not written into an accumulator's columns.

(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 target redemption forward has its own fact table. The product's subject matter is the target, and an accumulator has neither a target amount nor target points, which is why the code could not keep routing to equity_accumulator_instruments.

The table is authored from the ORE binding: the underlying, the currency, the fixing amount, the target amount and points and the strike. The fixing amount, the target amount and the strike are money, so all three are exact decimals. Target points are a count of observations rather than an amount, so they stay a continuous quantity. The target amount, the points and the strike are optional because the document may state a strike list instead of one strike, and the barrier that ends the product belongs with the shared strike child.

Verification. Full build clean, the database recreated, the whole suite passes 96 of 96, ores.trading.core.tests passes 1196 assertions in 178 cases, and the table is present in the database after the recreate.

Not done, and named: no mapper writes the table and EquityTaRF still routes to equity_accumulator_instruments. Both move with the mapper migration.