Task: Fix the defects the bond family review found

Close the defects the review found in the bonds instrument family, so the money that crosses the import boundary keeps its digits and the model states what the schema and the domain type already assume.

• The money columns that reach the persisted domain through a binary float are read with a decimal parse instead, or each is recorded with the evidence for why it cannot be.
• bond_forward.premium_amount is exact decimal in the model, the generated domain type and the column.
• instrument_option.premium_amount and instrument_option_exercise_price.price use numeric(38, 12), the scale the family's other money columns use.
• The money-column check flags a money column typed text, and its baselines are seeded rather than empty.
• The schedule parent and schedule-date child agree on the set of owner roles they admit.
• bond_repo.repo_index and bond_trs.funding_index generate an optional domain type, matching their nullable columns.
• The model that cites doc/knowledge/architecture/trading_bond_relational_model.org cites a page that 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.