T

jschoubben db942e9204 §88: a restarted runner asks the steps placed and not yet asked

Starter.Resume asks again each running step of a branch's running pipelines under the id it was placed under; the branch
view tells Views.OnReady once when it holds its first half, and the runner resumes that branch then.

Builds: design 47 G §22, §24, §88

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

2026-11-11 23:40:22 +01:00

contracts

A-102: the runner names the accepted kinds it puts steps on in invokes, and build joins the step inputs

2026-11-11 23:38:37 +01:00

modules

§88: a restarted runner asks the steps placed and not yet asked

2026-11-11 23:40:22 +01:00

sdk

SD4 (step key parser): ParseStepKey reads both forms and answers the asker

2026-11-11 20:36:06 +01:00

.gitignore

Nodes compose: placement from the catalogue, node records, self wants, own and pair credentials, core boxes and the authority from the vault (issue 1126)

2026-10-26 19:30:18 +01:00

README.md

Begin mesh-delivery with its README and its own check (ADR 0428)

2026-10-18 16:07:25 +00:00

README.md

mesh-delivery

Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).

Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.