novox/mesh-host
8
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Feature 57 (config and provisioning): the node-engine's part, into its release branch #114

Merged
mesh-tools merged 1 commits from 57-config-and-provisioning into feat/57-config-and-provisioning 2026-10-16 01:32:25 +00:00
Conversation 8 Commits 1 Files Changed 31
+1774 -43
mesh-tools commented 2026-10-15 21:13:39 +00:00
Member
Copy Link
Copy Source

Feature 57's mesh-host work as one commit (5a7ec377, tree equal to the local feature head 0c668408), into the release branch feat/57-config-and-provisioning (ADR 0358). Merging here delivers nothing; the release branch goes to main with the feature's bundled delivery plan.

Issues: 662, 673, 676, 755, 764, 786, 833 (main merged into the feature branch), 835, 851, and 804 (the SDK pin moves to mesh-sdk d3e18250, the feature's SDK on its release branch).

Review: Opus final look APPROVE at 1f1a912; 0c668408 adds only the SDK re-pin (go.mod, go.sum), tests and merge-check.sh green locally (real-bus tests not run here: no nats-server).

Feature 57's mesh-host work as one commit (5a7ec377, tree equal to the local feature head 0c668408), into the release branch `feat/57-config-and-provisioning` (ADR 0358). Merging here delivers nothing; the release branch goes to main with the feature's bundled delivery plan. Issues: 662, 673, 676, 755, 764, 786, 833 (main merged into the feature branch), 835, 851, and 804 (the SDK pin moves to mesh-sdk d3e18250, the feature's SDK on its release branch). Review: Opus final look APPROVE at 1f1a912; 0c668408 adds only the SDK re-pin (go.mod, go.sum), tests and merge-check.sh green locally (real-bus tests not run here: no nats-server).
mesh-tools added 1 commit 2026-10-15 21:13:40 +00:00
Land feature 57's node-engine work on its release branch
mesh/merge-gate head 5a7ec3775b98 merged into trunk 53fd32618916 beside mesh-controller#346@c711e622 — pass: builds mesh-host → ace, g14, novox, shanks; no…
Details
mesh/repo-check head 5a7ec3775b98 merged into trunk 53fd32618916 beside mesh-controller#346@c711e622 — pass: [release feat/57-config-and-provisioning, judg…
Details
mesh/delivery stopped: its walk plan-1792114347281764422 was stopped by a person (mesh-controller): mesh-host#114 merged into the release branch feat/57-…
Details
mesh/delivery-group group 57-config-and-provisioning stopped: a member was stopped
Details
5a7ec3775b 
The node-engine renders the feature's templates, collections and moved
providers' files, on the SDK the feature's modules build on (feature 57,
config and provisioning).
mesh-tools commented 2026-10-15 21:13:44 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-host@5a7ec3775b98 — stopped since 2026-10-16T01:33:33Z

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • 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-host is judged on its first machine

Group 57-config-and-provisioning, in order: novox/mesh-controller@c711e62287 → novox/mesh-host@5a7ec3775b

  • composed together: pass — [release feat/57-config-and-provisioning, judged by the group's controller 84847e5c6530] every machine composes with the change as it did without (4 of 4 compose)

Machines

  • mesh-host on every machine running it: sent

Transitions

  • 2026-10-16 00:34 rejected → proposed (recheck): issue 867: mesh-controller#351 (a07dd78c, the recheck asks mesh-delivery on a bus of its own) delivered to novox at 02:34; judge it beside its sibling mesh-controller#346 at c711e622, the second half of ADR 0382's live proof.
  • 2026-10-16 00:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 00:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 01:08 ready → proposed (recheck): issue 867: mesh-controller#352 (d70bb1f3, the group's own controller judges its composed check, ADR 0239 §14) delivered to all four machines at 03:07; judge #114 and the group 57-config-and-provisioning again.
  • 2026-10-16 01:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 01:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 01:21 ready → proposed (recheck): issue 867: mesh-catalog#327 (173c5d5e, a member's recheck puts the group's composed check out of date, ADR 0323 §6) delivered to novox at 03:21; judge #114 and ask group 57-config-and-provisioning again under its own controller.
  • 2026-10-16 01:25 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 01:25 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 01:32 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-16 01:32 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-16 01:33 delivering → stopped (stop): its walk plan-1792114347281764422 was stopped by a person (mesh-controller): mesh-host#114 merged into the release branch feat/57-config-and-provisioning, not main; this walk would send a node-engine judged only against that release branch to ace, g14, novox and shanks, which ADR 0358 §7 forbids. Stopped before any send by 57-lead@novox; feature 57 reaches the machines through its release pull requests into main.

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-host@5a7ec3775b98` — **stopped** since 2026-10-16T01:33:33Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - 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-host is judged on its first machine **Group** `57-config-and-provisioning`, in order: novox/mesh-controller@c711e62287ff → novox/mesh-host@5a7ec3775b98 - composed together: pass — [release feat/57-config-and-provisioning, judged by the group's controller 84847e5c6530] every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-host on every machine running it: sent **Transitions** - 2026-10-16 00:34 rejected → proposed (recheck): issue 867: mesh-controller#351 (a07dd78c, the recheck asks mesh-delivery on a bus of its own) delivered to novox at 02:34; judge it beside its sibling mesh-controller#346 at c711e622, the second half of ADR 0382's live proof. - 2026-10-16 00:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 00:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 01:08 ready → proposed (recheck): issue 867: mesh-controller#352 (d70bb1f3, the group's own controller judges its composed check, ADR 0239 §14) delivered to all four machines at 03:07; judge #114 and the group 57-config-and-provisioning again. - 2026-10-16 01:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 01:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 01:21 ready → proposed (recheck): issue 867: mesh-catalog#327 (173c5d5e, a member's recheck puts the group's composed check out of date, ADR 0323 §6) delivered to novox at 03:21; judge #114 and ask group 57-config-and-provisioning again under its own controller. - 2026-10-16 01:25 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 01:25 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 01:32 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 01:32 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-16 01:33 delivering → stopped (stop): its walk plan-1792114347281764422 was stopped by a person (mesh-controller): mesh-host#114 merged into the release branch feat/57-config-and-provisioning, not main; this walk would send a node-engine judged only against that release branch to ace, g14, novox and shanks, which ADR 0358 §7 forbids. Stopped before any send by 57-lead@novox; feature 57 reaches the machines through its release pull requests into main. The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-tools commented 2026-10-15 21:14:56 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 5a7ec377
Judged: head 5a7ec3775b98 merged into trunk 53fd32618916; read beside it: mesh-catalog 1a2c917abfdb, mesh-controller fcdecb436117, mesh-controller-main 7543f64911c5, mesh-tools 6b3e15042fee

  • mesh/merge-gate: FAIL — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] feat/57-config-and-provisioning's controller does not build with this change's validator: docker run --label mesh.build=build-1792098822994191065 --volume /var/lib/build-agent/judge-cache/homes/build-1792098822994191065:/var/lib/build-agent/judge-cache/homes/build-1792098822994191065 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792098822994191065 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792098822994191065/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792098822994191065/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host)
  • mesh/repo-check: PASS — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • 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-host is judged on its first machine
  • read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go

Run by the build seat on shanks as build-1792098822994191065 (builds --log build-1792098822994191065).

--- judged for the release branch feat/57-config-and-provisioning by its controller at fcdecb436117, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at fcdecb436117, mesh-controller-main main at 7543f64911c5, mesh-tools main at 6b3e15042fee
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261015210729-d3e182503c19
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.016s
ok  	github.com/novox/mesh-host/cmd/mesh-host	8.228s
ok  	github.com/novox/mesh-host/examples	1.029s
ok  	github.com/novox/mesh-host/internal/accounts	2.135s
ok  	github.com/novox/mesh-host/internal/apply	13.379s
ok  	github.com/novox/mesh-host/internal/bootstrap	6.344s
ok  	github.com/novox/mesh-host/internal/bundle	1.037s
ok  	github.com/novox/mesh-host/internal/declaration	1.082s
ok  	github.com/novox/mesh-host/internal/filling	1.758s
ok  	github.com/novox/mesh-host/internal/firewall	1.841s
ok  	github.com/novox/mesh-host/internal/identity	1.366s
ok  	github.com/novox/mesh-host/internal/image	1.033s
ok  	github.com/novox/mesh-host/internal/inventory	1.063s
ok  	github.com/novox/mesh-host/internal/link	10.554s
ok  	github.com/novox/mesh-host/internal/liveness	2.201s
ok  	github.com/novox/mesh-host/internal/meshcli	1.571s
ok  	github.com/novox/mesh-host/internal/network	1.073s
ok  	github.com/novox/mesh-host/internal/outward	1.041s
ok  	github.com/novox/mesh-host/internal/profile	1.638s
ok  	github.com/novox/mesh-host/internal/reachable	1.039s
ok  	github.com/novox/mesh-host/internal/store	1.851s
ok  	github.com/novox/mesh-host/internal/system	1.051s
ok  	github.com/novox/mesh-host/internal/tunnel	1.048s
ok  	github.com/novox/mesh-host/internal/units	1.043s
ok  	github.com/novox/mesh-host/internal/upgrade	1.619s
ok  	github.com/novox/mesh-host/internal/witness	12.939s
ok  	github.com/novox/mesh-host/packaging	1.048s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.015s
**Merge check** at `5a7ec377` Judged: head `5a7ec3775b98` merged into trunk `53fd32618916`; read beside it: mesh-catalog `1a2c917abfdb`, mesh-controller `fcdecb436117`, mesh-controller-main `7543f64911c5`, mesh-tools `6b3e15042fee` - `mesh/merge-gate`: **FAIL** — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] feat/57-config-and-provisioning's controller does not build with this change's validator: docker run --label mesh.build=build-1792098822994191065 --volume /var/lib/build-agent/judge-cache/homes/build-1792098822994191065:/var/lib/build-agent/judge-cache/homes/build-1792098822994191065 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792098822994191065 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792098822994191065/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792098822994191065/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host) - `mesh/repo-check`: **PASS** — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - 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-host is judged on its first machine - read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go Run by the build seat on shanks as `build-1792098822994191065` (`builds --log build-1792098822994191065`). ``` --- judged for the release branch feat/57-config-and-provisioning by its controller at fcdecb436117, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at fcdecb436117, mesh-controller-main main at 7543f64911c5, mesh-tools main at 6b3e15042fee --- its merge-check.sh (go toolchain) go: downloading git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261015210729-d3e182503c19 ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.016s ok github.com/novox/mesh-host/cmd/mesh-host 8.228s ok github.com/novox/mesh-host/examples 1.029s ok github.com/novox/mesh-host/internal/accounts 2.135s ok github.com/novox/mesh-host/internal/apply 13.379s ok github.com/novox/mesh-host/internal/bootstrap 6.344s ok github.com/novox/mesh-host/internal/bundle 1.037s ok github.com/novox/mesh-host/internal/declaration 1.082s ok github.com/novox/mesh-host/internal/filling 1.758s ok github.com/novox/mesh-host/internal/firewall 1.841s ok github.com/novox/mesh-host/internal/identity 1.366s ok github.com/novox/mesh-host/internal/image 1.033s ok github.com/novox/mesh-host/internal/inventory 1.063s ok github.com/novox/mesh-host/internal/link 10.554s ok github.com/novox/mesh-host/internal/liveness 2.201s ok github.com/novox/mesh-host/internal/meshcli 1.571s ok github.com/novox/mesh-host/internal/network 1.073s ok github.com/novox/mesh-host/internal/outward 1.041s ok github.com/novox/mesh-host/internal/profile 1.638s ok github.com/novox/mesh-host/internal/reachable 1.039s ok github.com/novox/mesh-host/internal/store 1.851s ok github.com/novox/mesh-host/internal/system 1.051s ok github.com/novox/mesh-host/internal/tunnel 1.048s ok github.com/novox/mesh-host/internal/units 1.043s ok github.com/novox/mesh-host/internal/upgrade 1.619s ok github.com/novox/mesh-host/internal/witness 12.939s ok github.com/novox/mesh-host/packaging 1.048s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.015s ```
mesh-tools commented 2026-10-16 00:01:52 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 5a7ec377
Judged: head 5a7ec3775b98 merged into trunk 53fd32618916; read beside it: mesh-catalog 1a2c917abfdb, mesh-controller fcdecb436117, mesh-controller-main a47976be4e69, mesh-tools 6b3e15042fee
Siblings could not be learned: mesh-delivery did not say the group's pull requests (this controller is not on the bus): the check reads no siblings

  • mesh/merge-gate: FAIL — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] feat/57-config-and-provisioning's controller does not build with this change's validator: docker run --label mesh.build=build-1792108857803910413 --volume /var/lib/build-agent/judge-cache/homes/build-1792108857803910413:/var/lib/build-agent/judge-cache/homes/build-1792108857803910413 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792108857803910413 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792108857803910413/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792108857803910413/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host)
  • mesh/repo-check: PASS — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • 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-host is judged on its first machine
  • read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go

Run by the build seat on shanks as build-1792108857803910413 (builds --log build-1792108857803910413).

--- judged for the release branch feat/57-config-and-provisioning by its controller at fcdecb436117, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at fcdecb436117, mesh-controller-main main at a47976be4e69, mesh-tools main at 6b3e15042fee
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.018s
ok  	github.com/novox/mesh-host/cmd/mesh-host	6.244s
ok  	github.com/novox/mesh-host/examples	1.035s
ok  	github.com/novox/mesh-host/internal/accounts	1.528s
ok  	github.com/novox/mesh-host/internal/apply	6.019s
ok  	github.com/novox/mesh-host/internal/bootstrap	4.814s
ok  	github.com/novox/mesh-host/internal/bundle	1.015s
ok  	github.com/novox/mesh-host/internal/declaration	1.076s
ok  	github.com/novox/mesh-host/internal/filling	1.749s
ok  	github.com/novox/mesh-host/internal/firewall	1.868s
ok  	github.com/novox/mesh-host/internal/identity	1.107s
ok  	github.com/novox/mesh-host/internal/image	1.024s
ok  	github.com/novox/mesh-host/internal/inventory	1.050s
ok  	github.com/novox/mesh-host/internal/link	10.508s
ok  	github.com/novox/mesh-host/internal/liveness	2.125s
ok  	github.com/novox/mesh-host/internal/meshcli	1.562s
ok  	github.com/novox/mesh-host/internal/network	1.048s
ok  	github.com/novox/mesh-host/internal/outward	1.029s
ok  	github.com/novox/mesh-host/internal/profile	1.640s
ok  	github.com/novox/mesh-host/internal/reachable	1.029s
ok  	github.com/novox/mesh-host/internal/store	1.219s
ok  	github.com/novox/mesh-host/internal/system	1.031s
ok  	github.com/novox/mesh-host/internal/tunnel	1.037s
ok  	github.com/novox/mesh-host/internal/units	1.015s
ok  	github.com/novox/mesh-host/internal/upgrade	1.125s
ok  	github.com/novox/mesh-host/internal/witness	5.220s
ok  	github.com/novox/mesh-host/packaging	1.013s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.015s
**Merge check** at `5a7ec377` Judged: head `5a7ec3775b98` merged into trunk `53fd32618916`; read beside it: mesh-catalog `1a2c917abfdb`, mesh-controller `fcdecb436117`, mesh-controller-main `a47976be4e69`, mesh-tools `6b3e15042fee` Siblings could not be learned: mesh-delivery did not say the group's pull requests (this controller is not on the bus): the check reads no siblings - `mesh/merge-gate`: **FAIL** — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] feat/57-config-and-provisioning's controller does not build with this change's validator: docker run --label mesh.build=build-1792108857803910413 --volume /var/lib/build-agent/judge-cache/homes/build-1792108857803910413:/var/lib/build-agent/judge-cache/homes/build-1792108857803910413 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792108857803910413 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792108857803910413/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792108857803910413/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host) - `mesh/repo-check`: **PASS** — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - 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-host is judged on its first machine - read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go Run by the build seat on shanks as `build-1792108857803910413` (`builds --log build-1792108857803910413`). ``` --- judged for the release branch feat/57-config-and-provisioning by its controller at fcdecb436117, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at fcdecb436117, mesh-controller-main main at a47976be4e69, mesh-tools main at 6b3e15042fee --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.018s ok github.com/novox/mesh-host/cmd/mesh-host 6.244s ok github.com/novox/mesh-host/examples 1.035s ok github.com/novox/mesh-host/internal/accounts 1.528s ok github.com/novox/mesh-host/internal/apply 6.019s ok github.com/novox/mesh-host/internal/bootstrap 4.814s ok github.com/novox/mesh-host/internal/bundle 1.015s ok github.com/novox/mesh-host/internal/declaration 1.076s ok github.com/novox/mesh-host/internal/filling 1.749s ok github.com/novox/mesh-host/internal/firewall 1.868s ok github.com/novox/mesh-host/internal/identity 1.107s ok github.com/novox/mesh-host/internal/image 1.024s ok github.com/novox/mesh-host/internal/inventory 1.050s ok github.com/novox/mesh-host/internal/link 10.508s ok github.com/novox/mesh-host/internal/liveness 2.125s ok github.com/novox/mesh-host/internal/meshcli 1.562s ok github.com/novox/mesh-host/internal/network 1.048s ok github.com/novox/mesh-host/internal/outward 1.029s ok github.com/novox/mesh-host/internal/profile 1.640s ok github.com/novox/mesh-host/internal/reachable 1.029s ok github.com/novox/mesh-host/internal/store 1.219s ok github.com/novox/mesh-host/internal/system 1.031s ok github.com/novox/mesh-host/internal/tunnel 1.037s ok github.com/novox/mesh-host/internal/units 1.015s ok github.com/novox/mesh-host/internal/upgrade 1.125s ok github.com/novox/mesh-host/internal/witness 5.220s ok github.com/novox/mesh-host/packaging 1.013s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.015s ```
mesh-tools commented 2026-10-16 00:20:13 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 5a7ec377
Judged: head 5a7ec3775b98 merged into trunk 53fd32618916; read beside it: mesh-catalog 1a2c917abfdb, mesh-controller fcdecb436117, mesh-controller-main af60d2719c0c, mesh-tools 6b3e15042fee
Siblings could not be learned: mesh-delivery did not say the group's pull requests (this controller is not on the bus): the check reads no siblings

  • mesh/merge-gate: FAIL — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] feat/57-config-and-provisioning's controller does not build with this change's validator: docker run --label mesh.build=build-1792109965807695732 --volume /var/lib/build-agent/judge-cache/homes/build-1792109965807695732:/var/lib/build-agent/judge-cache/homes/build-1792109965807695732 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792109965807695732 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792109965807695732/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792109965807695732/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host)
  • mesh/repo-check: PASS — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • 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-host is judged on its first machine
  • read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go

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

--- judged for the release branch feat/57-config-and-provisioning by its controller at fcdecb436117, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at fcdecb436117, mesh-controller-main main at af60d2719c0c, mesh-tools main at 6b3e15042fee
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261015210729-d3e182503c19
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.012s
ok  	github.com/novox/mesh-host/cmd/mesh-host	6.049s
ok  	github.com/novox/mesh-host/examples	1.024s
ok  	github.com/novox/mesh-host/internal/accounts	1.438s
ok  	github.com/novox/mesh-host/internal/apply	5.246s
ok  	github.com/novox/mesh-host/internal/bootstrap	3.711s
ok  	github.com/novox/mesh-host/internal/bundle	1.023s
ok  	github.com/novox/mesh-host/internal/declaration	1.059s
ok  	github.com/novox/mesh-host/internal/filling	1.740s
ok  	github.com/novox/mesh-host/internal/firewall	1.674s
ok  	github.com/novox/mesh-host/internal/identity	1.103s
ok  	github.com/novox/mesh-host/internal/image	1.023s
ok  	github.com/novox/mesh-host/internal/inventory	1.045s
ok  	github.com/novox/mesh-host/internal/link	10.510s
ok  	github.com/novox/mesh-host/internal/liveness	2.129s
ok  	github.com/novox/mesh-host/internal/meshcli	1.554s
ok  	github.com/novox/mesh-host/internal/network	1.042s
ok  	github.com/novox/mesh-host/internal/outward	1.028s
ok  	github.com/novox/mesh-host/internal/profile	1.666s
ok  	github.com/novox/mesh-host/internal/reachable	1.068s
ok  	github.com/novox/mesh-host/internal/store	1.233s
ok  	github.com/novox/mesh-host/internal/system	1.064s
ok  	github.com/novox/mesh-host/internal/tunnel	1.066s
ok  	github.com/novox/mesh-host/internal/units	1.025s
ok  	github.com/novox/mesh-host/internal/upgrade	1.183s
ok  	github.com/novox/mesh-host/internal/witness	4.797s
ok  	github.com/novox/mesh-host/packaging	1.060s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.010s
**Merge check** at `5a7ec377` Judged: head `5a7ec3775b98` merged into trunk `53fd32618916`; read beside it: mesh-catalog `1a2c917abfdb`, mesh-controller `fcdecb436117`, mesh-controller-main `af60d2719c0c`, mesh-tools `6b3e15042fee` Siblings could not be learned: mesh-delivery did not say the group's pull requests (this controller is not on the bus): the check reads no siblings - `mesh/merge-gate`: **FAIL** — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] feat/57-config-and-provisioning's controller does not build with this change's validator: docker run --label mesh.build=build-1792109965807695732 --volume /var/lib/build-agent/judge-cache/homes/build-1792109965807695732:/var/lib/build-agent/judge-cache/homes/build-1792109965807695732 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792109965807695732 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792109965807695732/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792109965807695732/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host) - `mesh/repo-check`: **PASS** — [release feat/57-config-and-provisioning, judged by its controller fcdecb436117] its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - 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-host is judged on its first machine - read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go Run by the build seat on ace as `build-1792109965807695732` (`builds --log build-1792109965807695732`). ``` --- judged for the release branch feat/57-config-and-provisioning by its controller at fcdecb436117, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at fcdecb436117, mesh-controller-main main at af60d2719c0c, mesh-tools main at 6b3e15042fee --- its merge-check.sh (go toolchain) go: downloading git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261015210729-d3e182503c19 ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.012s ok github.com/novox/mesh-host/cmd/mesh-host 6.049s ok github.com/novox/mesh-host/examples 1.024s ok github.com/novox/mesh-host/internal/accounts 1.438s ok github.com/novox/mesh-host/internal/apply 5.246s ok github.com/novox/mesh-host/internal/bootstrap 3.711s ok github.com/novox/mesh-host/internal/bundle 1.023s ok github.com/novox/mesh-host/internal/declaration 1.059s ok github.com/novox/mesh-host/internal/filling 1.740s ok github.com/novox/mesh-host/internal/firewall 1.674s ok github.com/novox/mesh-host/internal/identity 1.103s ok github.com/novox/mesh-host/internal/image 1.023s ok github.com/novox/mesh-host/internal/inventory 1.045s ok github.com/novox/mesh-host/internal/link 10.510s ok github.com/novox/mesh-host/internal/liveness 2.129s ok github.com/novox/mesh-host/internal/meshcli 1.554s ok github.com/novox/mesh-host/internal/network 1.042s ok github.com/novox/mesh-host/internal/outward 1.028s ok github.com/novox/mesh-host/internal/profile 1.666s ok github.com/novox/mesh-host/internal/reachable 1.068s ok github.com/novox/mesh-host/internal/store 1.233s ok github.com/novox/mesh-host/internal/system 1.064s ok github.com/novox/mesh-host/internal/tunnel 1.066s ok github.com/novox/mesh-host/internal/units 1.025s ok github.com/novox/mesh-host/internal/upgrade 1.183s ok github.com/novox/mesh-host/internal/witness 4.797s ok github.com/novox/mesh-host/packaging 1.060s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.010s ```
mesh-tools commented 2026-10-16 00:38:07 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 5a7ec377
Judged: head 5a7ec3775b98 merged into trunk 53fd32618916; read beside it: mesh-catalog 1a2c917abfdb, mesh-controller 1c9eb9e813fa, mesh-controller-main a07dd78c3e90, mesh-tools 6b3e15042fee
Siblings read beside it: novox/mesh-controller#346 c711e62287ff merged onto fcdecb436117 (feat/57-config-and-provisioning); judged by sibling novox/mesh-controller#346 merge 1c9eb9e813fa

  • mesh/merge-gate: PASS — [release feat/57-config-and-provisioning, judged by its controller 1c9eb9e813fa] every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: PASS — [release feat/57-config-and-provisioning, judged by its controller 1c9eb9e813fa] its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • 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-host is judged on its first machine
  • read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go

Run by the build seat on shanks as build-1792110883737522361 (builds --log build-1792110883737522361).

--- judged for the release branch feat/57-config-and-provisioning by its controller at 1c9eb9e813fa, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at 1c9eb9e813fa, mesh-controller-main main at a07dd78c3e90, mesh-tools main at 6b3e15042fee
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T00:34:58Z 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-16T00:34:58Z

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-host

notes:
  - cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go and internal/units/units_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.016s
ok  	github.com/novox/mesh-host/cmd/mesh-host	7.351s
ok  	github.com/novox/mesh-host/examples	1.030s
ok  	github.com/novox/mesh-host/internal/accounts	1.957s
ok  	github.com/novox/mesh-host/internal/apply	23.255s
ok  	github.com/novox/mesh-host/internal/bootstrap	5.105s
ok  	github.com/novox/mesh-host/internal/bundle	1.024s
ok  	github.com/novox/mesh-host/internal/declaration	1.077s
ok  	github.com/novox/mesh-host/internal/filling	1.747s
ok  	github.com/novox/mesh-host/internal/firewall	1.809s
ok  	github.com/novox/mesh-host/internal/identity	1.112s
ok  	github.com/novox/mesh-host/internal/image	1.029s
ok  	github.com/novox/mesh-host/internal/inventory	1.054s
ok  	github.com/novox/mesh-host/internal/link	10.497s
ok  	github.com/novox/mesh-host/internal/liveness	2.136s
ok  	github.com/novox/mesh-host/internal/meshcli	1.560s
ok  	github.com/novox/mesh-host/internal/network	1.048s
ok  	github.com/novox/mesh-host/internal/outward	1.035s
ok  	github.com/novox/mesh-host/internal/profile	1.627s
ok  	github.com/novox/mesh-host/internal/reachable	1.034s
ok  	github.com/novox/mesh-host/internal/store	1.474s
ok  	github.com/novox/mesh-host/internal/system	1.037s
ok  	github.com/novox/mesh-host/internal/tunnel	1.039s
ok  	github.com/novox/mesh-host/internal/units	1.029s
ok  	github.com/novox/mesh-host/internal/upgrade	1.586s
ok  	github.com/novox/mesh-host/internal/witness	22.624s
ok  	github.com/novox/mesh-host/packaging	1.013s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.013s
**Merge check** at `5a7ec377` Judged: head `5a7ec3775b98` merged into trunk `53fd32618916`; read beside it: mesh-catalog `1a2c917abfdb`, mesh-controller `1c9eb9e813fa`, mesh-controller-main `a07dd78c3e90`, mesh-tools `6b3e15042fee` Siblings read beside it: novox/mesh-controller#346 `c711e62287ff` merged onto `fcdecb436117` (feat/57-config-and-provisioning); judged by sibling novox/mesh-controller#346 merge 1c9eb9e813fa - `mesh/merge-gate`: **PASS** — [release feat/57-config-and-provisioning, judged by its controller 1c9eb9e813fa] every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — [release feat/57-config-and-provisioning, judged by its controller 1c9eb9e813fa] its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - 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-host is judged on its first machine - read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go Run by the build seat on shanks as `build-1792110883737522361` (`builds --log build-1792110883737522361`). ``` --- judged for the release branch feat/57-config-and-provisioning by its controller at 1c9eb9e813fa, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at 1c9eb9e813fa, mesh-controller-main main at a07dd78c3e90, mesh-tools main at 6b3e15042fee --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T00:34:58Z 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-16T00:34:58Z 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-host notes: - cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go and internal/units/units_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.016s ok github.com/novox/mesh-host/cmd/mesh-host 7.351s ok github.com/novox/mesh-host/examples 1.030s ok github.com/novox/mesh-host/internal/accounts 1.957s ok github.com/novox/mesh-host/internal/apply 23.255s ok github.com/novox/mesh-host/internal/bootstrap 5.105s ok github.com/novox/mesh-host/internal/bundle 1.024s ok github.com/novox/mesh-host/internal/declaration 1.077s ok github.com/novox/mesh-host/internal/filling 1.747s ok github.com/novox/mesh-host/internal/firewall 1.809s ok github.com/novox/mesh-host/internal/identity 1.112s ok github.com/novox/mesh-host/internal/image 1.029s ok github.com/novox/mesh-host/internal/inventory 1.054s ok github.com/novox/mesh-host/internal/link 10.497s ok github.com/novox/mesh-host/internal/liveness 2.136s ok github.com/novox/mesh-host/internal/meshcli 1.560s ok github.com/novox/mesh-host/internal/network 1.048s ok github.com/novox/mesh-host/internal/outward 1.035s ok github.com/novox/mesh-host/internal/profile 1.627s ok github.com/novox/mesh-host/internal/reachable 1.034s ok github.com/novox/mesh-host/internal/store 1.474s ok github.com/novox/mesh-host/internal/system 1.037s ok github.com/novox/mesh-host/internal/tunnel 1.039s ok github.com/novox/mesh-host/internal/units 1.029s ok github.com/novox/mesh-host/internal/upgrade 1.586s ok github.com/novox/mesh-host/internal/witness 22.624s ok github.com/novox/mesh-host/packaging 1.013s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.013s ```
mesh-tools added the mesh/ready label 2026-10-16 00:38:47 +00:00
mesh-tools commented 2026-10-16 00:38:53 +00:00
Author
Member
Copy Link
Copy Source

ready at 5a7ec3775b

ready at 5a7ec3775b988e315a22959e640a9ace299a5cef
mesh-tools commented 2026-10-16 01:12:26 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 5a7ec377
Judged: head 5a7ec3775b98 merged into trunk 53fd32618916; read beside it: mesh-catalog 1a2c917abfdb, mesh-controller 084fed391351, mesh-controller-main d70bb1f38867, mesh-tools 6b3e15042fee
Siblings read beside it: novox/mesh-controller#346 c711e62287ff merged onto fcdecb436117 (feat/57-config-and-provisioning); judged by sibling novox/mesh-controller#346 merge 084fed391351

  • mesh/merge-gate: PASS — [release feat/57-config-and-provisioning, judged by the group's controller 084fed391351] every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: PASS — [release feat/57-config-and-provisioning, judged by the group's controller 084fed391351] its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • 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-host is judged on its first machine
  • read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go

Run by the build seat on novox as build-1792112888384808918 (builds --log build-1792112888384808918).

--- judged for the release branch feat/57-config-and-provisioning by the group's controller at 084fed391351, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at 084fed391351, mesh-controller-main main at d70bb1f38867, mesh-tools main at 6b3e15042fee
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T01:05:49Z 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-16T01:05:49Z

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-host

notes:
  - cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go and internal/units/units_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261015210729-d3e182503c19
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.017s
ok  	github.com/novox/mesh-host/cmd/mesh-host	9.296s
ok  	github.com/novox/mesh-host/examples	1.032s
ok  	github.com/novox/mesh-host/internal/accounts	2.224s
ok  	github.com/novox/mesh-host/internal/apply	35.059s
ok  	github.com/novox/mesh-host/internal/bootstrap	6.172s
ok  	github.com/novox/mesh-host/internal/bundle	1.028s
ok  	github.com/novox/mesh-host/internal/declaration	1.078s
ok  	github.com/novox/mesh-host/internal/filling	1.743s
ok  	github.com/novox/mesh-host/internal/firewall	1.847s
ok  	github.com/novox/mesh-host/internal/identity	1.626s
ok  	github.com/novox/mesh-host/internal/image	1.018s
ok  	github.com/novox/mesh-host/internal/inventory	1.055s
ok  	github.com/novox/mesh-host/internal/link	10.643s
ok  	github.com/novox/mesh-host/internal/liveness	2.971s
ok  	github.com/novox/mesh-host/internal/meshcli	1.570s
ok  	github.com/novox/mesh-host/internal/network	1.044s
ok  	github.com/novox/mesh-host/internal/outward	1.020s
ok  	github.com/novox/mesh-host/internal/profile	1.622s
ok  	github.com/novox/mesh-host/internal/reachable	1.016s
ok  	github.com/novox/mesh-host/internal/store	2.295s
ok  	github.com/novox/mesh-host/internal/system	1.036s
ok  	github.com/novox/mesh-host/internal/tunnel	1.020s
ok  	github.com/novox/mesh-host/internal/units	1.015s
ok  	github.com/novox/mesh-host/internal/upgrade	2.111s
ok  	github.com/novox/mesh-host/internal/witness	35.072s
ok  	github.com/novox/mesh-host/packaging	1.014s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.015s
**Merge check** at `5a7ec377` Judged: head `5a7ec3775b98` merged into trunk `53fd32618916`; read beside it: mesh-catalog `1a2c917abfdb`, mesh-controller `084fed391351`, mesh-controller-main `d70bb1f38867`, mesh-tools `6b3e15042fee` Siblings read beside it: novox/mesh-controller#346 `c711e62287ff` merged onto `fcdecb436117` (feat/57-config-and-provisioning); judged by sibling novox/mesh-controller#346 merge 084fed391351 - `mesh/merge-gate`: **PASS** — [release feat/57-config-and-provisioning, judged by the group's controller 084fed391351] every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — [release feat/57-config-and-provisioning, judged by the group's controller 084fed391351] its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - 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-host is judged on its first machine - read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go Run by the build seat on novox as `build-1792112888384808918` (`builds --log build-1792112888384808918`). ``` --- judged for the release branch feat/57-config-and-provisioning by the group's controller at 084fed391351, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at 084fed391351, mesh-controller-main main at d70bb1f38867, mesh-tools main at 6b3e15042fee --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T01:05:49Z 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-16T01:05:49Z 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-host notes: - cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go and internal/units/units_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) go: downloading git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261015210729-d3e182503c19 ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.017s ok github.com/novox/mesh-host/cmd/mesh-host 9.296s ok github.com/novox/mesh-host/examples 1.032s ok github.com/novox/mesh-host/internal/accounts 2.224s ok github.com/novox/mesh-host/internal/apply 35.059s ok github.com/novox/mesh-host/internal/bootstrap 6.172s ok github.com/novox/mesh-host/internal/bundle 1.028s ok github.com/novox/mesh-host/internal/declaration 1.078s ok github.com/novox/mesh-host/internal/filling 1.743s ok github.com/novox/mesh-host/internal/firewall 1.847s ok github.com/novox/mesh-host/internal/identity 1.626s ok github.com/novox/mesh-host/internal/image 1.018s ok github.com/novox/mesh-host/internal/inventory 1.055s ok github.com/novox/mesh-host/internal/link 10.643s ok github.com/novox/mesh-host/internal/liveness 2.971s ok github.com/novox/mesh-host/internal/meshcli 1.570s ok github.com/novox/mesh-host/internal/network 1.044s ok github.com/novox/mesh-host/internal/outward 1.020s ok github.com/novox/mesh-host/internal/profile 1.622s ok github.com/novox/mesh-host/internal/reachable 1.016s ok github.com/novox/mesh-host/internal/store 2.295s ok github.com/novox/mesh-host/internal/system 1.036s ok github.com/novox/mesh-host/internal/tunnel 1.020s ok github.com/novox/mesh-host/internal/units 1.015s ok github.com/novox/mesh-host/internal/upgrade 2.111s ok github.com/novox/mesh-host/internal/witness 35.072s ok github.com/novox/mesh-host/packaging 1.014s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.015s ```
mesh-tools commented 2026-10-16 01:25:07 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 5a7ec377
Judged: head 5a7ec3775b98 merged into trunk 53fd32618916; read beside it: mesh-catalog 1a2c917abfdb, mesh-controller 038955ddc093, mesh-controller-main d70bb1f38867, mesh-tools 6b3e15042fee
Siblings read beside it: novox/mesh-controller#346 c711e62287ff merged onto fcdecb436117 (feat/57-config-and-provisioning); judged by sibling novox/mesh-controller#346 merge 038955ddc093

  • mesh/merge-gate: PASS — [release feat/57-config-and-provisioning, judged by the group's controller 038955ddc093] every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: PASS — [release feat/57-config-and-provisioning, judged by the group's controller 038955ddc093] its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • 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-host is judged on its first machine
  • read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go

Run by the build seat on novox as build-1792113689091236202 (builds --log build-1792113689091236202).

--- judged for the release branch feat/57-config-and-provisioning by the group's controller at 038955ddc093, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at 038955ddc093, mesh-controller-main main at d70bb1f38867, mesh-tools main at 6b3e15042fee
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T01:14:49Z 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-16T01:14:49Z

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-host

notes:
  - cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go and internal/units/units_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.037s
ok  	github.com/novox/mesh-host/cmd/mesh-host	9.015s
ok  	github.com/novox/mesh-host/examples	1.056s
ok  	github.com/novox/mesh-host/internal/accounts	2.900s
ok  	github.com/novox/mesh-host/internal/apply	32.303s
ok  	github.com/novox/mesh-host/internal/bootstrap	6.244s
ok  	github.com/novox/mesh-host/internal/bundle	1.026s
ok  	github.com/novox/mesh-host/internal/declaration	1.071s
ok  	github.com/novox/mesh-host/internal/filling	1.734s
ok  	github.com/novox/mesh-host/internal/firewall	1.945s
ok  	github.com/novox/mesh-host/internal/identity	1.402s
ok  	github.com/novox/mesh-host/internal/image	1.021s
ok  	github.com/novox/mesh-host/internal/inventory	1.036s
ok  	github.com/novox/mesh-host/internal/link	10.578s
ok  	github.com/novox/mesh-host/internal/liveness	2.894s
ok  	github.com/novox/mesh-host/internal/meshcli	1.550s
ok  	github.com/novox/mesh-host/internal/network	1.067s
ok  	github.com/novox/mesh-host/internal/outward	1.020s
ok  	github.com/novox/mesh-host/internal/profile	1.645s
ok  	github.com/novox/mesh-host/internal/reachable	1.016s
ok  	github.com/novox/mesh-host/internal/store	2.159s
ok  	github.com/novox/mesh-host/internal/system	1.017s
ok  	github.com/novox/mesh-host/internal/tunnel	1.019s
ok  	github.com/novox/mesh-host/internal/units	1.013s
ok  	github.com/novox/mesh-host/internal/upgrade	1.951s
ok  	github.com/novox/mesh-host/internal/witness	32.471s
ok  	github.com/novox/mesh-host/packaging	1.013s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.014s
**Merge check** at `5a7ec377` Judged: head `5a7ec3775b98` merged into trunk `53fd32618916`; read beside it: mesh-catalog `1a2c917abfdb`, mesh-controller `038955ddc093`, mesh-controller-main `d70bb1f38867`, mesh-tools `6b3e15042fee` Siblings read beside it: novox/mesh-controller#346 `c711e62287ff` merged onto `fcdecb436117` (feat/57-config-and-provisioning); judged by sibling novox/mesh-controller#346 merge 038955ddc093 - `mesh/merge-gate`: **PASS** — [release feat/57-config-and-provisioning, judged by the group's controller 038955ddc093] every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — [release feat/57-config-and-provisioning, judged by the group's controller 038955ddc093] its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - 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-host is judged on its first machine - read by no module's build: cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go Run by the build seat on novox as `build-1792113689091236202` (`builds --log build-1792113689091236202`). ``` --- judged for the release branch feat/57-config-and-provisioning by the group's controller at 038955ddc093, with the change's own validator; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller feat/57-config-and-provisioning at 038955ddc093, mesh-controller-main main at d70bb1f38867, mesh-tools main at 6b3e15042fee --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T01:14:49Z 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-16T01:14:49Z 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-host notes: - cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_test.go, internal/apply/vault_sealed_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go and internal/units/units_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.037s ok github.com/novox/mesh-host/cmd/mesh-host 9.015s ok github.com/novox/mesh-host/examples 1.056s ok github.com/novox/mesh-host/internal/accounts 2.900s ok github.com/novox/mesh-host/internal/apply 32.303s ok github.com/novox/mesh-host/internal/bootstrap 6.244s ok github.com/novox/mesh-host/internal/bundle 1.026s ok github.com/novox/mesh-host/internal/declaration 1.071s ok github.com/novox/mesh-host/internal/filling 1.734s ok github.com/novox/mesh-host/internal/firewall 1.945s ok github.com/novox/mesh-host/internal/identity 1.402s ok github.com/novox/mesh-host/internal/image 1.021s ok github.com/novox/mesh-host/internal/inventory 1.036s ok github.com/novox/mesh-host/internal/link 10.578s ok github.com/novox/mesh-host/internal/liveness 2.894s ok github.com/novox/mesh-host/internal/meshcli 1.550s ok github.com/novox/mesh-host/internal/network 1.067s ok github.com/novox/mesh-host/internal/outward 1.020s ok github.com/novox/mesh-host/internal/profile 1.645s ok github.com/novox/mesh-host/internal/reachable 1.016s ok github.com/novox/mesh-host/internal/store 2.159s ok github.com/novox/mesh-host/internal/system 1.017s ok github.com/novox/mesh-host/internal/tunnel 1.019s ok github.com/novox/mesh-host/internal/units 1.013s ok github.com/novox/mesh-host/internal/upgrade 1.951s ok github.com/novox/mesh-host/internal/witness 32.471s ok github.com/novox/mesh-host/packaging 1.013s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.014s ```
mesh-tools merged commit b546d4316c into feat/57-config-and-provisioning 2026-10-16 01:32:25 +00:00
mesh-tools deleted branch 57-config-and-provisioning 2026-10-16 01:32:26 +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 mesh/ready
Milestone
No items
No Milestone
Assignees
Clear assignees
jschoubben mesh-tools miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-host#114