From 0058f2671c80632b27f91673b4ee1141bddddda9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 11:08:36 +0100 Subject: [PATCH] Design 47 H2: H-A-467, the delivery view shows the pipelines (issue 1983) --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 952668ca..0f92e3c8 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -801,3 +801,15 @@ The lead's one-line answers to the questions H2's develop and review raise (impl engine composes the fixed one); the node-engine's H2 branch (`mesh-host` feat/47-H2) then carries main. The ordering edge (the fixed engine before any module with a package artifact) is a node-engine capability the delivery plan derives, noted for H2b. fix-a-bug-met-twice, P-failure-loud, design-it-as-it-should-be. +- **H-A-467 (the delivery view shows the pipelines, 11:10)** Issue 1983; the operator's ask of 22 Nov 11:05 ("can I see + the status of the pipelines somewhere, with live updates"; the parked idea of 16 Nov). (1) The delivery view (the + module mesh-delivery-view, its web page and its terminal view) gains a pipelines page: it reads the seat + mesh-pipeline-runner's `list` (branch, default main; limit, default 20) and `show` (pipeline; mover) and hears the seat's + events pipeline-started, step-ended, pipeline-ended and re-pinned; its manifest names those invokes and consumes; no + state of its own (P-NATS-native, P3). (2) The list rows: pipeline id, revision and source, started, outcome, the + movers' count, and the counts of steps per outcome (passed, failed, could not run, not asked, waiting, waiting for a + build node, bypassed, nothing to run); one pipeline's page: its mover rows as `show` without a mover answers them + (mover, fingerprint, published version, the mover's step outcomes), and one mover's steps as `show` with the mover + answers them (step, seat, node, outcome, started, ended, why). (3) A delivery links to its pipeline by its source + revision: the pipeline whose source equals the delivery's (list's `source` field); where several share it, the newest. + The page refreshes on the events it hears, never on a timer. P-NATS-native, P3, P11.