Follow-up to #158, from the review of mesh-catalog #137. systemctl disable does not remove an enable link once the unit's file is gone, so a leftover unit stays wanted at every login.
unlink-dangling {unit, scope, why} (why required): removes the dangling enable links named for one unit in the account's or the machine's own configuration, recording each first. It replaces rm ~/.config/systemd/user/*.wants/<unit> and unlink /etc/systemd/system/*.wants/<unit>.
Optional (ADR 0246 step 1): today's holder still holds the seat, and a holder serving it is accepted.
Test: TestResetFailedAndWantedByAreOptionalVerbsOfTheServiceManager extended to cover the new verb: optional, that why is required, its replaces, and read back optional from the row. merge-check.sh passed locally. The holder is mesh-catalog's feat/systemd-unlink-dangling.
Follow-up to #158, from the review of mesh-catalog #137. `systemctl disable` does not remove an enable link once the unit's file is gone, so a leftover unit stays wanted at every login.
- `unlink-dangling {unit, scope, why}` (`why` required): removes the dangling enable links named for one unit in the account's or the machine's own configuration, recording each first. It replaces `rm ~/.config/systemd/user/*.wants/<unit>` and `unlink /etc/systemd/system/*.wants/<unit>`.
- Optional (ADR 0246 step 1): today's holder still holds the seat, and a holder serving it is accepted.
Test: `TestResetFailedAndWantedByAreOptionalVerbsOfTheServiceManager` extended to cover the new verb: optional, that `why` is required, its replaces, and read back optional from the row. `merge-check.sh` passed locally. The holder is mesh-catalog's `feat/systemd-unlink-dangling`.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
disable cannot remove an enable link whose unit file is gone, so a
leftover unit stays wanted at every login with no verb to end it. Optional
until the systemd module serves it (ADR 0246 step 1).
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Transitions
2026-10-08 15:39 (new) → proposed (announced): novox/mesh-controller#160's head announced
2026-10-08 15:47 proposed → checked (checked): the verdict names this commit
2026-10-08 15:47 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 15:53 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 15:53 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-08 15:55 delivering → 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-controller@b5f2c3b961c5` — **superseded** since 2026-10-08T15:55:07Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
**Transitions**
- 2026-10-08 15:39 (new) → proposed (announced): novox/mesh-controller#160's head announced
- 2026-10-08 15:47 proposed → checked (checked): the verdict names this commit
- 2026-10-08 15:47 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 15:53 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-08 15:53 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-08 15:55 delivering → 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`.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as build-1791473964154572091 (builds --log build-1791473964154572091).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 51 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T15:33:40Z 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-08T15:33:40Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.033s
ok github.com/novox/mesh-controller/cmd/mesh-controller 183.836s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.195s
ok github.com/novox/mesh-controller/internal/artifacts 1.080s
ok github.com/novox/mesh-controller/internal/broker 2.655s
ok github.com/novox/mesh-controller/internal/builder 1.936s
ok github.com/novox/mesh-controller/internal/catalogue 4.813s
ok github.com/novox/mesh-controller/internal/conditions 2.236s
ok github.com/novox/mesh-controller/internal/envfile 1.052s
ok github.com/novox/mesh-controller/internal/facts 1.054s
ok github.com/novox/mesh-controller/internal/identity 4.714s
ok github.com/novox/mesh-controller/internal/inventory 83.735s
ok github.com/novox/mesh-controller/internal/lease 17.700s
ok github.com/novox/mesh-controller/internal/licences 4.308s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.044s
ok github.com/novox/mesh-controller/internal/link 46.195s
ok github.com/novox/mesh-controller/internal/lint 2.132s
ok github.com/novox/mesh-controller/internal/outward 1.080s
ok github.com/novox/mesh-controller/internal/overlay 1.063s
ok github.com/novox/mesh-controller/internal/secrets 1.554s
ok github.com/novox/mesh-controller/internal/store 3.452s
ok github.com/novox/mesh-controller/internal/testbus 1.248s
ok github.com/novox/mesh-controller/internal/token 1.015s
**Merge check** at `b5f2c3b9`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as `build-1791473964154572091` (`builds --log build-1791473964154572091`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 51 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T15:33:40Z 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-08T15:33:40Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.033s
ok github.com/novox/mesh-controller/cmd/mesh-controller 183.836s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.195s
ok github.com/novox/mesh-controller/internal/artifacts 1.080s
ok github.com/novox/mesh-controller/internal/broker 2.655s
ok github.com/novox/mesh-controller/internal/builder 1.936s
ok github.com/novox/mesh-controller/internal/catalogue 4.813s
ok github.com/novox/mesh-controller/internal/conditions 2.236s
ok github.com/novox/mesh-controller/internal/envfile 1.052s
ok github.com/novox/mesh-controller/internal/facts 1.054s
ok github.com/novox/mesh-controller/internal/identity 4.714s
ok github.com/novox/mesh-controller/internal/inventory 83.735s
ok github.com/novox/mesh-controller/internal/lease 17.700s
ok github.com/novox/mesh-controller/internal/licences 4.308s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.044s
ok github.com/novox/mesh-controller/internal/link 46.195s
ok github.com/novox/mesh-controller/internal/lint 2.132s
ok github.com/novox/mesh-controller/internal/outward 1.080s
ok github.com/novox/mesh-controller/internal/overlay 1.063s
ok github.com/novox/mesh-controller/internal/secrets 1.554s
ok github.com/novox/mesh-controller/internal/store 3.452s
ok github.com/novox/mesh-controller/internal/testbus 1.248s
ok github.com/novox/mesh-controller/internal/token 1.015s
```
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.
Follow-up to #158, from the review of mesh-catalog #137.
systemctl disabledoes not remove an enable link once the unit's file is gone, so a leftover unit stays wanted at every login.unlink-dangling {unit, scope, why}(whyrequired): removes the dangling enable links named for one unit in the account's or the machine's own configuration, recording each first. It replacesrm ~/.config/systemd/user/*.wants/<unit>andunlink /etc/systemd/system/*.wants/<unit>.Test:
TestResetFailedAndWantedByAreOptionalVerbsOfTheServiceManagerextended to cover the new verb: optional, thatwhyis required, its replaces, and read back optional from the row.merge-check.shpassed locally. The holder is mesh-catalog'sfeat/systemd-unlink-dangling.Delivery
novox/mesh-controller@b5f2c3b961c5— superseded since 2026-10-08T15:55:07ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
b5f2c3b9mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791473964154572091(builds --log build-1791473964154572091).