Fixes novox/hq issue 360 (the operator cannot choose a notification's action on a touchpad), hq PR #260.
Acceptance: on the laptop and the workstation, a tap on a notification with one action runs it; with several, rofi opens to choose one; a notification without actions closes on a tap.
Changes (module dunst only):
dunstrc: mouse_left_click = do_action, close_current (was close_current). Middle and right click unchanged. Semantics from dunst(5) and dunst 1.13.2's notification_do_action/input.c/menu.c: one action runs; several open the menu for that notification and the close waits for the menu (an Escape leaves it shown); none closes. Edge: a notification without actions but with one link opens the link.
dunstrc: dmenu = rofi -dmenu -p dunst (was dmenu -p dunst; the node-launcher's dmenu lives in ~/.local/bin, which the running dunst's PATH does not hold, so the menu never opened).
Package rofi declared (the file names it; the rofi module declares it too, as git/nfs-utils are shared today).
Contribution to node-display-session (i3): bindsym $mod+n exec --no-startup-id dunstctl context. $mod+n is bound nowhere else in the catalogue.
send refuses the token default, which dunst would run at a tap without the menu.
Tests: a tap chooses; the menu key is a binding only and is its source file; packages; the menu line. README updated.
Nothing else in the dunstrc changes; the font-size and width settings are untouched. Local: go vet, go test -race and the controller's module check (dunst: ok) pass.
Fixes novox/hq issue 360 (the operator cannot choose a notification's action on a touchpad), hq PR #260.
**Acceptance:** on the laptop and the workstation, a tap on a notification with one action runs it; with several, rofi opens to choose one; a notification without actions closes on a tap.
**Changes (module dunst only):**
- dunstrc: `mouse_left_click = do_action, close_current` (was `close_current`). Middle and right click unchanged. Semantics from dunst(5) and dunst 1.13.2's `notification_do_action`/`input.c`/`menu.c`: one action runs; several open the menu for that notification and the close waits for the menu (an Escape leaves it shown); none closes. Edge: a notification without actions but with one link opens the link.
- dunstrc: `dmenu = rofi -dmenu -p dunst` (was `dmenu -p dunst`; the node-launcher's `dmenu` lives in `~/.local/bin`, which the running dunst's PATH does not hold, so the menu never opened).
- Package `rofi` declared (the file names it; the rofi module declares it too, as `git`/`nfs-utils` are shared today).
- Contribution to `node-display-session` (i3): `bindsym $mod+n exec --no-startup-id dunstctl context`. `$mod+n` is bound nowhere else in the catalogue.
- `send` refuses the token `default`, which dunst would run at a tap without the menu.
- Tests: a tap chooses; the menu key is a binding only and is its source file; packages; the menu line. README updated.
Nothing else in the dunstrc changes; the font-size and width settings are untouched. Local: `go vet`, `go test -race` and the controller's `module check` (dunst: ok) pass.
mesh/merge-gate fail: builds dunst → g14, shanks; no bus step; 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with…
The actions sat on the middle click, which the operator's touchpads cannot give, and the context
menu named dmenu, which dunst's PATH does not hold. The left click is now do_action, close_current
(one action runs, several open the menu, none closes), the menu is rofi, declared as a package,
Super+N opens it from the keyboard through i3's contribution, and send refuses the token default,
which dunst would run at a tap without the menu.
Deliverynovox/mesh-catalog@f055898089e8 — superseded since 2026-10-09T22:21:15Z
Covered: delivered after its walk was superseded: the walk plan-1791584475080493383, which took its walk plan-1791584474746812089 over, ended done
Delivery plan — builds dunst → g14, shanks; no bus step
tier 0: dunst
g14: receives dunst
shanks: receives dunst
Machines
claude-code on ace: passed — healthy 3 times over 2m27s
dunst on g14: passed — healthy 3 times over 2m54s
claude-code on the rest running it: sent
dunst on the rest running it: sent
build-agent on ace: passed — carried by plan-1791588520135642438
route-proxy on ace: passed — carried by plan-1791588520135642438
build-agent on novox: passed — carried by plan-1791590819200835583
Transitions
2026-10-09 22:12 (new) → proposed (announced): novox/mesh-catalog#167's head announced
2026-10-09 22:13 proposed → checked (checked): the verdict names this commit
2026-10-09 22:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 22:21 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 22:21 published → superseded (superseded): a newer delivery to the same trunk took over its walk
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@f055898089e8` — **superseded** since 2026-10-09T22:21:15Z
**Covered**: delivered after its walk was superseded: the walk plan-1791584475080493383, which took its walk plan-1791584474746812089 over, ended done
**Delivery plan** — builds dunst → g14, shanks; no bus step
- tier 0: dunst
- g14: receives dunst
- shanks: receives dunst
**Machines**
- claude-code on ace: passed — healthy 3 times over 2m27s
- dunst on g14: passed — healthy 3 times over 2m54s
- claude-code on the rest running it: sent
- dunst on the rest running it: sent
- build-agent on ace: passed — carried by plan-1791588520135642438
- route-proxy on ace: passed — carried by plan-1791588520135642438
- build-agent on novox: passed — carried by plan-1791590819200835583
**Transitions**
- 2026-10-09 22:12 (new) → proposed (announced): novox/mesh-catalog#167's head announced
- 2026-10-09 22:13 proposed → checked (checked): the verdict names this commit
- 2026-10-09 22:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 22:21 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 22:21 published → superseded (superseded): a newer delivery to the same trunk took over its walk
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 — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - f35 needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it (modules: dunst)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds dunst → g14, shanks; no bus step
tier 0: dunst
g14: receives dunst
shanks: receives dunst
Run by the build seat on shanks as build-1791583659664939762 (builds --log build-1791583659664939762).
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
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
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
merge gate: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - f35 needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it
judged by controller development build against the facts of 2026-10-09T22:05:01Z
fails:
- a machine (f35): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - f35 needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it
- a machine (yvbpsm): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - yvbpsm needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - yvbpsm needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - yvbpsm needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - yvbpsm needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it
modules the change moves:
- dunst (changed)
machines:
- a machine (f35): does not compose; the change adds 0 resource(s) and removes 366
- 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; the change adds 0 resource(s) and removes 2 (-file:gitea.grant-npm-package-registry-f35.build-agent, -file:gitea.grant-npm-package-registry-yvbpsm.build-agent)
- a machine (yvbpsm): does not compose; the change adds 0 resource(s) and removes 329
a merge would rebuild 1 module(s) in 1 tier(s): dunst
mesh-controller: the change fails the merge gate
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 36406 strings of 629 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
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.062s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `2a16d39a`
- `mesh/merge-gate`: **FAIL** — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - f35 needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it (modules: dunst)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds dunst → g14, shanks; no bus step
- tier 0: dunst
- g14: receives dunst
- shanks: receives dunst
Run by the build seat on shanks as `build-1791583659664939762` (`builds --log build-1791583659664939762`).
```
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
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
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is left out of the rest of the mesh: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
f35 is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
yvbpsm is not counted as on the network: it does not resolve: these assignments cannot be applied:
- dunst and rofi both declare the package "rofi"
merge gate: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - f35 needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it
judged by controller development build against the facts of 2026-10-09T22:05:01Z
fails:
- a machine (f35): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - f35 needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it
- a machine (yvbpsm): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - yvbpsm needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - yvbpsm needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - yvbpsm needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - yvbpsm needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it
modules the change moves:
- dunst (changed)
machines:
- a machine (f35): does not compose; the change adds 0 resource(s) and removes 366
- 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; the change adds 0 resource(s) and removes 2 (-file:gitea.grant-npm-package-registry-f35.build-agent, -file:gitea.grant-npm-package-registry-yvbpsm.build-agent)
- a machine (yvbpsm): does not compose; the change adds 0 resource(s) and removes 329
a merge would rebuild 1 module(s) in 1 tier(s): dunst
mesh-controller: the change fails the merge gate
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 36406 strings of 629 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
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.062s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds dunst → g14, shanks; no bus step
tier 0: dunst
g14: receives dunst
shanks: receives dunst
Run by the build seat on ace as build-1791583932811542760 (builds --log build-1791583932811542760).
--- the gate: dunst
dunst: ok, 6 tool(s)
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:05:01Z 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-09T22:05:01Z
modules the change moves:
- dunst (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 1 module(s) in 1 tier(s): dunst
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 36406 strings of 629 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
agent-home: no archive and no file written into under the agent's home
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.055s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `f0558980`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds dunst → g14, shanks; no bus step
- tier 0: dunst
- g14: receives dunst
- shanks: receives dunst
Run by the build seat on ace as `build-1791583932811542760` (`builds --log build-1791583932811542760`).
```
--- the gate: dunst
dunst: ok, 6 tool(s)
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:05:01Z 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-09T22:05:01Z
modules the change moves:
- dunst (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 1 module(s) in 1 tier(s): dunst
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 36406 strings of 629 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
agent-home: no archive and no file written into under the agent's home
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.055s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds dunst → g14, shanks; no bus step
tier 0: dunst
g14: receives dunst
shanks: receives dunst
Run by the build seat on g14 as build-1791583871916183646 (builds --log build-1791583871916183646).
--- the gate: dunst
dunst: ok, 6 tool(s)
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:05:01Z 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-09T22:05:01Z
modules the change moves:
- dunst (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 1 module(s) in 1 tier(s): dunst
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 36406 strings of 629 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
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.071s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `f76396de`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds dunst → g14, shanks; no bus step
- tier 0: dunst
- g14: receives dunst
- shanks: receives dunst
Run by the build seat on g14 as `build-1791583871916183646` (`builds --log build-1791583871916183646`).
```
--- the gate: dunst
dunst: ok, 6 tool(s)
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:05:01Z 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-09T22:05:01Z
modules the change moves:
- dunst (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 1 module(s) in 1 tier(s): dunst
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 36406 strings of 629 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
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.071s
--- its merge-check-typescript.sh (typescript toolchain)
```
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.
Fixes novox/hq issue 360 (the operator cannot choose a notification's action on a touchpad), hq PR #260.
Acceptance: on the laptop and the workstation, a tap on a notification with one action runs it; with several, rofi opens to choose one; a notification without actions closes on a tap.
Changes (module dunst only):
mouse_left_click = do_action, close_current(wasclose_current). Middle and right click unchanged. Semantics from dunst(5) and dunst 1.13.2'snotification_do_action/input.c/menu.c: one action runs; several open the menu for that notification and the close waits for the menu (an Escape leaves it shown); none closes. Edge: a notification without actions but with one link opens the link.dmenu = rofi -dmenu -p dunst(wasdmenu -p dunst; the node-launcher'sdmenulives in~/.local/bin, which the running dunst's PATH does not hold, so the menu never opened).rofideclared (the file names it; the rofi module declares it too, asgit/nfs-utilsare shared today).node-display-session(i3):bindsym $mod+n exec --no-startup-id dunstctl context.$mod+nis bound nowhere else in the catalogue.sendrefuses the tokendefault, which dunst would run at a tap without the menu.Nothing else in the dunstrc changes; the font-size and width settings are untouched. Local:
go vet,go test -raceand the controller'smodule check(dunst: ok) pass.Delivery
novox/mesh-catalog@f055898089e8— superseded since 2026-10-09T22:21:15ZCovered: delivered after its walk was superseded: the walk plan-1791584475080493383, which took its walk plan-1791584474746812089 over, ended done
Delivery plan — builds dunst → g14, 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
2a16d39amesh/merge-gate: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — these assignments cannot be applied: - dunst and rofi both declare the package "rofi" - f35 needs "artifact-store" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "internal-acme-ca" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "npm-package-registry" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it - f35 needs "wildcard-resolution" from ygcyr, and they are not both on the private network — assign mesh-wireguard to whichever is missing it (modules: dunst)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds dunst → g14, shanks; no bus step
Run by the build seat on shanks as
build-1791583659664939762(builds --log build-1791583659664939762).Merge check at
f0558980mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds dunst → g14, shanks; no bus step
Run by the build seat on ace as
build-1791583932811542760(builds --log build-1791583932811542760).Merge check at
f76396demesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds dunst → g14, shanks; no bus step
Run by the build seat on g14 as
build-1791583871916183646(builds --log build-1791583871916183646).