Task: Close the flip story and move coverage to the population story

The flip story closes with only the tasks its arc owns, and every task that belongs to coverage lives in the coverage story.

• The flip story lists no open task and its sprint row says DONE.
• The coverage, legal entity and capture-index tasks live in the stories whose arcs they serve.

(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 flip story closed with six tasks that belong to its arc — the scaffold, the two construction shapes, the commodity facts, the credit reference type, the six family flips and the bond security — and four that belong to coverage left it: the bond product gap, the commodity charter, the credit family and the legal entity. They live in the population story now.

The capture-index task went to this story, where the agile index is wired.

Two documents were deleted: the population story held a second, unstarted copy of the credit task under the same branch as the delivered one, and the flip story held the unused scaffold task every story is born with. Neither had an inbound link from anywhere but the story table that named it.

The flip story's acceptance was rewritten to claim what the arc delivers: every product a planner draws is constructed by name. Whether a planner draws all the codes its family routes is a coverage question, and it is now stated there rather than implied here.