Let the build modules answer their own step results and toolchains, so a fetch's workspace and a build's digest can be read (issue 1562, build-module half) #410

Merged

mesh-tools merged 1 commits from fix/1562-read-steps into main 2026-10-21 10:26:14 +00:00

Conversation 2 Commits 1 Files Changed 16

+734 -22

mesh-tools commented 2026-10-21 10:10:00 +00:00

Member

Copy Link

Copy Source

Issue 1562, the build-module half (ADR 0469 §2: a long step finishes on <node>.<id> of the module's steps state). Met twice: R4c-3's live check could not read any step's result.

• mesh-build-go: build_go_step {id} (the stored step: tool, state, times, reason and result, e.g. a fetch's workspace id; id or <node>.<id>, another node's key refused), build_go_steps {limit} (this node's latest, newest first), build_go_toolchains (every key of the toolchains state). mesh-build-node: the same as build_node_*.
• They read the module's own state (declared, no new grant) and run outside the toolchain guard, so a node whose go or node cannot run can still say what its steps did.

Tests: read_test.go in each module; the reviewer broke the code eight ways and each made a test fail. mesh-controller.try build-1792576647956408729 passed at c33b83dc (51 s).

Not in this pull request: the indexer half of 1562 (mesh-delivery), so 1562 stays open. Later: issue 1645 (read.go is copied between the two modules; it belongs in mesh-sdk's buildstep).

Reviewed-by: reviewer-1562@shanks at c33b83dce7

Issue 1562, the build-module half (ADR 0469 §2: a long step finishes on `<node>.<id>` of the module's steps state). Met twice: R4c-3's live check could not read any step's result. - mesh-build-go: `build_go_step {id}` (the stored step: tool, state, times, reason and result, e.g. a fetch's workspace id; id or `<node>.<id>`, another node's key refused), `build_go_steps {limit}` (this node's latest, newest first), `build_go_toolchains` (every key of the toolchains state). mesh-build-node: the same as build_node_*. - They read the module's own state (declared, no new grant) and run outside the toolchain guard, so a node whose go or node cannot run can still say what its steps did. Tests: read_test.go in each module; the reviewer broke the code eight ways and each made a test fail. mesh-controller.try build-1792576647956408729 passed at c33b83dc (51 s). Not in this pull request: the indexer half of 1562 (mesh-delivery), so 1562 stays open. Later: issue 1645 (read.go is copied between the two modules; it belongs in mesh-sdk's buildstep). Reviewed-by: reviewer-1562@shanks at c33b83dce7d53a26e9b23d5d973f206e910968dc

mesh-tools added 1 commit 2026-10-21 10:10:00 +00:00

Read a build module's steps and toolchains states with its own tools, so a step's result and the reported toolchain can be checked live (issue 1562) c33b83dce7

mesh-tools commented 2026-10-21 10:10:11 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@c33b83dce7d5 — covered since 2026-10-21T10:59:40Z

Delivery plan — builds mesh-build-go, mesh-build-node → g14, novox, shanks; no bus step

• tier 0: mesh-build-go, mesh-build-node
• g14: receives mesh-build-go, mesh-build-node
• novox: receives mesh-build-go, mesh-build-node
• shanks: receives mesh-build-go, mesh-build-node
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-build-go, mesh-build-node is judged on its first machine

Machines

• dev-tools on every machine running it: sent
• mesh-build-go on every machine running it: sent
• mesh-build-node on every machine running it: sent
• mesh-sdk on every machine running it: sent
• mesh-tools on every machine running it: sent
• audit-logger on every machine running it: sent
• confluence on every machine running it: sent
• gitea on every machine running it: sent
• gitlab on every machine running it: sent
• jira on every machine running it: sent
• lab on every machine running it: sent
• mesh-catalog on every machine running it: sent
• model-usage on every machine running it: sent
• openai-consumer on every machine running it: sent
• route-adapter on every machine running it: sent
• showcase on every machine running it: sent

Transitions

• 2026-10-21 10:10 (new) → proposed (announced): novox/mesh-catalog#410's head announced
• 2026-10-21 10:25 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-21 10:25 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-21 10:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-21 10:36 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
• 2026-10-21 10:59 delivering → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-catalog@e023f69989 (merged as b5dbfbb7 into main, walk plan-1792576951664537534)

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@c33b83dce7d5` — **covered** since 2026-10-21T10:59:40Z **Delivery plan** — builds mesh-build-go, mesh-build-node → g14, novox, shanks; no bus step - tier 0: mesh-build-go, mesh-build-node - g14: receives mesh-build-go, mesh-build-node - novox: receives mesh-build-go, mesh-build-node - shanks: receives mesh-build-go, mesh-build-node - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-build-go, mesh-build-node is judged on its first machine **Machines** - dev-tools on every machine running it: sent - mesh-build-go on every machine running it: sent - mesh-build-node on every machine running it: sent - mesh-sdk on every machine running it: sent - mesh-tools on every machine running it: sent - audit-logger on every machine running it: sent - confluence on every machine running it: sent - gitea on every machine running it: sent - gitlab on every machine running it: sent - jira on every machine running it: sent - lab on every machine running it: sent - mesh-catalog on every machine running it: sent - model-usage on every machine running it: sent - openai-consumer on every machine running it: sent - route-adapter on every machine running it: sent - showcase on every machine running it: sent **Transitions** - 2026-10-21 10:10 (new) → proposed (announced): novox/mesh-catalog#410's head announced - 2026-10-21 10:25 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 10:25 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 10:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 10:36 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-21 10:59 delivering → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-catalog@e023f69989ab (merged as b5dbfbb7 into main, walk plan-1792576951664537534) The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools commented 2026-10-21 10:25:32 +00:00

Author

Member

Copy Link

Copy Source

Merge check at c33b83dc
Judged: head c33b83dce7d5 merged into trunk 940594b07478; read beside it: mesh-controller 0205b8f7080a, mesh-controller-main ff42f2183900, mesh-host c5c4caa2a4ab, mesh-tools e0fadc43d9dd

• mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-build-go, mesh-build-node)
• 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-build-go, mesh-build-node → g14, novox, shanks; no bus step

• tier 0: mesh-build-go, mesh-build-node
• g14: receives mesh-build-go, mesh-build-node
• novox: receives mesh-build-go, mesh-build-node
• shanks: receives mesh-build-go, mesh-build-node
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-build-go, mesh-build-node is judged on its first machine
• read by no module's build: modules/mesh-build-go/README.md, modules/mesh-build-go/cmd/mesh-build-go/module_test.go, modules/mesh-build-go/cmd/mesh-build-go/read_test.go, modules/mesh-build-node/README.md, modules/mesh-build-node/cmd/mesh-build-node/module_test.go, modules/mesh-build-node/cmd/mesh-build-node/read_test.go

Run by the build seat on ace as build-1792577408470803265 (builds --log build-1792577408470803265).

--- the gate: mesh-build-go, mesh-build-node
mesh-build-go: ok, 9 tool(s), keeps state toolchains, keys, steps, ready: mesh-build-go.own-runtime by its tool build_go_health every 1m0s
mesh-build-node: ok, 8 tool(s), keeps state toolchains, keys, steps, ready: mesh-build-node.own-runtime by its tool build_node_health every 1m0s
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-21T10:16:45Z says they run
composing every machine as the mesh is
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
composing every machine with the change
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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-21T10:16:45Z

modules the change moves:
  - mesh-build-go (changed)
  - mesh-build-node (changed)

machines:
  - a machine (f35): composes; the change adds 0 resource(s) and removes 3 (-package:mesh-build-go.go, -package:mesh-build-node.nodejs, -package:mesh-build-node.npm)
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes; the change adds 0 resource(s) and removes 3 (-package:mesh-build-go.go, -package:mesh-build-node.nodejs, -package:mesh-build-node.npm)
  - a machine (yvbpsm): composes; the change adds 0 resource(s) and removes 3 (-package:mesh-build-go.go, -package:mesh-build-node.nodejs, -package:mesh-build-node.npm)

a merge would rebuild 2 module(s) in 1 tier(s): mesh-build-go, mesh-build-node

notes:
  - modules/mesh-build-go/README.md, modules/mesh-build-go/cmd/mesh-build-go/module_test.go, modules/mesh-build-go/cmd/mesh-build-go/read_test.go, modules/mesh-build-node/README.md, modules/mesh-build-node/cmd/mesh-build-node/module_test.go and modules/mesh-build-node/cmd/mesh-build-node/read_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words and 70 daemons' lines, none in the 58328 strings of 900 files
ok  	git.novox.be/novox/mesh-catalog/checks/toolchains	0.010s
toolchains: go, nodejs and npm are declared only by their owners
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.011s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.008s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.015s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/owned	0.008s
owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.012s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.219s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.014s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.010s
templates: no module keeps a file's text inline but the 0 listed
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: 59, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.196s
testing modules/mesh-build-go
ok  	meshbuildgo/cmd/mesh-build-go	14.714s
testing modules/mesh-build-node
ok  	meshbuildnode/cmd/mesh-build-node	1.253s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `c33b83dc` Judged: head `c33b83dce7d5` merged into trunk `940594b07478`; read beside it: mesh-controller `0205b8f7080a`, mesh-controller-main `ff42f2183900`, mesh-host `c5c4caa2a4ab`, mesh-tools `e0fadc43d9dd` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-build-go, mesh-build-node) - `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-build-go, mesh-build-node → g14, novox, shanks; no bus step - tier 0: mesh-build-go, mesh-build-node - g14: receives mesh-build-go, mesh-build-node - novox: receives mesh-build-go, mesh-build-node - shanks: receives mesh-build-go, mesh-build-node - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-build-go, mesh-build-node is judged on its first machine - read by no module's build: modules/mesh-build-go/README.md, modules/mesh-build-go/cmd/mesh-build-go/module_test.go, modules/mesh-build-go/cmd/mesh-build-go/read_test.go, modules/mesh-build-node/README.md, modules/mesh-build-node/cmd/mesh-build-node/module_test.go, modules/mesh-build-node/cmd/mesh-build-node/read_test.go Run by the build seat on ace as `build-1792577408470803265` (`builds --log build-1792577408470803265`). ``` --- the gate: mesh-build-go, mesh-build-node mesh-build-go: ok, 9 tool(s), keeps state toolchains, keys, steps, ready: mesh-build-go.own-runtime by its tool build_go_health every 1m0s mesh-build-node: ok, 8 tool(s), keeps state toolchains, keys, steps, ready: mesh-build-node.own-runtime by its tool build_node_health every 1m0s 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-21T10:16:45Z says they run composing every machine as the mesh is HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus composing every machine with the change HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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-21T10:16:45Z modules the change moves: - mesh-build-go (changed) - mesh-build-node (changed) machines: - a machine (f35): composes; the change adds 0 resource(s) and removes 3 (-package:mesh-build-go.go, -package:mesh-build-node.nodejs, -package:mesh-build-node.npm) - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes; the change adds 0 resource(s) and removes 3 (-package:mesh-build-go.go, -package:mesh-build-node.nodejs, -package:mesh-build-node.npm) - a machine (yvbpsm): composes; the change adds 0 resource(s) and removes 3 (-package:mesh-build-go.go, -package:mesh-build-node.nodejs, -package:mesh-build-node.npm) a merge would rebuild 2 module(s) in 1 tier(s): mesh-build-go, mesh-build-node notes: - modules/mesh-build-go/README.md, modules/mesh-build-go/cmd/mesh-build-go/module_test.go, modules/mesh-build-go/cmd/mesh-build-go/read_test.go, modules/mesh-build-node/README.md, modules/mesh-build-node/cmd/mesh-build-node/module_test.go and modules/mesh-build-node/cmd/mesh-build-node/read_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words and 70 daemons' lines, none in the 58328 strings of 900 files ok git.novox.be/novox/mesh-catalog/checks/toolchains 0.010s toolchains: go, nodejs and npm are declared only by their owners ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.008s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.015s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/owned 0.008s owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory ok git.novox.be/novox/mesh-catalog/checks/secrets 0.012s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.219s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.014s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.010s templates: no module keeps a file's text inline but the 0 listed 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: 59, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.196s testing modules/mesh-build-go ok meshbuildgo/cmd/mesh-build-go 14.714s testing modules/mesh-build-node ok meshbuildnode/cmd/mesh-build-node 1.253s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-tools merged commit 710cfbd622 into main 2026-10-21 10:26:14 +00:00

mesh-tools deleted branch fix/1562-read-steps 2026-10-21 10:26:14 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#410