Why (issue 525 step 3, ADR 0304 §1 and ADR 0306 §2). The controller is to ask mesh-delivery.groups, when a merge is heard, whether its delivery group still has a member to merge, so a merge in no waiting group is cut at once instead of waiting the merge window. The controller's composed bus grant gains mesh.seat.mesh-delivery.tool.groups (mesh-controller branch feat/525-a-lone-merge-skips-the-window), and the installer's first user list must name it too, or the controller's broker test fails: "the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups]".
What changes: one entry, mesh.seat.mesh-delivery.tool.groups, after ...tool.times in the controller's publish list in examples/foundation-first-node-nats.lock — the same shape as 212a3cc did for times (ADR 0282).
Order: this merges and delivers first; the controller branch then recaptures testdata/beside/mesh-host at it.
Note: mesh-host restarts the node-engine on every machine: a core delivery of its own.
**Why** (issue 525 step 3, ADR 0304 §1 and ADR 0306 §2). The controller is to ask `mesh-delivery.groups`, when a merge is heard, whether its delivery group still has a member to merge, so a merge in no waiting group is cut at once instead of waiting the merge window. The controller's composed bus grant gains `mesh.seat.mesh-delivery.tool.groups` (mesh-controller branch feat/525-a-lone-merge-skips-the-window), and the installer's first user list must name it too, or the controller's broker test fails: "the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups]".
**What changes**: one entry, `mesh.seat.mesh-delivery.tool.groups`, after `...tool.times` in the controller's publish list in `examples/foundation-first-node-nats.lock` — the same shape as 212a3cc did for `times` (ADR 0282).
**Order**: this merges and delivers first; the controller branch then recaptures `testdata/beside/mesh-host` at it.
**Note**: mesh-host restarts the node-engine on every machine: a core delivery of its own.
The controller is to ask mesh-delivery whether a merge's delivery
group still has a member to merge, so that a merge in no waiting group
is cut at once (ADR 0304, ADR 0306); its bus grant names the verb, and
the installer's first user list must too, as for times (212a3cc).
Deliverynovox/mesh-host@90ce9e9d9fcd — delivered since 2026-10-12T10:14:43Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-12 10:09 (new) → proposed (announced): novox/mesh-host#85's head announced
2026-10-12 10:10 proposed → checked (checked): the verdict names this commit
2026-10-12 10:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 10:14 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 10:14 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/mesh-host@90ce9e9d9fcd` — **delivered** since 2026-10-12T10:14:43Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-12 10:09 (new) → proposed (announced): novox/mesh-host#85's head announced
- 2026-10-12 10:10 proposed → checked (checked): the verdict names this commit
- 2026-10-12 10:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 10:14 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 10:14 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.
Why (issue 525 step 3, ADR 0304 §1 and ADR 0306 §2). The controller is to ask
mesh-delivery.groups, when a merge is heard, whether its delivery group still has a member to merge, so a merge in no waiting group is cut at once instead of waiting the merge window. The controller's composed bus grant gainsmesh.seat.mesh-delivery.tool.groups(mesh-controller branch feat/525-a-lone-merge-skips-the-window), and the installer's first user list must name it too, or the controller's broker test fails: "the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups]".What changes: one entry,
mesh.seat.mesh-delivery.tool.groups, after...tool.timesin the controller's publish list inexamples/foundation-first-node-nats.lock— the same shape as212a3ccdid fortimes(ADR 0282).Order: this merges and delivers first; the controller branch then recaptures
testdata/beside/mesh-hostat it.Note: mesh-host restarts the node-engine on every machine: a core delivery of its own.
Delivery
novox/mesh-host@90ce9e9d9fcd— delivered since 2026-10-12T10:14:43ZDelivery 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.