Do not merge before mesh-controller #170 is live on the controller. Its checks are expected to fail until then, because the controller the mesh runs today does not know trusted. To be fully safe against a controller rollback, also wait until mesh-host #65 is on every node: it makes a file accept and ignore trusted.
With #170, a file that asks for a ${setting:} counts as trusted unless it says "trusted": false (fail closed, hq issue 339). Its settings can then be changed at the controller's terminal only, never through the settings verb.
module check against #170's controller lists 9 such files here. Only two are opted out, because nothing but their own person reads them:
dunstconfiguration: the notifier's width and font size, in the person's own dunstrc;
xdguser-dirs: the person's own folder names.
The other 7 stay unmarked, so they count as trusted: hostname name, lab runtime-env (the forge it fetches from), mailu config-env (domain, proxy address), mounts config, nfs-server config (shares and grants), power logind drop-in, and zsh tools-conf (execute).
The media catalogue gets no change. All 13 of its files are trusted: the identity.env files set the uid and gid a container runs as, nzbget's server-env sets a login, and qbittorrent's init script runs as root.
Do not merge before **mesh-controller #170 is live** on the controller. Its checks are expected to fail until then, because the controller the mesh runs today does not know `trusted`. To be fully safe against a controller rollback, also wait until mesh-host #65 is on every node: it makes a file accept and ignore `trusted`.
With #170, a file that asks for a `${setting:}` counts as **trusted** unless it says `"trusted": false` (fail closed, hq issue 339). Its settings can then be changed at the controller's terminal only, never through the `settings` verb.
`module check` against #170's controller lists 9 such files here. Only two are opted out, because nothing but their own person reads them:
- `dunst` `configuration`: the notifier's width and font size, in the person's own dunstrc;
- `xdg` `user-dirs`: the person's own folder names.
The other 7 stay unmarked, so they count as trusted: `hostname` name, `lab` runtime-env (the forge it fetches from), `mailu` config-env (domain, proxy address), `mounts` config, `nfs-server` config (shares and grants), `power` logind drop-in, and `zsh` tools-conf (`execute`).
The media catalogue gets no change. All 13 of its files are trusted: the `identity.env` files set the uid and gid a container runs as, nzbget's `server-env` sets a login, and qbittorrent's init script runs as root.
With mesh-controller #170 a file that asks for a setting counts as trusted
unless it says otherwise, and its settings are set at the controller's
terminal alone (hq issue 339). These two are a person's own notifier look and
folder names in their home, which nothing else trusts.
Deliverynovox/mesh-catalog@bdd2d65404b9 — delivered since 2026-10-09T00:36:42Z
Delivery plan — builds dunst, xdg → g14, shanks; no bus step
tier 0: dunst, xdg
g14: receives dunst, xdg
shanks: receives dunst, xdg
Machines
dunst on g14: passed — healthy 3 times over 2m35s
xdg on g14: passed — judged with dunst: healthy 3 times over 2m35s
dunst on the rest running it: sent
xdg on the rest running it: sent
Transitions
2026-10-08 23:42 (new) → proposed (announced): novox/mesh-catalog#148's head announced
2026-10-08 23:44 proposed → checked (checked): the verdict names this commit
2026-10-08 23:44 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-09 00:25 rejected → proposed (recheck): failed only because the controller and engine did not know trusted; mesh-controller #170 and mesh-host #65 are now live everywhere
2026-10-09 00:28 proposed → checked (checked): the verdict names this commit
2026-10-09 00:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 00:33 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:33 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:36 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@bdd2d65404b9` — **delivered** since 2026-10-09T00:36:42Z
**Delivery plan** — builds dunst, xdg → g14, shanks; no bus step
- tier 0: dunst, xdg
- g14: receives dunst, xdg
- shanks: receives dunst, xdg
**Machines**
- dunst on g14: passed — healthy 3 times over 2m35s
- xdg on g14: passed — judged with dunst: healthy 3 times over 2m35s
- dunst on the rest running it: sent
- xdg on the rest running it: sent
**Transitions**
- 2026-10-08 23:42 (new) → proposed (announced): novox/mesh-catalog#148's head announced
- 2026-10-08 23:44 proposed → checked (checked): the verdict names this commit
- 2026-10-08 23:44 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
- 2026-10-09 00:25 rejected → proposed (recheck): failed only because the controller and engine did not know `trusted`; mesh-controller #170 and mesh-host #65 are now live everywhere
- 2026-10-09 00:28 proposed → checked (checked): the verdict names this commit
- 2026-10-09 00:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 00:33 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:33 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:36 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: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored (modules: dunst, xdg)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds dunst, xdg → g14, shanks; no bus step
tier 0: dunst, xdg
g14: receives dunst, xdg
shanks: receives dunst, xdg
Run by the build seat on shanks as build-1791502970760748059 (builds --log build-1791502970760748059).
--- the gate: dunst, xdg
dunst: ok, 6 tool(s)
xdg: ok, 5 tool(s)
long-running resources without health: 0
2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-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: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored
judged by controller development build against the facts of 2026-10-08T23:38:08Z
fails:
- a machine (f35): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored
- a machine (yvbpsm): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored
modules the change moves:
- dunst (changed)
- xdg (changed)
machines:
- a machine (f35): does not compose
- 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): does not compose
a merge would rebuild 2 module(s) in 1 tier(s): dunst, xdg
mesh-controller: the change fails the merge gate
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 33671 strings of 600 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/dunst
ok dunst/cmd/dunst-tools 3.056s
testing modules/xdg
ok xdg/cmd/xdg-tools 1.058s
**Merge check** at `bdd2d654`
- `mesh/merge-gate`: **FAIL** — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored (modules: dunst, xdg)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds dunst, xdg → g14, shanks; no bus step
- tier 0: dunst, xdg
- g14: receives dunst, xdg
- shanks: receives dunst, xdg
Run by the build seat on shanks as `build-1791502970760748059` (`builds --log build-1791502970760748059`).
```
--- the gate: dunst, xdg
dunst: ok, 6 tool(s)
xdg: ok, 5 tool(s)
long-running resources without health: 0
2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-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: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored
judged by controller development build against the facts of 2026-10-08T23:38:08Z
fails:
- a machine (f35): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored
- a machine (yvbpsm): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored
modules the change moves:
- dunst (changed)
- xdg (changed)
machines:
- a machine (f35): does not compose
- 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): does not compose
a merge would rebuild 2 module(s) in 1 tier(s): dunst, xdg
mesh-controller: the change fails the merge gate
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 33671 strings of 600 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/dunst
ok dunst/cmd/dunst-tools 3.056s
testing modules/xdg
ok xdg/cmd/xdg-tools 1.058s
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst, xdg)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds dunst, xdg → g14, shanks; no bus step
tier 0: dunst, xdg
g14: receives dunst, xdg
shanks: receives dunst, xdg
Run by the build seat on novox as build-1791505552890723099 (builds --log build-1791505552890723099).
--- the gate: dunst, xdg
dunst: ok, 6 tool(s)
xdg: ok, 5 tool(s)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:16:57Z 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-09T00:16:57Z
modules the change moves:
- dunst (changed)
- xdg (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 2 module(s) in 1 tier(s): dunst, xdg
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 33671 strings of 600 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.008s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/dunst
ok dunst/cmd/dunst-tools 3.117s
testing modules/xdg
ok xdg/cmd/xdg-tools 1.074s
**Merge check** at `bdd2d654`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst, xdg)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds dunst, xdg → g14, shanks; no bus step
- tier 0: dunst, xdg
- g14: receives dunst, xdg
- shanks: receives dunst, xdg
Run by the build seat on novox as `build-1791505552890723099` (`builds --log build-1791505552890723099`).
```
--- the gate: dunst, xdg
dunst: ok, 6 tool(s)
xdg: ok, 5 tool(s)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:16:57Z 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-09T00:16:57Z
modules the change moves:
- dunst (changed)
- xdg (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 2 module(s) in 1 tier(s): dunst, xdg
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 33671 strings of 600 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.008s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/dunst
ok dunst/cmd/dunst-tools 3.117s
testing modules/xdg
ok xdg/cmd/xdg-tools 1.074s
```
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.
Do not merge before mesh-controller #170 is live on the controller. Its checks are expected to fail until then, because the controller the mesh runs today does not know
trusted. To be fully safe against a controller rollback, also wait until mesh-host #65 is on every node: it makes a file accept and ignoretrusted.With #170, a file that asks for a
${setting:}counts as trusted unless it says"trusted": false(fail closed, hq issue 339). Its settings can then be changed at the controller's terminal only, never through thesettingsverb.module checkagainst #170's controller lists 9 such files here. Only two are opted out, because nothing but their own person reads them:dunstconfiguration: the notifier's width and font size, in the person's own dunstrc;xdguser-dirs: the person's own folder names.The other 7 stay unmarked, so they count as trusted:
hostnamename,labruntime-env (the forge it fetches from),mailuconfig-env (domain, proxy address),mountsconfig,nfs-serverconfig (shares and grants),powerlogind drop-in, andzshtools-conf (execute).The media catalogue gets no change. All 13 of its files are trusted: the
identity.envfiles set the uid and gid a container runs as, nzbget'sserver-envsets a login, and qbittorrent's init script runs as root.Delivery
novox/mesh-catalog@bdd2d65404b9— delivered since 2026-10-09T00:36:42ZDelivery plan — builds dunst, xdg → g14, shanks; no bus step
Machines
Transitions
trusted; mesh-controller #170 and mesh-host #65 are now live everywhereThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
bdd2d654mesh/merge-gate: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "dunst.configuration": a file does not use "trusted", and it is set. Refused rather than ignored (modules: dunst, xdg)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds dunst, xdg → g14, shanks; no bus step
Run by the build seat on shanks as
build-1791502970760748059(builds --log build-1791502970760748059).Merge check at
bdd2d654mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst, xdg)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds dunst, xdg → g14, shanks; no bus step
Run by the build seat on novox as
build-1791505552890723099(builds --log build-1791505552890723099).