Task: Scaffold story: Implement the operations journeys in ores.web

Land the story that owns the Operations journey group: the story page, the six tasks, the sprint row and the programme's order table. The design is already accepted — the five journeys and the throwaway prototype carry it — and this task does not touch the journey documents.

• The story exists in Sprint 26, and the sprint's * Stories table links it.
• The programme story's order table names this story against the Operations group.
• The six tasks are wired into the story's * Tasks table: the five data-model linkages are one task each, and the screens build is one task.
• The story names the accepted prototype branch as its design record and states that the prototype is ported, not merged.
• compass lint passes and the pages publish.

1. Scaffold the story with compass story new.
2. Write the goal, the acceptance, the plan, the decisions, the out-of-scope list and the documents.
3. Scaffold the six tasks with compass task new, so each one is wired into the story's * Tasks table.
4. Wire the story into the sprint's * Stories table, and into the programme's order table.
5. Raise the scaffold PR. The six tasks stay BACKLOG until the PR merges.

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.

• The group is the ninth in Implement the user journeys in ores.web, after Tenancy. It was the catalogue's last group written, and it is the only one whose design arrived settled: the five journeys were written and walked against a clickable prototype in sprint 26, and the user accepted the walk on 2026-10-04.
• The prototype branch prototype/operations-journeys at 285519db99 is the design record and never merges. Each journey names the branch and its route under * Prototype.
• The five captures the walk filed are the story's first tasks: the heartbeat host (A1D7FC12), the roster read (B7B53CD1), the login-answer database (B7AE6C4F), the grid read's scope (3621E2BC) and the node summary's failure fields (8C1D6E61).
• The journey documents are fresh — written on 2026-10-04 against this tree — so no survey task precedes the build: each task re-checks its own claims as it works.
• The tree at the branch point already carries the journey runtime from the Setup group (projects/ores.web/packages/web/src/journeys/runtime.ts).
• The shell already carries one operations read: compute grid-stats and its recipe at projects/ores.shell/scripts/library/compute/, so the grid tasks verify the shell side as they change the read.

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.

Done 2026-10-04. PR #2622.

The Operations group has a story, six tasks, a row in sprint 26 and a row in the programme's order table:

Two facts were checked while scaffolding, and both are recorded on the story:

• The five journey documents are fresh. They were written and accepted against this tree on 2026-10-04, so no survey task precedes the build, and each task re-checks its own claims as it works.
• Both clients' starting points exist on the tree. The journey runtime is already there (projects/ores.web/packages/web/src/journeys/runtime.ts, landed by the Setup group), and the shell already carries one operations read: compute grid-stats and its recipe under projects/ores.shell/scripts/library/compute/.

The sprint's * Stories row needed one hand-edit: compass story new left it at BACKLOG while the story opened STARTED. The row states STARTED with 2026-10-04 as its start.

Verification: compass lint passes on this branch (filetags and generator markers valid; the durable-document link advisory stands at 224 links across 105 files). compass site page rebuilt 19 page(s) with 0 failure(s). The story row was read back from the sprint's * Stories table, and its six tasks were wired into its * Tasks table by compass task new.