Feature feat/mail-seats (playbook 07), one delivery group with novox/mesh-controller and novox/mesh-catalog.
Issue 835 (ADR 0380): the controller now publishes mesh.seat.operator-channel.tool.tell; the installer's first user list in examples/foundation-first-node.lock carries the same grant, at the place the controller composes it, so the genesis list stays what the controller would compose.
Reviewed locally: round 1 approved at c3b2fce. merge-check.sh green.
Feature feat/mail-seats (playbook 07), one delivery group with novox/mesh-controller and novox/mesh-catalog.
Issue 835 (ADR 0380): the controller now publishes mesh.seat.operator-channel.tool.tell; the installer's first user list in examples/foundation-first-node.lock carries the same grant, at the place the controller composes it, so the genesis list stays what the controller would compose.
Reviewed locally: round 1 approved at c3b2fce. merge-check.sh green.
ADR 0380's secret-given announcement asks operator-channel.tell over the
bus; the genesis bundle's first user list must already carry that
publish subject, in the same place the controller composes it
(internal/broker, mesh-controller ms-835 435468c1), or a first node's
controller starts without the grant until its own first composition.
2026-10-15 17:04 (new) → proposed (announced): novox/mesh-host#113's head announced
2026-10-15 17:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-15 17:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-15 17:09 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-15 17:09 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@c3b2fce0a29f` — **delivered** since 2026-10-15T17:09:32Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `feat/mail-seats`, in order: novox/mesh-controller@a18c17d3cc5f → novox/mesh-catalog@c2cd2e1eb15e → novox/mesh-host@c3b2fce0a29f
- novox/mesh-controller@a18c17d3cc5f before novox/mesh-catalog@c2cd2e1eb15e: declared
**Transitions**
- 2026-10-15 17:04 (new) → proposed (announced): novox/mesh-host#113's head announced
- 2026-10-15 17:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-15 17:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-15 17:09 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-15 17:09 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.
Feature feat/mail-seats (playbook 07), one delivery group with novox/mesh-controller and novox/mesh-catalog.
Issue 835 (ADR 0380): the controller now publishes mesh.seat.operator-channel.tool.tell; the installer's first user list in examples/foundation-first-node.lock carries the same grant, at the place the controller composes it, so the genesis list stays what the controller would compose.
Reviewed locally: round 1 approved at
c3b2fce. merge-check.sh green.Delivery
novox/mesh-host@c3b2fce0a29f— delivered since 2026-10-15T17:09:32ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
feat/mail-seats, in order: novox/mesh-controller@a18c17d3cc → novox/mesh-catalog@c2cd2e1eb1 → novox/mesh-host@c3b2fce0a2Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.