Task: Nest the portfolios into a tree

A reader sees where a book sits in the portfolio hierarchy and reads each level's total against the level above and below it.

• A portfolio nests under its parent portfolio.
• A portfolio's figure is its own books plus the portfolios under it.
• Each row states its depth, and the screen indents it.
• A book in no portfolio stands at the top.
• The trade count stays the run's own, not the sum of the rows.

(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 book level reads as a tree.

A portfolio nests under its parent portfolio, and its figure is its own books plus the portfolios under it, so each level can be checked against the level above and below. Each row states its depth and the screen indents it. A book in no portfolio, or in one whose name was not read, stands at the top rather than under a guess.

On run c2a86671 the level draws four rows: Global Portfolio over Banking Book over Liquidity Buffer Portfolio over Liquidity Buffer Bonds, each at 33,709,129.46 HKD over the same eight trades, which is what one book under one chain of portfolios should say.

The totals line states the run's own trade count rather than the sum of the rows, because a tree's rows state the same trades once per level above them.