Since #213 (issue 438) an unanswered merge check is told to push a new commit or look at the build queue. Since mesh-catalog #199 (issue 441) mesh-delivery also says such a line for a delivery held in ready or rejected, whose check already answered once: the build queue is the wrong place to look there, and the step is mesh-delivery.recheck.
stalledLine reads a new held field: the state of the delivery the unanswered line is about, as mesh-delivery says it (companion: mesh-catalog PR on branch fix/451-a-recheck-is-the-step). The controller never reads the state from says or h2.
unansweredWords: for held ready or rejected, the explanation says the delivery's state and the advice is a recheck naming the delivery id (mesh-delivery.recheck with id and why), or a new commit. It is advice, not an action: the controller is not granted the recheck.
No held (no delivery held, or a mesh-delivery from before): the advice of 438, unchanged. Either PR can land first.
Test: TestAnUnansweredMergeCheckOnAReadyOrRejectedDeliveryOffersARecheck fails on main (it is sent to the build queue); go vet and go test -race ./cmd/mesh-controller pass.
Fixes novox/hq issue 451.
Since #213 (issue 438) an unanswered merge check is told to push a new commit or look at the build queue. Since mesh-catalog #199 (issue 441) mesh-delivery also says such a line for a delivery held in ready or rejected, whose check already answered once: the build queue is the wrong place to look there, and the step is `mesh-delivery.recheck`.
- `stalledLine` reads a new `held` field: the state of the delivery the unanswered line is about, as mesh-delivery says it (companion: mesh-catalog PR on branch `fix/451-a-recheck-is-the-step`). The controller never reads the state from `says` or `h2`.
- `unansweredWords`: for `held` ready or rejected, the explanation says the delivery's state and the advice is a recheck naming the delivery id (`mesh-delivery.recheck` with id and why), or a new commit. It is advice, not an action: the controller is not granted the recheck.
- No `held` (no delivery held, or a mesh-delivery from before): the advice of 438, unchanged. Either PR can land first.
Test: `TestAnUnansweredMergeCheckOnAReadyOrRejectedDeliveryOffersARecheck` fails on main (it is sent to the build queue); `go vet` and `go test -race ./cmd/mesh-controller` pass.
That check answered once, so the build queue is the wrong place to look.
mesh-delivery names the delivery's state as data (held); the controller
reads it and never the words. A line without it keeps the advice of 438.
Deliverynovox/mesh-controller@a23b190747d4 — delivered since 2026-10-12T12:22:43Z
Delivery plan — builds mesh-controller, route-proxy → ace, novox; no bus step
tier 0: mesh-controller, route-proxy
ace: receives route-proxy
novox: receives mesh-controller, route-proxy
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
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy is judged on its first machine
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-controller on novox: passed — healthy 3 times over 3m38s
mesh-controller on the rest running it: sent
Transitions
2026-10-12 11:57 (new) → proposed (announced): novox/mesh-controller#254's head announced
2026-10-12 12:06 proposed → checked (checked): the verdict names this commit
2026-10-12 12:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 12:18 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 12:18 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-12 12:22 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@a23b190747d4` — **delivered** since 2026-10-12T12:22:43Z
**Delivery plan** — builds mesh-controller, route-proxy → ace, novox; no bus step
- tier 0: mesh-controller, route-proxy
- ace: receives route-proxy
- novox: receives mesh-controller, route-proxy
- 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
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy is judged on its first machine
**Group** `fix/451-a-recheck-is-the-step`, in order: novox/mesh-controller@a23b190747d4 → novox/mesh-catalog@befe451f6d5d
- novox/mesh-controller@a23b190747d4 before novox/mesh-catalog@befe451f6d5d: version skew
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m38s
- mesh-controller on the rest running it: sent
**Transitions**
- 2026-10-12 11:57 (new) → proposed (announced): novox/mesh-controller#254's head announced
- 2026-10-12 12:06 proposed → checked (checked): the verdict names this commit
- 2026-10-12 12:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 12:18 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 12:18 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-12 12:22 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/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)
mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
read by no module's build: cmd/mesh-controller/plain_words_test.go
Run by the build seat on ace as build-1791805749843379386 (builds --log build-1791805749843379386).
--- the gate: mesh-controller
mesh-controller: ok, 57 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-12T11:40:33Z 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-12T11:40:33Z
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 1 module(s) in 1 tier(s): mesh-controller
notes:
- cmd/mesh-controller/plain_words_test.go 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.042s
ok github.com/novox/mesh-controller/cmd/mesh-controller 239.817s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.131s
ok github.com/novox/mesh-controller/internal/artifacts 1.077s
? github.com/novox/mesh-controller/internal/beside [no test files]
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)
genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
genesis_template_test.go:48: the installer's user list lets the controller publish [mesh.seat.mesh-delivery.tool.groups], which it does not derive
FAIL
FAIL github.com/novox/mesh-controller/internal/broker 3.186s
ok github.com/novox/mesh-controller/internal/builder 16.094s
ok github.com/novox/mesh-controller/internal/catalogue 7.891s
ok github.com/novox/mesh-controller/internal/conditions 2.911s
ok github.com/novox/mesh-controller/internal/envfile 1.074s
ok github.com/novox/mesh-controller/internal/facts 1.063s
ok github.com/novox/mesh-controller/internal/identity 4.742s
ok github.com/novox/mesh-controller/internal/inventory 92.845s
ok github.com/novox/mesh-controller/internal/lease 17.637s
ok github.com/novox/mesh-controller/internal/licences 4.314s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.058s
ok github.com/novox/mesh-controller/internal/link 60.049s
ok github.com/novox/mesh-controller/internal/lint 2.394s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.095s
ok github.com/novox/mesh-controller/internal/secrets 1.513s
ok github.com/novox/mesh-controller/internal/store 3.536s
ok github.com/novox/mesh-controller/internal/testbus 1.224s
ok github.com/novox/mesh-controller/internal/token 1.026s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)
genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
genesis_template_test.go:48: the installer's user list lets the controller publish [mesh.seat.mesh-delivery.tool.groups], which it does not derive
FAIL github.com/novox/mesh-controller/internal/broker 3.186s
**Merge check** at `e737e13b`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
- read by no module's build: cmd/mesh-controller/plain_words_test.go
Run by the build seat on ace as `build-1791805749843379386` (`builds --log build-1791805749843379386`).
```
--- the gate: mesh-controller
mesh-controller: ok, 57 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-12T11:40:33Z 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-12T11:40:33Z
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 1 module(s) in 1 tier(s): mesh-controller
notes:
- cmd/mesh-controller/plain_words_test.go 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.042s
ok github.com/novox/mesh-controller/cmd/mesh-controller 239.817s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.131s
ok github.com/novox/mesh-controller/internal/artifacts 1.077s
? github.com/novox/mesh-controller/internal/beside [no test files]
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)
genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
genesis_template_test.go:48: the installer's user list lets the controller publish [mesh.seat.mesh-delivery.tool.groups], which it does not derive
FAIL
FAIL github.com/novox/mesh-controller/internal/broker 3.186s
ok github.com/novox/mesh-controller/internal/builder 16.094s
ok github.com/novox/mesh-controller/internal/catalogue 7.891s
ok github.com/novox/mesh-controller/internal/conditions 2.911s
ok github.com/novox/mesh-controller/internal/envfile 1.074s
ok github.com/novox/mesh-controller/internal/facts 1.063s
ok github.com/novox/mesh-controller/internal/identity 4.742s
ok github.com/novox/mesh-controller/internal/inventory 92.845s
ok github.com/novox/mesh-controller/internal/lease 17.637s
ok github.com/novox/mesh-controller/internal/licences 4.314s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.058s
ok github.com/novox/mesh-controller/internal/link 60.049s
ok github.com/novox/mesh-controller/internal/lint 2.394s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.095s
ok github.com/novox/mesh-controller/internal/secrets 1.513s
ok github.com/novox/mesh-controller/internal/store 3.536s
ok github.com/novox/mesh-controller/internal/testbus 1.224s
ok github.com/novox/mesh-controller/internal/token 1.026s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)
genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
genesis_template_test.go:48: the installer's user list lets the controller publish [mesh.seat.mesh-delivery.tool.groups], which it does not derive
FAIL github.com/novox/mesh-controller/internal/broker 3.186s
```
mesh/merge-gate pass: builds mesh-controller, route-proxy → ace, novox; no bus step; every machine composes with the change as it did without (4 of 4 compo…
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller, route-proxy)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-controller, route-proxy → ace, novox; no bus step
tier 0: mesh-controller, route-proxy
ace: receives route-proxy
novox: receives mesh-controller, route-proxy
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
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy is judged on its first machine
Run by the build seat on ace as build-1791806255864981897 (builds --log build-1791806255864981897).
--- the gate: mesh-controller, route-proxy
mesh-controller: ok, 57 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-12T11:52:38Z 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-12T11:52:38Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.044s
ok github.com/novox/mesh-controller/cmd/mesh-controller 247.746s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.015s
ok github.com/novox/mesh-controller/examples/route-proxy 1.115s
ok github.com/novox/mesh-controller/internal/artifacts 1.047s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.139s
ok github.com/novox/mesh-controller/internal/builder 15.963s
ok github.com/novox/mesh-controller/internal/catalogue 7.708s
ok github.com/novox/mesh-controller/internal/conditions 2.678s
ok github.com/novox/mesh-controller/internal/envfile 1.075s
ok github.com/novox/mesh-controller/internal/facts 1.080s
ok github.com/novox/mesh-controller/internal/identity 4.610s
ok github.com/novox/mesh-controller/internal/inventory 91.895s
ok github.com/novox/mesh-controller/internal/lease 17.688s
ok github.com/novox/mesh-controller/internal/licences 4.196s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.041s
ok github.com/novox/mesh-controller/internal/link 60.923s
ok github.com/novox/mesh-controller/internal/lint 2.336s
ok github.com/novox/mesh-controller/internal/outward 1.072s
ok github.com/novox/mesh-controller/internal/overlay 1.058s
ok github.com/novox/mesh-controller/internal/secrets 1.448s
ok github.com/novox/mesh-controller/internal/store 3.446s
ok github.com/novox/mesh-controller/internal/testbus 1.204s
ok github.com/novox/mesh-controller/internal/token 1.023s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.41s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.42s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.44s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.39s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.44s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.31s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.45s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.43s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.42s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.42s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.27s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.30s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.28s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.27s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
**Merge check** at `a23b1907`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-controller, route-proxy → ace, novox; no bus step
- tier 0: mesh-controller, route-proxy
- ace: receives route-proxy
- novox: receives mesh-controller, route-proxy
- 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
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy is judged on its first machine
Run by the build seat on ace as `build-1791806255864981897` (`builds --log build-1791806255864981897`).
```
--- the gate: mesh-controller, route-proxy
mesh-controller: ok, 57 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-12T11:52:38Z 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-12T11:52:38Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.044s
ok github.com/novox/mesh-controller/cmd/mesh-controller 247.746s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.015s
ok github.com/novox/mesh-controller/examples/route-proxy 1.115s
ok github.com/novox/mesh-controller/internal/artifacts 1.047s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.139s
ok github.com/novox/mesh-controller/internal/builder 15.963s
ok github.com/novox/mesh-controller/internal/catalogue 7.708s
ok github.com/novox/mesh-controller/internal/conditions 2.678s
ok github.com/novox/mesh-controller/internal/envfile 1.075s
ok github.com/novox/mesh-controller/internal/facts 1.080s
ok github.com/novox/mesh-controller/internal/identity 4.610s
ok github.com/novox/mesh-controller/internal/inventory 91.895s
ok github.com/novox/mesh-controller/internal/lease 17.688s
ok github.com/novox/mesh-controller/internal/licences 4.196s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.041s
ok github.com/novox/mesh-controller/internal/link 60.923s
ok github.com/novox/mesh-controller/internal/lint 2.336s
ok github.com/novox/mesh-controller/internal/outward 1.072s
ok github.com/novox/mesh-controller/internal/overlay 1.058s
ok github.com/novox/mesh-controller/internal/secrets 1.448s
ok github.com/novox/mesh-controller/internal/store 3.446s
ok github.com/novox/mesh-controller/internal/testbus 1.204s
ok github.com/novox/mesh-controller/internal/token 1.023s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.41s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.42s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.44s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.39s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.44s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.31s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.45s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.43s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.42s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.42s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.27s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.30s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.28s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.27s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
```
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.
Fixes novox/hq issue 451.
Since #213 (issue 438) an unanswered merge check is told to push a new commit or look at the build queue. Since mesh-catalog #199 (issue 441) mesh-delivery also says such a line for a delivery held in ready or rejected, whose check already answered once: the build queue is the wrong place to look there, and the step is
mesh-delivery.recheck.stalledLinereads a newheldfield: the state of the delivery the unanswered line is about, as mesh-delivery says it (companion: mesh-catalog PR on branchfix/451-a-recheck-is-the-step). The controller never reads the state fromsaysorh2.unansweredWords: forheldready or rejected, the explanation says the delivery's state and the advice is a recheck naming the delivery id (mesh-delivery.recheckwith id and why), or a new commit. It is advice, not an action: the controller is not granted the recheck.held(no delivery held, or a mesh-delivery from before): the advice of 438, unchanged. Either PR can land first.Test:
TestAnUnansweredMergeCheckOnAReadyOrRejectedDeliveryOffersARecheckfails on main (it is sent to the build queue);go vetandgo test -race ./cmd/mesh-controllerpass.Delivery
novox/mesh-controller@a23b190747d4— delivered since 2026-10-12T12:22:43ZDelivery plan — builds mesh-controller, route-proxy → ace, novox; no bus step
Group
fix/451-a-recheck-is-the-step, in order: novox/mesh-controller@a23b190747 → novox/mesh-catalog@befe451f6dMachines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
e737e13bmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)Delivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1791805749843379386(builds --log build-1791805749843379386).Merge check at
a23b1907mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller, route-proxy → ace, novox; no bus step
Run by the build seat on ace as
build-1791806255864981897(builds --log build-1791806255864981897).