Phase 5: check the node-engine's changes against every machine before they merge (hq ADR 0237) #42

2026-10-06T19:18:17Z

mesh-admin commented

2026-10-06 19:18:17 +00:00

hq ADR 0237 decisions 3-4.

merge-check.sh: fmt, vet, the suite; then the controller the mesh runs, built with this tree's validate and internal/declaration in place of the vendored ones, runs merge-gate over the facts snapshot — a node-engine change that would refuse what the mesh sends today fails its PR naming the machine. (Suite verified green inside the mesh's Go toolchain image.)
examples/foundation-first-node-nats.lock: the controller may publish mesh.seat.mesh-controller.event.checked and subscribe mesh.mod.gitea.event.pull.updated, as it now composes.

Merge together with mesh-controller #96: the controller's genesis-template test compares the two in both directions.

hq ADR 0237 decisions 3-4. - `merge-check.sh`: fmt, vet, the suite; then the controller the mesh runs, built with *this tree's* `validate` and `internal/declaration` in place of the vendored ones, runs `merge-gate` over the facts snapshot — a node-engine change that would refuse what the mesh sends today fails its PR naming the machine. (Suite verified green inside the mesh's Go toolchain image.) - `examples/foundation-first-node-nats.lock`: the controller may publish `mesh.seat.mesh-controller.event.checked` and subscribe `mesh.mod.gitea.event.pull.updated`, as it now composes. **Merge together with mesh-controller #96**: the controller's genesis-template test compares the two in both directions.

mesh-admin added 1 commit 2026-10-06 19:18:17 +00:00

Check the node-engine's changes against every machine before they merge (hq ADR 0237) 2fb7c91eaf

merge-check.sh runs the suite, then builds the controller the mesh runs with this change's
validator in place of the one it vendors and runs the merge gate: a change to the node-engine
that would refuse what the mesh sends today fails its pull request, naming the machine. The
installer's first user list lets the controller say a check's verdict and hear a pull request's
head, as the controller now composes it.

mesh-admin merged commit f39e282fed into main

2026-10-06 19:19:20 +00:00

mesh-admin deleted branch feat/merge-gate

2026-10-06 19:19:21 +00:00

mesh-admin commented

2026-10-06 23:10:57 +00:00

Delivery novox/mesh-host@f39e282fed82 — delivered since 2026-10-06T23:05:28Z

Machines

mesh-host on ace: passed — healthy 3 times over 2m37s
mesh-host on the rest running it: sent

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#42 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
2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
2026-10-06 23:05 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-host@f39e282fed82` — **delivered** since 2026-10-06T23:05:28Z **Machines** - mesh-host on ace: passed — healthy 3 times over 2m37s - mesh-host on the rest running it: sent **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#42 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 - 2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go` - 2026-10-06 23:05 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#42