The installer's carried user list must equal what the controller derives (mesh-controller's TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose reads this file). Adds the controller's subscriptions to mesh.mod.*.event.provisioner.{failing,recovered} (hq ADR 0224, mesh-controller #70) and the build seats' tool.> publishes it already derived (hq ADR 0219, drift that test caught).
The installer's carried user list must equal what the controller derives (mesh-controller's `TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose` reads this file). Adds the controller's subscriptions to `mesh.mod.*.event.provisioner.{failing,recovered}` (hq ADR 0224, mesh-controller #70) and the build seats' `tool.>` publishes it already derived (hq ADR 0219, drift that test caught).
Merge after mesh-controller #70.
The carried user list must equal what the controller derives (its test reads
this file): add the provisioner.failing/recovered subscriptions (hq ADR 0224)
and the build seats' tool publishes it already derived (hq ADR 0219).
Deliverynovox/mesh-host@07430240bb8f — held since 2026-10-06T23:05:28Z
Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#28 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-host@07430240bb8f` — **held** since 2026-10-06T23:05:28Z
Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on.
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#28 merged; its head was not heard by this owner, so it is made from the forge's word
- 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
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.
The installer's carried user list must equal what the controller derives (mesh-controller's
TestTheInstallersFirstUserListIsWhatTheControllerWouldComposereads this file). Adds the controller's subscriptions tomesh.mod.*.event.provisioner.{failing,recovered}(hq ADR 0224, mesh-controller #70) and the build seats'tool.>publishes it already derived (hq ADR 0219, drift that test caught).Merge after mesh-controller #70.
Delivery
novox/mesh-host@07430240bb8f— held since 2026-10-06T23:05:28ZHeld for a person: merged without a passing check: only a person decides that it goes on —
mesh-delivery.releasewith why lets it go on.Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.