A follow-up to #163 from the review of the shares work (hq ADR 0263).
The node-nfs-server verbs exports and test still said a share is exported to "the private network's range". Since the review, the server exports each share only to the private addresses of the nodes it grants the share to and that ask for it (ADR 0263 rule 5). The descriptions now say so, and test's address argument is described as a node's private address.
A test, TestTheExportVerbsDescribePerNodeAddresses, failed before the change and passes after. Only descriptions change: no verb, argument name or schema shape.
Not to be merged before review.
A follow-up to #163 from the review of the shares work (hq ADR 0263).
The `node-nfs-server` verbs `exports` and `test` still said a share is exported to "the private network's range". Since the review, the server exports each share only to the private addresses of the nodes it grants the share to and that ask for it (ADR 0263 rule 5). The descriptions now say so, and `test`'s `address` argument is described as a node's private address.
A test, `TestTheExportVerbsDescribePerNodeAddresses`, failed before the change and passes after. Only descriptions change: no verb, argument name or schema shape.
Not to be merged before review.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-controller on novox: passed — healthy 3 times over 3m39s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m39s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 3m46s
route-proxy on the rest running it: sent
Transitions
2026-10-08 19:14 (new) → proposed (announced): novox/mesh-controller#166's head announced
2026-10-08 19:18 proposed → checked (checked): the verdict names this commit
2026-10-08 19:18 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 21:05 ready → proposed (recheck): checked at 19:18Z before #161, #165 and #167 merged; check it against today's main before merging
2026-10-08 21:11 proposed → checked (checked): the verdict names this commit
2026-10-08 21:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 21:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 21:13 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-08 21:28 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@5d7d8ee2d64c` — **delivered** since 2026-10-08T21:28:18Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
**Group** `fix/shares-review-followups`, in order: novox/hq@4dd52cace6fb → novox/mesh-controller@5d7d8ee2d64c → novox/mesh-catalog@68b158d5238f → novox/mesh-host@fedd9dcf350e
- novox/mesh-controller@5d7d8ee2d64c before novox/mesh-catalog@68b158d5238f: built by
- novox/mesh-controller@5d7d8ee2d64c before novox/mesh-host@fedd9dcf350e: built by, over engine before controller
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m39s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m39s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 3m46s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-08 19:14 (new) → proposed (announced): novox/mesh-controller#166's head announced
- 2026-10-08 19:18 proposed → checked (checked): the verdict names this commit
- 2026-10-08 19:18 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 21:05 ready → proposed (recheck): checked at 19:18Z before #161, #165 and #167 merged; check it against today's main before merging
- 2026-10-08 21:11 proposed → checked (checked): the verdict names this commit
- 2026-10-08 21:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 21:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-08 21:13 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-08 21:28 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as build-1791486858662398729 (builds --log build-1791486858662398729).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-08T19:09:42Z 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-08T19:09:42Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.033s
ok github.com/novox/mesh-controller/cmd/mesh-controller 163.943s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.019s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/route-proxy 1.116s
ok github.com/novox/mesh-controller/internal/artifacts 1.040s
ok github.com/novox/mesh-controller/internal/broker 2.513s
ok github.com/novox/mesh-controller/internal/builder 1.830s
ok github.com/novox/mesh-controller/internal/catalogue 4.183s
ok github.com/novox/mesh-controller/internal/conditions 2.181s
ok github.com/novox/mesh-controller/internal/envfile 1.053s
ok github.com/novox/mesh-controller/internal/facts 1.086s
ok github.com/novox/mesh-controller/internal/identity 4.141s
ok github.com/novox/mesh-controller/internal/inventory 73.371s
ok github.com/novox/mesh-controller/internal/lease 17.723s
ok github.com/novox/mesh-controller/internal/licences 3.790s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.083s
ok github.com/novox/mesh-controller/internal/link 50.756s
ok github.com/novox/mesh-controller/internal/lint 1.969s
ok github.com/novox/mesh-controller/internal/outward 1.076s
ok github.com/novox/mesh-controller/internal/overlay 1.064s
ok github.com/novox/mesh-controller/internal/secrets 1.436s
ok github.com/novox/mesh-controller/internal/store 3.288s
ok github.com/novox/mesh-controller/internal/testbus 1.258s
ok github.com/novox/mesh-controller/internal/token 1.016s
**Merge check** at `5d7d8ee2`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as `build-1791486858662398729` (`builds --log build-1791486858662398729`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-08T19:09:42Z 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-08T19:09:42Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.033s
ok github.com/novox/mesh-controller/cmd/mesh-controller 163.943s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.019s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/route-proxy 1.116s
ok github.com/novox/mesh-controller/internal/artifacts 1.040s
ok github.com/novox/mesh-controller/internal/broker 2.513s
ok github.com/novox/mesh-controller/internal/builder 1.830s
ok github.com/novox/mesh-controller/internal/catalogue 4.183s
ok github.com/novox/mesh-controller/internal/conditions 2.181s
ok github.com/novox/mesh-controller/internal/envfile 1.053s
ok github.com/novox/mesh-controller/internal/facts 1.086s
ok github.com/novox/mesh-controller/internal/identity 4.141s
ok github.com/novox/mesh-controller/internal/inventory 73.371s
ok github.com/novox/mesh-controller/internal/lease 17.723s
ok github.com/novox/mesh-controller/internal/licences 3.790s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.083s
ok github.com/novox/mesh-controller/internal/link 50.756s
ok github.com/novox/mesh-controller/internal/lint 1.969s
ok github.com/novox/mesh-controller/internal/outward 1.076s
ok github.com/novox/mesh-controller/internal/overlay 1.064s
ok github.com/novox/mesh-controller/internal/secrets 1.436s
ok github.com/novox/mesh-controller/internal/store 3.288s
ok github.com/novox/mesh-controller/internal/testbus 1.258s
ok github.com/novox/mesh-controller/internal/token 1.016s
```
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as build-1791493557789543772 (builds --log build-1791493557789543772).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-08T21:02:21Z 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-08T21:02:21Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.041s
ok github.com/novox/mesh-controller/cmd/mesh-controller 207.028s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.029s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/route-proxy 1.128s
ok github.com/novox/mesh-controller/internal/artifacts 1.056s
ok github.com/novox/mesh-controller/internal/broker 6.590s
ok github.com/novox/mesh-controller/internal/builder 4.277s
ok github.com/novox/mesh-controller/internal/catalogue 5.368s
ok github.com/novox/mesh-controller/internal/conditions 2.290s
ok github.com/novox/mesh-controller/internal/envfile 1.031s
ok github.com/novox/mesh-controller/internal/facts 1.033s
ok github.com/novox/mesh-controller/internal/identity 12.437s
ok github.com/novox/mesh-controller/internal/inventory 95.128s
ok github.com/novox/mesh-controller/internal/lease 17.705s
ok github.com/novox/mesh-controller/internal/licences 12.048s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.015s
ok github.com/novox/mesh-controller/internal/link 56.633s
ok github.com/novox/mesh-controller/internal/lint 2.396s
ok github.com/novox/mesh-controller/internal/outward 1.037s
ok github.com/novox/mesh-controller/internal/overlay 1.019s
ok github.com/novox/mesh-controller/internal/secrets 1.435s
ok github.com/novox/mesh-controller/internal/store 6.337s
ok github.com/novox/mesh-controller/internal/testbus 1.178s
ok github.com/novox/mesh-controller/internal/token 1.024s
**Merge check** at `5d7d8ee2`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as `build-1791493557789543772` (`builds --log build-1791493557789543772`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-08T21:02:21Z 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-08T21:02:21Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.041s
ok github.com/novox/mesh-controller/cmd/mesh-controller 207.028s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.029s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/route-proxy 1.128s
ok github.com/novox/mesh-controller/internal/artifacts 1.056s
ok github.com/novox/mesh-controller/internal/broker 6.590s
ok github.com/novox/mesh-controller/internal/builder 4.277s
ok github.com/novox/mesh-controller/internal/catalogue 5.368s
ok github.com/novox/mesh-controller/internal/conditions 2.290s
ok github.com/novox/mesh-controller/internal/envfile 1.031s
ok github.com/novox/mesh-controller/internal/facts 1.033s
ok github.com/novox/mesh-controller/internal/identity 12.437s
ok github.com/novox/mesh-controller/internal/inventory 95.128s
ok github.com/novox/mesh-controller/internal/lease 17.705s
ok github.com/novox/mesh-controller/internal/licences 12.048s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.015s
ok github.com/novox/mesh-controller/internal/link 56.633s
ok github.com/novox/mesh-controller/internal/lint 2.396s
ok github.com/novox/mesh-controller/internal/outward 1.037s
ok github.com/novox/mesh-controller/internal/overlay 1.019s
ok github.com/novox/mesh-controller/internal/secrets 1.435s
ok github.com/novox/mesh-controller/internal/store 6.337s
ok github.com/novox/mesh-controller/internal/testbus 1.178s
ok github.com/novox/mesh-controller/internal/token 1.024s
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A follow-up to #163 from the review of the shares work (hq ADR 0263).
The
node-nfs-serververbsexportsandteststill said a share is exported to "the private network's range". Since the review, the server exports each share only to the private addresses of the nodes it grants the share to and that ask for it (ADR 0263 rule 5). The descriptions now say so, andtest'saddressargument is described as a node's private address.A test,
TestTheExportVerbsDescribePerNodeAddresses, failed before the change and passes after. Only descriptions change: no verb, argument name or schema shape.Not to be merged before review.
Delivery
novox/mesh-controller@5d7d8ee2d64c— delivered since 2026-10-08T21:28:18ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Group
fix/shares-review-followups, in order: novox/hq@4dd52cace6 → novox/mesh-controller@5d7d8ee2d6 → novox/mesh-catalog@68b158d523 → novox/mesh-host@fedd9dcf35Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
5d7d8ee2mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791486858662398729(builds --log build-1791486858662398729).Merge check at
5d7d8ee2mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791493557789543772(builds --log build-1791493557789543772).