examples/foundation-first-node-nats.lock: the controller's carried publish list gains mesh.seat.node-backup.tool.backed-up.*, matching what the controller now composes (mesh-controller's TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose fails without it).
internal/apply/apply.go: what the engine already did on unassign is unchanged — a directory with anything in it is kept, an empty one removed — but the report no longer says "remove it by hand"; it says an unassignment never deletes data and only cleanup delete removes retired data. Test asserts the wording.
Before this: unassigning kept a non-empty data directory, forgot its record, and told the reader to delete it by hand.
go test -race ./... green, vet/gofmt clean. Merge together with mesh-controller's PR.
hq ADR 0233.
- `examples/foundation-first-node-nats.lock`: the controller's carried publish list gains `mesh.seat.node-backup.tool.backed-up.*`, matching what the controller now composes (mesh-controller's `TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose` fails without it).
- `internal/apply/apply.go`: what the engine already did on unassign is unchanged — a directory with anything in it is kept, an empty one removed — but the report no longer says "remove it by hand"; it says an unassignment never deletes data and only `cleanup delete` removes retired data. Test asserts the wording.
Before this: unassigning kept a non-empty data directory, **forgot its record**, and told the reader to delete it by hand.
`go test -race ./...` green, vet/gofmt clean. Merge together with mesh-controller's PR.
The installer's first user list must match the controller's composed grant, which now reads every
machine's backup holder; and a kept directory's report pointed at the one act that loses data.
Deliverynovox/mesh-host@8d853791b2fc — 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#39 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@8d853791b2fc` — **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#39 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.
hq ADR 0233.
examples/foundation-first-node-nats.lock: the controller's carried publish list gainsmesh.seat.node-backup.tool.backed-up.*, matching what the controller now composes (mesh-controller'sTestTheInstallersFirstUserListIsWhatTheControllerWouldComposefails without it).internal/apply/apply.go: what the engine already did on unassign is unchanged — a directory with anything in it is kept, an empty one removed — but the report no longer says "remove it by hand"; it says an unassignment never deletes data and onlycleanup deleteremoves retired data. Test asserts the wording.Before this: unassigning kept a non-empty data directory, forgot its record, and told the reader to delete it by hand.
go test -race ./...green, vet/gofmt clean. Merge together with mesh-controller's PR.Delivery
novox/mesh-host@8d853791b2fc— 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.