Fixes the controller half of novox/hq issue 234 (critical): a later declaration left out four assigned modules, and a machine applied it. Decision: issue 234 note of 2026-10-11 (questions 2 and 3). Needs novox/mesh-host#82 first: this pins the node-engine at that PR's head (20d5af9), because the controller validates every declaration with the node-engine's own parser, which must read generation before any machine is sent it. Once #82 merges, the pin moves to its merge, as for issue 361.
What changes
Assignment generation: migration 0094 adds a one-row counter assignment_generation, seeded 1. Row triggers on assignment raise it on insert or delete, and on an update only when the row changed (when (old is distinct from new)). It moves in the same transaction as every assignment change, including one taken by a node's removal or a module's rename. The controller's inventory has no consolidated schema file beside its migrations: a fresh store applies every numbered migration, so 0094 is both.
The declaration carries it: read in allot, before the composition reads any assignment. Sent as generation only to a machine whose engine's ordered reports say reads_generation.
No put-back mark: a gate puts a machine back by composing it again through allot, so the put-back carries the generation as it stands and is never older than what the machine applied. mesh-host#82 still reads put_back; this controller never sends it.
The would-send is stamped the same way (facts.go, push's digests) with the generation the machine was last sent. node.sent_generation is written in the same transaction as the digest.
Every send is recorded in declaration_send in that transaction, under a savepoint: node, sequence, lease epoch, sender (caller, pid, host, build), generation composed from, digest, modules named; newest 200 per machine. If the send's own row cannot be written, the machine's record still commits, the send does not read as failed, and the push says SEND NOT RECORDED on stderr and in its output.
Every refusal raises S20 (machine.<node>.older-generation, warning, for an hour): on the send it refused, naming the sender, both generations, the sequence and the modules; or, for a sequence the mesh has no send for, as a row of its own whose sender is said to be unknown.
A counter behind the machine (the refused send carried the counter as it stands, so a store was put back from a backup): the counter is raised past what the machine applied, and S20 says so and asks for push <node>. Nothing is pushed from the refusal handler: it runs in the receive loop, and a push there would hold the loop and the node's hold for as long as the push takes.
What a machine was last told: plan <node> shows it. status and node show follow after #223 (their files are in it), tracked as an issue.
Compatibility
Older engine: never says reads_generation, is sent no new key; its bytes are what they were.
Newer engine with an older controller: is sent no generation, refuses nothing for one.
plan --json, plan --diff and the merge gate compose without an order, so they compose every machine as before.
Moved with the pin
The node-engine's main requires a newer mesh-sdk (f047d0a → 33917f9; it only adds the state counter and go/health). testdata/beside captures the SDK's conformance fixtures at that commit; they are unchanged.
Tests (written first)
Unit tests (on main they do not compile: no generation, record or reads_generation exists there): the generation is sent only to a machine that reads one, and no put-back mark; the sender is named; S20 names a sender, an unknown sender and a counter behind (asks for a push); only the counter as it stands counts as behind; S20 in the signals-table walk; TestTheGenerationOnTheWire. Store-backed (skip without MESH_TEST_POSTGRES, run on the build seat): every assignment change raises the generation, an update that changes nothing does not, the counter is raised past a machine's and never lowered, a send is recorded with sender, generation and modules and a refusal is kept on it, a refusal of an unrecorded sequence is kept with an unknown sender and is not the last send, a send row that cannot be written leaves the digest and generation written and returns SendNotRecordedError, reads_generation follows the latest report.
gofmt, go vet ./... and go test ./... pass locally (store-backed tests skipped). Touches no file of #223 or #225.
after: novox/mesh-host
Fixes the controller half of novox/hq issue 234 (critical): a later declaration left out four assigned modules, and a machine applied it. Decision: issue 234 note of 2026-10-11 (questions 2 and 3). Needs novox/mesh-host#82 first: this pins the node-engine at that PR's head (20d5af9), because the controller validates every declaration with the node-engine's own parser, which must read `generation` before any machine is sent it. Once #82 merges, the pin moves to its merge, as for issue 361.
## What changes
- **Assignment generation**: migration 0094 adds a one-row counter `assignment_generation`, seeded 1. Row triggers on `assignment` raise it on insert or delete, and on an update only when the row changed (`when (old is distinct from new)`). It moves in the same transaction as every assignment change, including one taken by a node's removal or a module's rename. The controller's inventory has no consolidated schema file beside its migrations: a fresh store applies every numbered migration, so 0094 is both.
- **The declaration carries it**: read in `allot`, before the composition reads any assignment. Sent as `generation` only to a machine whose engine's ordered reports say `reads_generation`.
- **No put-back mark**: a gate puts a machine back by composing it again through `allot`, so the put-back carries the generation as it stands and is never older than what the machine applied. mesh-host#82 still reads `put_back`; this controller never sends it.
- **The would-send is stamped the same way** (`facts.go`, push's digests) with the generation the machine was last sent. `node.sent_generation` is written in the same transaction as the digest.
- **Every send is recorded** in `declaration_send` in that transaction, under a savepoint: node, sequence, lease epoch, sender (caller, pid, host, build), generation composed from, digest, modules named; newest 200 per machine. If the send's own row cannot be written, the machine's record still commits, the send does not read as failed, and the push says `SEND NOT RECORDED` on stderr and in its output.
- **Every refusal raises S20** (`machine.<node>.older-generation`, warning, for an hour): on the send it refused, naming the sender, both generations, the sequence and the modules; or, for a sequence the mesh has no send for, as a row of its own whose sender is said to be unknown.
- **A counter behind the machine** (the refused send carried the counter as it stands, so a store was put back from a backup): the counter is raised past what the machine applied, and S20 says so and asks for `push <node>`. Nothing is pushed from the refusal handler: it runs in the receive loop, and a push there would hold the loop and the node's hold for as long as the push takes.
- **What a machine was last told**: `plan <node>` shows it. `status` and `node show` follow after #223 (their files are in it), tracked as an issue.
## Compatibility
- Older engine: never says `reads_generation`, is sent no new key; its bytes are what they were.
- Newer engine with an older controller: is sent no generation, refuses nothing for one.
- `plan --json`, `plan --diff` and the merge gate compose without an order, so they compose every machine as before.
## Moved with the pin
The node-engine's main requires a newer mesh-sdk (f047d0a → 33917f9; it only adds the state counter and go/health). `testdata/beside` captures the SDK's conformance fixtures at that commit; they are unchanged.
## Tests (written first)
Unit tests (on main they do not compile: no generation, record or `reads_generation` exists there): the generation is sent only to a machine that reads one, and no put-back mark; the sender is named; S20 names a sender, an unknown sender and a counter behind (asks for a push); only the counter as it stands counts as behind; S20 in the signals-table walk; `TestTheGenerationOnTheWire`. Store-backed (skip without MESH_TEST_POSTGRES, run on the build seat): every assignment change raises the generation, an update that changes nothing does not, the counter is raised past a machine's and never lowered, a send is recorded with sender, generation and modules and a refusal is kept on it, a refusal of an unrecorded sequence is kept with an unknown sender and is not the last send, a send row that cannot be written leaves the digest and generation written and returns SendNotRecordedError, reads_generation follows the latest report.
`gofmt`, `go vet ./...` and `go test ./...` pass locally (store-backed tests skipped). Touches no file of #223 or #225.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
A declaration newer in sequence than every other named four fewer modules
than the assignments held, a machine applied it, and nothing the mesh kept
said who sent it or from what view. The store now raises an assignment
generation in the same transaction as every assignment change (a trigger,
so a cascade counts too); a send reads it before composing, carries it to
engines that said they read it, marks a gate's put-back, and is recorded
with its sequence, sender, generation and modules. The would-send is
stamped with what was last sent, so nothing reads behind for it; a refusal
is kept on the send it refused and raised as S20 naming the sender; plan
says what the machine was last told.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 4m7s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m41s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 2m25s
route-proxy on the rest running it: sent
Transitions
2026-10-11 17:00 (new) → proposed (announced): novox/mesh-controller#227's head announced
2026-10-11 17:07 proposed → checked (checked): the verdict names this commit
2026-10-11 17:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 17:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 17:10 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-11 17:26 delivering → delivered (done): its walk is done, carrying its own commit: 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.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@0c675bcdb5aa` — **delivered** since 2026-10-11T17:26:31Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 4m7s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m41s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 2m25s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-11 17:00 (new) → proposed (announced): novox/mesh-controller#227's head announced
- 2026-10-11 17:07 proposed → checked (checked): the verdict names this commit
- 2026-10-11 17:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 17:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 17:10 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-11 17:26 delivering → delivered (done): its walk is done, carrying its own commit: 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`.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on ace as build-1791711064767274851 (builds --log build-1791711064767274851).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:30:02Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:30:02Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.032s
ok github.com/novox/mesh-controller/cmd/mesh-controller 205.301s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.031s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.044s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/route-proxy 1.126s
ok github.com/novox/mesh-controller/internal/artifacts 1.069s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.643s
ok github.com/novox/mesh-controller/internal/builder 3.695s
ok github.com/novox/mesh-controller/internal/catalogue 6.564s
ok github.com/novox/mesh-controller/internal/conditions 2.448s
ok github.com/novox/mesh-controller/internal/envfile 1.036s
ok github.com/novox/mesh-controller/internal/facts 1.042s
ok github.com/novox/mesh-controller/internal/identity 4.291s
ok github.com/novox/mesh-controller/internal/inventory 79.603s
ok github.com/novox/mesh-controller/internal/lease 17.684s
ok github.com/novox/mesh-controller/internal/licences 3.855s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.039s
ok github.com/novox/mesh-controller/internal/link 58.619s
ok github.com/novox/mesh-controller/internal/lint 2.130s
ok github.com/novox/mesh-controller/internal/outward 1.077s
ok github.com/novox/mesh-controller/internal/overlay 1.065s
ok github.com/novox/mesh-controller/internal/secrets 1.428s
ok github.com/novox/mesh-controller/internal/store 3.378s
ok github.com/novox/mesh-controller/internal/testbus 1.230s
ok github.com/novox/mesh-controller/internal/token 1.019s
**Merge check** at `313efa82`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on ace as `build-1791711064767274851` (`builds --log build-1791711064767274851`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:30:02Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:30:02Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.032s
ok github.com/novox/mesh-controller/cmd/mesh-controller 205.301s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.031s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.044s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/route-proxy 1.126s
ok github.com/novox/mesh-controller/internal/artifacts 1.069s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.643s
ok github.com/novox/mesh-controller/internal/builder 3.695s
ok github.com/novox/mesh-controller/internal/catalogue 6.564s
ok github.com/novox/mesh-controller/internal/conditions 2.448s
ok github.com/novox/mesh-controller/internal/envfile 1.036s
ok github.com/novox/mesh-controller/internal/facts 1.042s
ok github.com/novox/mesh-controller/internal/identity 4.291s
ok github.com/novox/mesh-controller/internal/inventory 79.603s
ok github.com/novox/mesh-controller/internal/lease 17.684s
ok github.com/novox/mesh-controller/internal/licences 3.855s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.039s
ok github.com/novox/mesh-controller/internal/link 58.619s
ok github.com/novox/mesh-controller/internal/lint 2.130s
ok github.com/novox/mesh-controller/internal/outward 1.077s
ok github.com/novox/mesh-controller/internal/overlay 1.065s
ok github.com/novox/mesh-controller/internal/secrets 1.428s
ok github.com/novox/mesh-controller/internal/store 3.378s
ok github.com/novox/mesh-controller/internal/testbus 1.230s
ok github.com/novox/mesh-controller/internal/token 1.019s
```
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
A refusal of a send the mesh never recorded went only to stderr; it is now kept
with its sender said to be unknown, and raised. A counter behind the machine (a
store put back) is raised and the condition names push, since the receive loop
must not push. The node's digest and generation are one transaction, and a send
record that fails is said loudly without failing the send. The trigger ignores
an update that changes nothing, and the put-back mark is dropped: a put-back is
composed afresh with the current generation.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as build-1791712553933936018 (builds --log build-1791712553933936018).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:55:21Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:55:21Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 236.205s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.059s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.046s
ok github.com/novox/mesh-controller/examples/route-proxy 1.200s
ok github.com/novox/mesh-controller/internal/artifacts 1.087s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.055s
ok github.com/novox/mesh-controller/internal/builder 3.751s
ok github.com/novox/mesh-controller/internal/catalogue 7.166s
ok github.com/novox/mesh-controller/internal/conditions 2.580s
ok github.com/novox/mesh-controller/internal/envfile 1.062s
ok github.com/novox/mesh-controller/internal/facts 1.063s
ok github.com/novox/mesh-controller/internal/identity 5.054s
ok github.com/novox/mesh-controller/internal/inventory 95.232s
ok github.com/novox/mesh-controller/internal/lease 17.718s
ok github.com/novox/mesh-controller/internal/licences 4.620s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.057s
ok github.com/novox/mesh-controller/internal/link 61.142s
ok github.com/novox/mesh-controller/internal/lint 2.367s
ok github.com/novox/mesh-controller/internal/outward 1.083s
ok github.com/novox/mesh-controller/internal/overlay 1.070s
ok github.com/novox/mesh-controller/internal/secrets 1.536s
ok github.com/novox/mesh-controller/internal/store 3.612s
ok github.com/novox/mesh-controller/internal/testbus 1.256s
ok github.com/novox/mesh-controller/internal/token 1.015s
**Merge check** at `5dd0e3c0`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as `build-1791712553933936018` (`builds --log build-1791712553933936018`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:55:21Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:55:21Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 236.205s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.059s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.046s
ok github.com/novox/mesh-controller/examples/route-proxy 1.200s
ok github.com/novox/mesh-controller/internal/artifacts 1.087s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.055s
ok github.com/novox/mesh-controller/internal/builder 3.751s
ok github.com/novox/mesh-controller/internal/catalogue 7.166s
ok github.com/novox/mesh-controller/internal/conditions 2.580s
ok github.com/novox/mesh-controller/internal/envfile 1.062s
ok github.com/novox/mesh-controller/internal/facts 1.063s
ok github.com/novox/mesh-controller/internal/identity 5.054s
ok github.com/novox/mesh-controller/internal/inventory 95.232s
ok github.com/novox/mesh-controller/internal/lease 17.718s
ok github.com/novox/mesh-controller/internal/licences 4.620s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.057s
ok github.com/novox/mesh-controller/internal/link 61.142s
ok github.com/novox/mesh-controller/internal/lint 2.367s
ok github.com/novox/mesh-controller/internal/outward 1.083s
ok github.com/novox/mesh-controller/internal/overlay 1.070s
ok github.com/novox/mesh-controller/internal/secrets 1.536s
ok github.com/novox/mesh-controller/internal/store 3.612s
ok github.com/novox/mesh-controller/internal/testbus 1.256s
ok github.com/novox/mesh-controller/internal/token 1.015s
```
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as build-1791735240401131074 (builds --log build-1791735240401131074).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T16:12:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T16:12:35Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.047s
ok github.com/novox/mesh-controller/cmd/mesh-controller 243.816s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.039s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.038s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.205s
ok github.com/novox/mesh-controller/internal/artifacts 1.073s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.930s
ok github.com/novox/mesh-controller/internal/builder 4.047s
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL
FAIL github.com/novox/mesh-controller/internal/catalogue 7.007s
ok github.com/novox/mesh-controller/internal/conditions 2.684s
ok github.com/novox/mesh-controller/internal/envfile 1.054s
ok github.com/novox/mesh-controller/internal/facts 1.048s
ok github.com/novox/mesh-controller/internal/identity 5.118s
ok github.com/novox/mesh-controller/internal/inventory 98.275s
ok github.com/novox/mesh-controller/internal/lease 17.733s
ok github.com/novox/mesh-controller/internal/licences 4.566s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.040s
ok github.com/novox/mesh-controller/internal/link 61.632s
ok github.com/novox/mesh-controller/internal/lint 2.473s
ok github.com/novox/mesh-controller/internal/outward 1.087s
ok github.com/novox/mesh-controller/internal/overlay 1.063s
ok github.com/novox/mesh-controller/internal/secrets 1.574s
ok github.com/novox/mesh-controller/internal/store 3.599s
ok github.com/novox/mesh-controller/internal/testbus 1.207s
ok github.com/novox/mesh-controller/internal/token 1.019s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL github.com/novox/mesh-controller/internal/catalogue 7.007s
**Merge check** at `5dd0e3c0`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as `build-1791735240401131074` (`builds --log build-1791735240401131074`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T16:12:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T16:12:35Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.047s
ok github.com/novox/mesh-controller/cmd/mesh-controller 243.816s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.039s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.038s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.205s
ok github.com/novox/mesh-controller/internal/artifacts 1.073s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.930s
ok github.com/novox/mesh-controller/internal/builder 4.047s
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL
FAIL github.com/novox/mesh-controller/internal/catalogue 7.007s
ok github.com/novox/mesh-controller/internal/conditions 2.684s
ok github.com/novox/mesh-controller/internal/envfile 1.054s
ok github.com/novox/mesh-controller/internal/facts 1.048s
ok github.com/novox/mesh-controller/internal/identity 5.118s
ok github.com/novox/mesh-controller/internal/inventory 98.275s
ok github.com/novox/mesh-controller/internal/lease 17.733s
ok github.com/novox/mesh-controller/internal/licences 4.566s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.040s
ok github.com/novox/mesh-controller/internal/link 61.632s
ok github.com/novox/mesh-controller/internal/lint 2.473s
ok github.com/novox/mesh-controller/internal/outward 1.087s
ok github.com/novox/mesh-controller/internal/overlay 1.063s
ok github.com/novox/mesh-controller/internal/secrets 1.574s
ok github.com/novox/mesh-controller/internal/store 3.599s
ok github.com/novox/mesh-controller/internal/testbus 1.207s
ok github.com/novox/mesh-controller/internal/token 1.019s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL github.com/novox/mesh-controller/internal/catalogue 7.007s
```
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on ace as build-1791737581813168769 (builds --log build-1791737581813168769).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T16:22:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T16:22:35Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 205.607s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/route-proxy 1.123s
ok github.com/novox/mesh-controller/internal/artifacts 1.035s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.663s
ok github.com/novox/mesh-controller/internal/builder 3.503s
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL
FAIL github.com/novox/mesh-controller/internal/catalogue 5.678s
ok github.com/novox/mesh-controller/internal/conditions 2.486s
ok github.com/novox/mesh-controller/internal/envfile 1.063s
ok github.com/novox/mesh-controller/internal/facts 1.065s
ok github.com/novox/mesh-controller/internal/identity 4.247s
ok github.com/novox/mesh-controller/internal/inventory 80.325s
ok github.com/novox/mesh-controller/internal/lease 17.709s
ok github.com/novox/mesh-controller/internal/licences 3.921s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.093s
ok github.com/novox/mesh-controller/internal/link 58.475s
ok github.com/novox/mesh-controller/internal/lint 2.176s
ok github.com/novox/mesh-controller/internal/outward 1.089s
ok github.com/novox/mesh-controller/internal/overlay 1.078s
ok github.com/novox/mesh-controller/internal/secrets 1.458s
ok github.com/novox/mesh-controller/internal/store 3.322s
ok github.com/novox/mesh-controller/internal/testbus 1.239s
ok github.com/novox/mesh-controller/internal/token 1.019s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL github.com/novox/mesh-controller/internal/catalogue 5.678s
**Merge check** at `5dd0e3c0`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on ace as `build-1791737581813168769` (`builds --log build-1791737581813168769`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T16:22:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T16:22:35Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 205.607s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/route-proxy 1.123s
ok github.com/novox/mesh-controller/internal/artifacts 1.035s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.663s
ok github.com/novox/mesh-controller/internal/builder 3.503s
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL
FAIL github.com/novox/mesh-controller/internal/catalogue 5.678s
ok github.com/novox/mesh-controller/internal/conditions 2.486s
ok github.com/novox/mesh-controller/internal/envfile 1.063s
ok github.com/novox/mesh-controller/internal/facts 1.065s
ok github.com/novox/mesh-controller/internal/identity 4.247s
ok github.com/novox/mesh-controller/internal/inventory 80.325s
ok github.com/novox/mesh-controller/internal/lease 17.709s
ok github.com/novox/mesh-controller/internal/licences 3.921s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.093s
ok github.com/novox/mesh-controller/internal/link 58.475s
ok github.com/novox/mesh-controller/internal/lint 2.176s
ok github.com/novox/mesh-controller/internal/outward 1.089s
ok github.com/novox/mesh-controller/internal/overlay 1.078s
ok github.com/novox/mesh-controller/internal/secrets 1.458s
ok github.com/novox/mesh-controller/internal/store 3.322s
ok github.com/novox/mesh-controller/internal/testbus 1.239s
ok github.com/novox/mesh-controller/internal/token 1.019s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL github.com/novox/mesh-controller/internal/catalogue 5.678s
```
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as build-1791738051633198468 (builds --log build-1791738051633198468).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T16:22:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T16:22:35Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.040s
ok github.com/novox/mesh-controller/cmd/mesh-controller 241.029s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.060s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.067s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.054s
ok github.com/novox/mesh-controller/examples/route-proxy 1.220s
ok github.com/novox/mesh-controller/internal/artifacts 1.094s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.145s
ok github.com/novox/mesh-controller/internal/builder 18.633s
ok github.com/novox/mesh-controller/internal/catalogue 7.695s
ok github.com/novox/mesh-controller/internal/conditions 2.661s
ok github.com/novox/mesh-controller/internal/envfile 1.075s
ok github.com/novox/mesh-controller/internal/facts 1.081s
ok github.com/novox/mesh-controller/internal/identity 4.968s
ok github.com/novox/mesh-controller/internal/inventory 99.425s
ok github.com/novox/mesh-controller/internal/lease 17.728s
ok github.com/novox/mesh-controller/internal/licences 4.484s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.058s
ok github.com/novox/mesh-controller/internal/link 63.950s
ok github.com/novox/mesh-controller/internal/lint 2.422s
ok github.com/novox/mesh-controller/internal/outward 1.092s
ok github.com/novox/mesh-controller/internal/overlay 1.063s
ok github.com/novox/mesh-controller/internal/secrets 1.558s
ok github.com/novox/mesh-controller/internal/store 3.540s
ok github.com/novox/mesh-controller/internal/testbus 1.252s
ok github.com/novox/mesh-controller/internal/token 1.016s
**Merge check** at `0c675bcd`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as `build-1791738051633198468` (`builds --log build-1791738051633198468`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T16:22:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T16:22:35Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/generation_test.go, cmd/mesh-controller/held_back_test.go, cmd/mesh-controller/issue_204_test.go, cmd/mesh-controller/signals_test.go, internal/inventory/sends_test.go, internal/link/generation_test.go and testdata/beside/CAPTURED read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.040s
ok github.com/novox/mesh-controller/cmd/mesh-controller 241.029s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.060s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.067s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.054s
ok github.com/novox/mesh-controller/examples/route-proxy 1.220s
ok github.com/novox/mesh-controller/internal/artifacts 1.094s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.145s
ok github.com/novox/mesh-controller/internal/builder 18.633s
ok github.com/novox/mesh-controller/internal/catalogue 7.695s
ok github.com/novox/mesh-controller/internal/conditions 2.661s
ok github.com/novox/mesh-controller/internal/envfile 1.075s
ok github.com/novox/mesh-controller/internal/facts 1.081s
ok github.com/novox/mesh-controller/internal/identity 4.968s
ok github.com/novox/mesh-controller/internal/inventory 99.425s
ok github.com/novox/mesh-controller/internal/lease 17.728s
ok github.com/novox/mesh-controller/internal/licences 4.484s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.058s
ok github.com/novox/mesh-controller/internal/link 63.950s
ok github.com/novox/mesh-controller/internal/lint 2.422s
ok github.com/novox/mesh-controller/internal/outward 1.092s
ok github.com/novox/mesh-controller/internal/overlay 1.063s
ok github.com/novox/mesh-controller/internal/secrets 1.558s
ok github.com/novox/mesh-controller/internal/store 3.540s
ok github.com/novox/mesh-controller/internal/testbus 1.252s
ok github.com/novox/mesh-controller/internal/token 1.016s
```
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.
after: novox/mesh-host
Fixes the controller half of novox/hq issue 234 (critical): a later declaration left out four assigned modules, and a machine applied it. Decision: issue 234 note of 2026-10-11 (questions 2 and 3). Needs novox/mesh-host#82 first: this pins the node-engine at that PR's head (20d5af9), because the controller validates every declaration with the node-engine's own parser, which must read
generationbefore any machine is sent it. Once #82 merges, the pin moves to its merge, as for issue 361.What changes
assignment_generation, seeded 1. Row triggers onassignmentraise it on insert or delete, and on an update only when the row changed (when (old is distinct from new)). It moves in the same transaction as every assignment change, including one taken by a node's removal or a module's rename. The controller's inventory has no consolidated schema file beside its migrations: a fresh store applies every numbered migration, so 0094 is both.allot, before the composition reads any assignment. Sent asgenerationonly to a machine whose engine's ordered reports sayreads_generation.allot, so the put-back carries the generation as it stands and is never older than what the machine applied. mesh-host#82 still readsput_back; this controller never sends it.facts.go, push's digests) with the generation the machine was last sent.node.sent_generationis written in the same transaction as the digest.declaration_sendin that transaction, under a savepoint: node, sequence, lease epoch, sender (caller, pid, host, build), generation composed from, digest, modules named; newest 200 per machine. If the send's own row cannot be written, the machine's record still commits, the send does not read as failed, and the push saysSEND NOT RECORDEDon stderr and in its output.machine.<node>.older-generation, warning, for an hour): on the send it refused, naming the sender, both generations, the sequence and the modules; or, for a sequence the mesh has no send for, as a row of its own whose sender is said to be unknown.push <node>. Nothing is pushed from the refusal handler: it runs in the receive loop, and a push there would hold the loop and the node's hold for as long as the push takes.plan <node>shows it.statusandnode showfollow after #223 (their files are in it), tracked as an issue.Compatibility
reads_generation, is sent no new key; its bytes are what they were.plan --json,plan --diffand the merge gate compose without an order, so they compose every machine as before.Moved with the pin
The node-engine's main requires a newer mesh-sdk (f047d0a → 33917f9; it only adds the state counter and go/health).
testdata/besidecaptures the SDK's conformance fixtures at that commit; they are unchanged.Tests (written first)
Unit tests (on main they do not compile: no generation, record or
reads_generationexists there): the generation is sent only to a machine that reads one, and no put-back mark; the sender is named; S20 names a sender, an unknown sender and a counter behind (asks for a push); only the counter as it stands counts as behind; S20 in the signals-table walk;TestTheGenerationOnTheWire. Store-backed (skip without MESH_TEST_POSTGRES, run on the build seat): every assignment change raises the generation, an update that changes nothing does not, the counter is raised past a machine's and never lowered, a send is recorded with sender, generation and modules and a refusal is kept on it, a refusal of an unrecorded sequence is kept with an unknown sender and is not the last send, a send row that cannot be written leaves the digest and generation written and returns SendNotRecordedError, reads_generation follows the latest report.gofmt,go vet ./...andgo test ./...pass locally (store-backed tests skipped). Touches no file of #223 or #225.Delivery
novox/mesh-controller@0c675bcdb5aa— delivered since 2026-10-11T17:26:31ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
313efa82mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791711064767274851(builds --log build-1791711064767274851).Merge check at
5dd0e3c0mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791712553933936018(builds --log build-1791712553933936018).Merge check at
5dd0e3c0mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791735240401131074(builds --log build-1791735240401131074).Merge check at
5dd0e3c0mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.03s)Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791737581813168769(builds --log build-1791737581813168769).Merge check at
0c675bcdmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791738051633198468(builds --log build-1791738051633198468).