Task: Build the ores.qt bond bridge over the relational model

The qt bridge is the last of the three bond follow-up tasks staged by the deliverable design_bond_relational_model.org. The instrument the forms edit is no longer one row: it is an instrument row, its issue, its fact rows and the issue's child rows, joined by keys. This task delivers the container over the generated part types (handcrafted first; codegen absorbs it only when the parent story's container grammar lands), the qt views over the new row shapes, the wire protocol and the reworked BondInstrumentForm. The deliverable lists the shared schedule and underlyings tables and the container grammar as dependencies of the parent story; the probe resolves with evidence whether the family's views need the shared tables at all, since the issue's child rows live in family tables per the approved answers.

• The container over the generated part types is handcrafted and assembles the instrument with its issue, fact rows and the issue's child rows.
• The qt views present the new row shapes and the BondInstrumentForm works against the new rows; the wire protocol carries the assembled container.
• The probe records with evidence whether the family's views need the shared schedule and underlyings tables, and what the family depends on from the parent story's container grammar.

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

Manual QA scenarios (scaffolded via compass add test_scenario, run through the QA Validation Runner panel) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

Abandoned at sprint 25 close. Sprint 26 replaces the codegen approaches tried so far with one method: for each module, sync codegen and clear its drift. Sprint 26 opens new, clean stories for each module. This story is not carried forward.