Registers issue 332 (playbook 03), status located. The node-service-manager seat had no verb to clear a failed unit's record (systemctl reset-failed), or to say what wants a unit and whether an enable link naming it dangles. The only step left was a shell, which ADR 0245 rules out.
The fix lands in the three steps of ADR 0246:
mesh-controller #158 promises reset-failed and wanted-by as optional.
mesh-catalog #137: the systemd module serves them, merged after step 1 is delivered.
A later controller change requires them.
fixed-by: is filled at resolution. merge-check.sh passes locally.
Registers issue 332 (playbook 03), status `located`. The `node-service-manager` seat had no verb to clear a failed unit's record (`systemctl reset-failed`), or to say what wants a unit and whether an enable link naming it dangles. The only step left was a shell, which ADR 0245 rules out.
The fix lands in the three steps of ADR 0246:
1. mesh-controller #158 promises `reset-failed` and `wanted-by` as optional.
2. mesh-catalog #137: the systemd module serves them, merged after step 1 is delivered.
3. A later controller change requires them.
`fixed-by:` is filled at resolution. `merge-check.sh` passes locally.
A leftover user unit stayed raised on the workstation: no seat verb showed
the dangling enable link that keeps asking for it, or reset its failed
record, so the only step left was a shell. Lands per ADR 0246.
Deliverynovox/hq@fd6c452e619f — delivered since 2026-10-08T15:53:04Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-08 15:40 (new) → proposed (announced): novox/hq#222's head announced
2026-10-08 15:42 proposed → checked (checked): the verdict names this commit
2026-10-08 15:42 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 → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@fd6c452e619f` — **delivered** since 2026-10-08T15:53:04Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-08 15:40 (new) → proposed (announced): novox/hq#222's head announced
- 2026-10-08 15:42 proposed → checked (checked): the verdict names this commit
- 2026-10-08 15:42 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 → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
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.
Registers issue 332 (playbook 03), status
located. Thenode-service-managerseat had no verb to clear a failed unit's record (systemctl reset-failed), or to say what wants a unit and whether an enable link naming it dangles. The only step left was a shell, which ADR 0245 rules out.The fix lands in the three steps of ADR 0246:
reset-failedandwanted-byas optional.fixed-by:is filled at resolution.merge-check.shpasses locally.Delivery
novox/hq@fd6c452e619f— delivered since 2026-10-08T15:53:04ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.