The third review's follow-ups to #64 (hq issue 339). Do not merge without review. Stacked on #64 (and so on #63): merge those first; until then this diff shows their commits too. The follow-up itself is the one commit ff2553f.
The running runtimes are asked first:docker info --format '{{.DockerRootDir}}' and podman info --format '{{.Store.GraphRoot}}', once per apply, with a 10 s timeout. A runtime that is not running or not installed answers nothing. The guard asks on a runner of its own (apply.AskRuntimes, set by the engine), never the apply's runner, so tests that read back what the apply ran are not disturbed.
The files are read beside the answers, in every form the review named:
ExecStart continuation lines (a trailing backslash);
single and double quotes;
$VAR and ${VAR} from Environment= and EnvironmentFile= (a leading - allowed), across the unit and its drop-ins as systemd merges them;
--config-file naming another daemon.json;
TOML literal strings (graphroot = '...') in storage.conf.
Fail first: the new test TestEveryFormOfADataRootIsRead, run against runtimeDataRoots() on #64's head ae1293e, read none of the five roots. On this head it reads all five, and the running runtime's answer beside them.
The hand-over keyed to its resource (the optional item) is already in #64.
merge-check.sh passes locally.
The third review's follow-ups to #64 (hq issue 339). Do not merge without review. **Stacked on #64** (and so on #63): merge those first; until then this diff shows their commits too. The follow-up itself is the one commit ff2553f.
- **The running runtimes are asked first:** `docker info --format '{{.DockerRootDir}}'` and `podman info --format '{{.Store.GraphRoot}}'`, once per apply, with a 10 s timeout. A runtime that is not running or not installed answers nothing. The guard asks on a runner of its own (`apply.AskRuntimes`, set by the engine), never the apply's runner, so tests that read back what the apply ran are not disturbed.
- **The files are read beside the answers, in every form the review named:**
- ExecStart continuation lines (a trailing backslash);
- single and double quotes;
- `$VAR` and `${VAR}` from `Environment=` and `EnvironmentFile=` (a leading `-` allowed), across the unit and its drop-ins as systemd merges them;
- `--config-file` naming another daemon.json;
- TOML literal strings (`graphroot = '...'`) in storage.conf.
- **Fail first:** the new test `TestEveryFormOfADataRootIsRead`, run against `runtimeDataRoots()` on #64's head ae1293e, read none of the five roots. On this head it reads all five, and the running runtime's answer beside them.
- The hand-over keyed to its resource (the optional item) is already in #64.
`merge-check.sh` passes locally.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
A directory the engine used as found kept its owner and mode in silence, so
a module that cannot write it would just fail (hq issue 339 review). Each
one is now a WARNING in every apply's log and its module's resource of kind
directory, stated unhealthy on every look with its owner and what was
declared, which the controller raises as the module's condition; `mesh-host
hand-over <dir>` at the machine hands it to the mesh, and the next apply
gives it the declared owner and mode. The guard also refuses the spool, /opt,
the container runtimes' data (its configured data-root too), and an account's
.ssh as an access, a mount, or a directory anywhere but its own home.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/delivery covered: a later merge that contains it was delivered: novox/mesh-host@7c046a8a1d84 (merged as d28ca959 into main, walk plan-17915049347305…
The review of #64 asked for containerd's tree, dockerd's --data-root from its
unit and drop-ins, and podman's graphroot to be refused like docker's own
(hq issue 339); and the controller now tells a directory a send found from
one found before it, which needs the time it was first found kept across
applies instead of the time of the last apply. A hand-over now names the
resource it was for, so it lapses if another declaration points at the path.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
The third review of #64 (hq issue 339): an ExecStart continued over lines, a
quoted path, a variable from Environment= or EnvironmentFile= across the unit
and its drop-ins, dockerd's --config-file and podman's TOML literal strings
each hid a data root from the guard. The running runtimes are now asked first
(docker info, podman info) on a runner of the guard's own, and the files are
read beside them in all those forms.
Deliverynovox/mesh-host@7c046a8a1d84 — delivered since 2026-10-09T00:18:45Z
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
Machines
mesh-host on ace: passed — healthy 3 times over 2m24s
mesh-host on the rest running it: sent
Transitions
2026-10-08 23:42 (new) → proposed (announced): novox/mesh-host#65's head announced
2026-10-08 23:44 proposed → checked (checked): the verdict names this commit
2026-10-08 23:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 00:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 00:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-09 00:18 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-host@7c046a8a1d84` — **delivered** since 2026-10-09T00:18:45Z
**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
**Machines**
- mesh-host on ace: passed — healthy 3 times over 2m24s
- mesh-host on the rest running it: sent
**Transitions**
- 2026-10-08 23:42 (new) → proposed (announced): novox/mesh-host#65's head announced
- 2026-10-08 23:44 proposed → checked (checked): the verdict names this commit
- 2026-10-08 23:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 00:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 00:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-09 00:18 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — 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
Run by the build seat on shanks as build-1791501760296553622 (builds --log build-1791501760296553622).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:13:48Z 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-08T23:13:48Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.015s
ok github.com/novox/mesh-host/cmd/mesh-host 5.385s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.018s
ok github.com/novox/mesh-host/internal/apply 4.606s
ok github.com/novox/mesh-host/internal/bootstrap 1.614s
ok github.com/novox/mesh-host/internal/bundle 1.029s
ok github.com/novox/mesh-host/internal/declaration 1.071s
ok github.com/novox/mesh-host/internal/firewall 1.859s
ok github.com/novox/mesh-host/internal/identity 1.129s
ok github.com/novox/mesh-host/internal/image 1.035s
ok github.com/novox/mesh-host/internal/inventory 1.039s
ok github.com/novox/mesh-host/internal/link 10.352s
ok github.com/novox/mesh-host/internal/liveness 2.082s
ok github.com/novox/mesh-host/internal/network 1.051s
ok github.com/novox/mesh-host/internal/outward 1.039s
ok github.com/novox/mesh-host/internal/profile 1.524s
ok github.com/novox/mesh-host/internal/reachable 1.039s
ok github.com/novox/mesh-host/internal/store 1.224s
ok github.com/novox/mesh-host/internal/system 1.039s
ok github.com/novox/mesh-host/internal/tunnel 1.045s
ok github.com/novox/mesh-host/internal/units 1.036s
ok github.com/novox/mesh-host/internal/upgrade 1.146s
ok github.com/novox/mesh-host/internal/witness 4.814s
ok github.com/novox/mesh-host/packaging 1.032s
ok github.com/novox/mesh-host/validate 1.033s
**Merge check** at `ff2553f4`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — 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
Run by the build seat on shanks as `build-1791501760296553622` (`builds --log build-1791501760296553622`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:13:48Z 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-08T23:13:48Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.015s
ok github.com/novox/mesh-host/cmd/mesh-host 5.385s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.018s
ok github.com/novox/mesh-host/internal/apply 4.606s
ok github.com/novox/mesh-host/internal/bootstrap 1.614s
ok github.com/novox/mesh-host/internal/bundle 1.029s
ok github.com/novox/mesh-host/internal/declaration 1.071s
ok github.com/novox/mesh-host/internal/firewall 1.859s
ok github.com/novox/mesh-host/internal/identity 1.129s
ok github.com/novox/mesh-host/internal/image 1.035s
ok github.com/novox/mesh-host/internal/inventory 1.039s
ok github.com/novox/mesh-host/internal/link 10.352s
ok github.com/novox/mesh-host/internal/liveness 2.082s
ok github.com/novox/mesh-host/internal/network 1.051s
ok github.com/novox/mesh-host/internal/outward 1.039s
ok github.com/novox/mesh-host/internal/profile 1.524s
ok github.com/novox/mesh-host/internal/reachable 1.039s
ok github.com/novox/mesh-host/internal/store 1.224s
ok github.com/novox/mesh-host/internal/system 1.039s
ok github.com/novox/mesh-host/internal/tunnel 1.045s
ok github.com/novox/mesh-host/internal/units 1.036s
ok github.com/novox/mesh-host/internal/upgrade 1.146s
ok github.com/novox/mesh-host/internal/witness 4.814s
ok github.com/novox/mesh-host/packaging 1.032s
ok github.com/novox/mesh-host/validate 1.033s
```
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
The fourth review (hq issue 339): `trusted` is the catalogue's word and the
controller takes it out, but a controller that passes it on, an older one or
one rolled back to, must not cost a node its whole declaration. A file now
accepts it and nothing reads it; any other resource still refuses it. And a
podman that hangs no longer eats docker's ten seconds.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — 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
Run by the build seat on g14 as build-1791502940349096700 (builds --log build-1791502940349096700).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:38:08Z 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-08T23:38:08Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.017s
ok github.com/novox/mesh-host/cmd/mesh-host 5.262s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.014s
ok github.com/novox/mesh-host/internal/apply 2.207s
ok github.com/novox/mesh-host/internal/bootstrap 1.335s
ok github.com/novox/mesh-host/internal/bundle 1.016s
ok github.com/novox/mesh-host/internal/declaration 1.052s
ok github.com/novox/mesh-host/internal/firewall 1.675s
ok github.com/novox/mesh-host/internal/identity 1.047s
ok github.com/novox/mesh-host/internal/image 1.021s
ok github.com/novox/mesh-host/internal/inventory 1.026s
ok github.com/novox/mesh-host/internal/link 10.362s
ok github.com/novox/mesh-host/internal/liveness 2.043s
ok github.com/novox/mesh-host/internal/network 1.036s
ok github.com/novox/mesh-host/internal/outward 1.025s
ok github.com/novox/mesh-host/internal/profile 1.540s
ok github.com/novox/mesh-host/internal/reachable 1.019s
ok github.com/novox/mesh-host/internal/store 1.086s
ok github.com/novox/mesh-host/internal/system 1.026s
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.039s
ok github.com/novox/mesh-host/internal/witness 1.560s
ok github.com/novox/mesh-host/packaging 1.010s
ok github.com/novox/mesh-host/validate 1.010s
**Merge check** at `7c046a8a`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — 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
Run by the build seat on g14 as `build-1791502940349096700` (`builds --log build-1791502940349096700`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:38:08Z 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-08T23:38:08Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.017s
ok github.com/novox/mesh-host/cmd/mesh-host 5.262s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.014s
ok github.com/novox/mesh-host/internal/apply 2.207s
ok github.com/novox/mesh-host/internal/bootstrap 1.335s
ok github.com/novox/mesh-host/internal/bundle 1.016s
ok github.com/novox/mesh-host/internal/declaration 1.052s
ok github.com/novox/mesh-host/internal/firewall 1.675s
ok github.com/novox/mesh-host/internal/identity 1.047s
ok github.com/novox/mesh-host/internal/image 1.021s
ok github.com/novox/mesh-host/internal/inventory 1.026s
ok github.com/novox/mesh-host/internal/link 10.362s
ok github.com/novox/mesh-host/internal/liveness 2.043s
ok github.com/novox/mesh-host/internal/network 1.036s
ok github.com/novox/mesh-host/internal/outward 1.025s
ok github.com/novox/mesh-host/internal/profile 1.540s
ok github.com/novox/mesh-host/internal/reachable 1.019s
ok github.com/novox/mesh-host/internal/store 1.086s
ok github.com/novox/mesh-host/internal/system 1.026s
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.039s
ok github.com/novox/mesh-host/internal/witness 1.560s
ok github.com/novox/mesh-host/packaging 1.010s
ok github.com/novox/mesh-host/validate 1.010s
```
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.
The third review's follow-ups to #64 (hq issue 339). Do not merge without review. Stacked on #64 (and so on #63): merge those first; until then this diff shows their commits too. The follow-up itself is the one commit
ff2553f.docker info --format '{{.DockerRootDir}}'andpodman info --format '{{.Store.GraphRoot}}', once per apply, with a 10 s timeout. A runtime that is not running or not installed answers nothing. The guard asks on a runner of its own (apply.AskRuntimes, set by the engine), never the apply's runner, so tests that read back what the apply ran are not disturbed.$VARand${VAR}fromEnvironment=andEnvironmentFile=(a leading-allowed), across the unit and its drop-ins as systemd merges them;--config-filenaming another daemon.json;graphroot = '...') in storage.conf.TestEveryFormOfADataRootIsRead, run againstruntimeDataRoots()on #64's headae1293e, read none of the five roots. On this head it reads all five, and the running runtime's answer beside them.merge-check.shpasses locally.Delivery
novox/mesh-host@7c046a8a1d84— delivered since 2026-10-09T00:18:45ZDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
ff2553f4mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791501760296553622(builds --log build-1791501760296553622).trusted, and give each runtime its own time to answerMerge check at
7c046a8amesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791502940349096700(builds --log build-1791502940349096700).