Task: Open sprint 27

Sprint 27 exists as an agile artefact with its mission, and it is the current sprint in the version manifest and the agile index.

• sprint_27/sprint.org has its mission and links Sprint 26 as Previous.
• The version manifest lists Sprint 27, and the agile index names it as the current sprint.

Followed How do I open a new sprint? exactly: compass add sprint scaffolded sprint_27, the mission was set from sprint 26's retrospective direction (one pass, the UX), the Previous field points at sprint 26, and the version manifest and the agile index name the new sprint as current. No stories moved from sprint 26: its close resolved every story, and the nineteen unfinished ones wait in the product backlog inbox for sprint 27 planning. The version bump and the vcpkg update ride the same branch as separate commits.

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.

Sprint 27 is scaffolded with the mission "Finish the UX pass: land the remaining journey groups in ores.web, and bring the record screens to the standard." The version manifest lists it from 2026-10-05 with sprint 26 as its Previous, and the agile index names it as the current sprint. Sprint 26 is DONE; its nineteen carried stories wait in the product backlog inbox for sprint 27 planning.