Task: Populate sprint 28 with the carried stories

Sprint 28 holds the 41 stories carried from sprint 27 — its 21 unfinished stories and the 20 successors their remainders were split into — instead of leaving them in the product backlog inbox.

• Every sprint 27 carry and successor moves out of the inbox into sprint 28, with its ID, tasks and history intact.
• Each moved story names sprint 28 as its parent and carries the sprint_28 tag.
• The sprint's * Stories table lists every moved story.

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