The delivery view shows pipelines live (issue 1983, H-A-467) #327

Merged
mesh-tools merged 5 commits from feat/pipelines-view into main 2026-11-22 13:41:04 +00:00
Member

The operator follows the pipelines in the delivery view, live (issue 1983: "can I see the status of the pipelines somewhere, with live updates").

Design lines

Builds design 47 H2, lead answers H-A-467 and its addendum (hq branch design/47-H1-answers-59, 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md), with H-A-376:

  • H-A-467 (1) The delivery view (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.
  • H-A-467 (2) List rows: pipeline id, revision and source, started, outcome, the movers' count and the counts of steps per outcome; one pipeline's page shows its mover rows; one mover's page shows its steps (step, seat, node, outcome, started, ended, why).
  • H-A-467 (3) A delivery links to its pipeline by its source revision (the newest pipeline with that source). The page refreshes on the events it hears, never on a timer.
  • H-A-467 (addendum) The runner's list row gains source, revision and steps (counts per step outcome), so a page's list is one read of the short form; the seat's form is raised once and regenerated; the full form stays.

What changed

  • Runner (mesh-delivery-pipeline, contracts): list's short row carries source revision, catalog graph revision and steps counted per outcome; the mesh-pipeline-runner seat's form is 7, contract regenerated (Go and TypeScript).
  • View (mesh-delivery-view): a pipelines page in the web view and the terminal view (-follow): the newest pipelines of a branch, one pipeline's movers, one mover's steps; read again on the runner's events heard on the module's one pull; the web pages reload on a stream of those changes, the terminal view prints again; each delivered source revision links to the newest pipeline of its source.
  • Review round 1 fixes: a list not read is shown unreadable and read again at the next event, not taken as a refusal; the page takes a limit (web limit query parameter, terminal -limit, 20 by default); the number of pipelines kept for the pages is the manifest setting pipelines-heard (1024 by default).

Tests

  • Unit tests added: internal/view/pipelines_test.go, cmd/mesh-delivery-view/main_test.go, cmd/mesh-delivery-cli/main_test.go, internal/pipeline/read_test.go, manifest_test.go (bounded waits, so a change never said fails instead of hanging).
  • Integration test added: cmd/mesh-delivery-view/integration_test.go (runs in this pull request's check).
  • The lead did not rerun the suites before pushing (the local copy lacks a mesh-sdk working copy); this pull request's check runs them.
  • Merges clean with main at 6f417c88 (dry run git merge --no-commit --no-ff origin/main).

Reviewed-by: mesh-code-reviewer@shanks at d151033dae
Pushed-by: lead-47@shanks
Fixes: issue 1983

The operator follows the pipelines in the delivery view, live (issue 1983: "can I see the status of the pipelines somewhere, with live updates"). ## Design lines Builds design 47 H2, lead answers H-A-467 and its addendum (hq branch `design/47-H1-answers-59`, `03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md`), with H-A-376: - **H-A-467 (1)** The delivery view (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. - **H-A-467 (2)** List rows: pipeline id, revision and source, started, outcome, the movers' count and the counts of steps per outcome; one pipeline's page shows its mover rows; one mover's page shows its steps (step, seat, node, outcome, started, ended, why). - **H-A-467 (3)** A delivery links to its pipeline by its source revision (the newest pipeline with that source). The page refreshes on the events it hears, never on a timer. - **H-A-467 (addendum)** The runner's list row gains `source`, `revision` and `steps` (counts per step outcome), so a page's list is one read of the short form; the seat's form is raised once and regenerated; the full form stays. ## What changed - **Runner (mesh-delivery-pipeline, contracts):** list's short row carries source revision, catalog graph revision and steps counted per outcome; the mesh-pipeline-runner seat's form is 7, contract regenerated (Go and TypeScript). - **View (mesh-delivery-view):** a pipelines page in the web view and the terminal view (`-follow`): the newest pipelines of a branch, one pipeline's movers, one mover's steps; read again on the runner's events heard on the module's one pull; the web pages reload on a stream of those changes, the terminal view prints again; each delivered source revision links to the newest pipeline of its source. - Review round 1 fixes: a list not read is shown unreadable and read again at the next event, not taken as a refusal; the page takes a limit (web `limit` query parameter, terminal `-limit`, 20 by default); the number of pipelines kept for the pages is the manifest setting `pipelines-heard` (1024 by default). ## Tests - Unit tests added: `internal/view/pipelines_test.go`, `cmd/mesh-delivery-view/main_test.go`, `cmd/mesh-delivery-cli/main_test.go`, `internal/pipeline/read_test.go`, `manifest_test.go` (bounded waits, so a change never said fails instead of hanging). - Integration test added: `cmd/mesh-delivery-view/integration_test.go` (runs in this pull request's check). - The lead did not rerun the suites before pushing (the local copy lacks a mesh-sdk working copy); this pull request's check runs them. - Merges clean with main at 6f417c88 (dry run `git merge --no-commit --no-ff origin/main`). Reviewed-by: mesh-code-reviewer@shanks at d151033dae555ab79a8c6e0b9d0e59c6e030d09f Pushed-by: lead-47@shanks Fixes: issue 1983
mesh-tools added 5 commits 2026-11-22 13:41:00 +00:00
The delivery view's pipelines page reads the newest pipelines of a branch in
one read of list's short form, so each row now carries the pipeline's source
revision, its catalog graph revision and its steps counted per outcome. The
runner seat's form is 7; the contract is regenerated; the full form stays.

Issue 1983.
Builds: design 47 H2 H-A-467 (addendum), H-A-376
The operator follows the pipelines in the delivery view: the newest
pipelines of a branch (main by default, the newest 20) with their steps
counted per outcome, one pipeline's mover rows and one mover's steps, read
through the seat mesh-pipeline-runner's list and show and read again on the
runner's events pipeline-started, step-ended, pipeline-ended and re-pinned,
heard on the module's one pull; the web pages reload on a stream of those
changes and the terminal view's -follow prints again, never on a timer. Each
delivered source revision links to the newest pipeline of its source. The
view keeps no state of its own for it.

Issue 1983.
Builds: design 47 H2 H-A-467 (1), (2), (3), H-A-376
The socket answered a refusal and a list it could not read with the same
field, so the terminal view's -follow ended at a list not read yet (the
runner not answering at the view's start) instead of showing it unreadable
and reading it again at the runner's next event. A refusal now has its own
field; a list's page is handed on whatever it holds. The unit tests' waits
for a change are bounded, so a change never said fails instead of hanging.

Issue 1983, review round 1 finding 1.
Builds: design 47 H2 H-A-467 (1), (2)
The design gives list a limit with a default of 20; the view asked 20
always and neither the web page nor the terminal view could ask another.
The web list takes a limit query parameter and the terminal view a -limit
flag; a followed branch's list is read at the default, any other limit is
read at the asking.

Issue 1983, review round 1 finding 2.
Builds: design 47 H2 H-A-467 (1)
The view kept the last change of at most 1024 pipelines for its pages, a
cap written into the code. A cap is a setting with a default (principle
11): the manifest gives pipelines-heard, 1024 by default, written into a
file of the state directory the process reads at its start. The cap is
kept, not removed: without it the pipelines heard grow without end over
the view's life.

Issue 1983, review round 1 finding 3.
Builds: design 47 H2 H-A-467 (1)
mesh-tools merged commit 314a996ed9 into main 2026-11-22 13:41:04 +00:00
mesh-tools deleted branch feat/pipelines-view 2026-11-22 13:41:04 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-delivery#327