Follow-up to #156 and #159 (second confirmation review).
modules/mesh-cli: SDK pinned at the tag go/v0.1.9 (cd01c370, mesh-sdk #14's merge) instead of the branch pseudo-version.
modules/mesh-delivery: a stalled line for a head the forge never announced carries the pull request's number, which the controller's condition names in its headline (mesh-controller follow-up feat/272-the-terminal-said-explicitly). The test asserting it fails before.
merge-check.sh (go, MESH_CHECK_MODULES=mesh-cli,mesh-delivery, gate from the controller follow-up) passes locally. No other module pins the SDK pseudo-version.
Follow-up to #156 and #159 (second confirmation review).
- `modules/mesh-cli`: SDK pinned at the tag `go/v0.1.9` (cd01c370, mesh-sdk #14's merge) instead of the branch pseudo-version.
- `modules/mesh-delivery`: a stalled line for a head the forge never announced carries the pull request's `number`, which the controller's condition names in its headline (mesh-controller follow-up `feat/272-the-terminal-said-explicitly`). The test asserting it fails before.
`merge-check.sh` (go, `MESH_CHECK_MODULES=mesh-cli,mesh-delivery`, gate from the controller follow-up) passes locally. No other module pins the SDK pseudo-version.
- mesh-cli pins the SDK at its tag now that go/v0.1.9 exists, instead of a
pseudo-version of the branch it was cut from.
- mesh-delivery's stalled line for a head the forge never announced
carries the pull request's number, which the controller's condition
names in its headline.
Deliverynovox/mesh-catalog@645961a87b36 — delivered since 2026-10-09T12:01:55Z
Delivery plan — builds mesh-cli, mesh-delivery → novox; no bus step
tier 0: mesh-cli, mesh-delivery
novox: receives mesh-delivery
Machines
mesh-cli on every machine running it: sent
mesh-delivery on novox: passed — healthy 3 times over 2m27s
mesh-delivery on the rest running it: sent
Transitions
2026-10-09 11:43 (new) → proposed (announced): novox/mesh-catalog#160's head announced
2026-10-09 11:45 proposed → checked (checked): the verdict names this commit
2026-10-09 11:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 11:54 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 11:54 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-09 12:01 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@645961a87b36` — **delivered** since 2026-10-09T12:01:55Z
**Delivery plan** — builds mesh-cli, mesh-delivery → novox; no bus step
- tier 0: mesh-cli, mesh-delivery
- novox: receives mesh-delivery
**Machines**
- mesh-cli on every machine running it: sent
- mesh-delivery on novox: passed — healthy 3 times over 2m27s
- mesh-delivery on the rest running it: sent
**Transitions**
- 2026-10-09 11:43 (new) → proposed (announced): novox/mesh-catalog#160's head announced
- 2026-10-09 11:45 proposed → checked (checked): the verdict names this commit
- 2026-10-09 11:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 11:54 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 11:54 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-09 12:01 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-cli, mesh-delivery)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds mesh-cli, mesh-delivery → novox; no bus step
tier 0: mesh-cli, mesh-delivery
novox: receives mesh-delivery
Run by the build seat on shanks as build-1791546184550007357 (builds --log build-1791546184550007357).
--- the gate: mesh-cli, mesh-delivery
mesh-cli: ok
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:35:23Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T11:35:23Z
modules the change moves:
- mesh-cli (added)
- mesh-delivery (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-delivery
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 34954 strings of 613 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/mesh-cli
ok mesh-cli/cmd/mesh-cli 1.012s
testing modules/mesh-delivery
ok mesh-delivery/cmd/mesh-delivery 1.325s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `645961a8`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-cli, mesh-delivery)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds mesh-cli, mesh-delivery → novox; no bus step
- tier 0: mesh-cli, mesh-delivery
- novox: receives mesh-delivery
Run by the build seat on shanks as `build-1791546184550007357` (`builds --log build-1791546184550007357`).
```
--- the gate: mesh-cli, mesh-delivery
mesh-cli: ok
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:35:23Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T11:35:23Z
modules the change moves:
- mesh-cli (added)
- mesh-delivery (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-delivery
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 34954 strings of 613 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/mesh-cli
ok mesh-cli/cmd/mesh-cli 1.012s
testing modules/mesh-delivery
ok mesh-delivery/cmd/mesh-delivery 1.325s
--- its merge-check-typescript.sh (typescript toolchain)
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #156 and #159 (second confirmation review).
modules/mesh-cli: SDK pinned at the taggo/v0.1.9(cd01c370, mesh-sdk #14's merge) instead of the branch pseudo-version.modules/mesh-delivery: a stalled line for a head the forge never announced carries the pull request'snumber, which the controller's condition names in its headline (mesh-controller follow-upfeat/272-the-terminal-said-explicitly). The test asserting it fails before.merge-check.sh(go,MESH_CHECK_MODULES=mesh-cli,mesh-delivery, gate from the controller follow-up) passes locally. No other module pins the SDK pseudo-version.Delivery
novox/mesh-catalog@645961a87b36— delivered since 2026-10-09T12:01:55ZDelivery plan — builds mesh-cli, mesh-delivery → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
645961a8mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-cli, mesh-delivery)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds mesh-cli, mesh-delivery → novox; no bus step
Run by the build seat on shanks as
build-1791546184550007357(builds --log build-1791546184550007357).