Fixes novox/hq issue 582 (a core delivery's apply phase ends at the next walk's send).
Cause, proven. The apply duration is written on the controller from the machine's report (internal/link/enrolment.go → RecordApplyDuration), starting at node.sent_at, set per machine at its own send. The walk records SentAt for the rest only after sendRollout returned for every machine (cmd/mesh-controller/release_plan.go, the loop after sentNow). FirstAppliedAfter (internal/inventory/walkphases.go) took the first duration started no earlier than 2 s before that record, so a machine sent first in a 20-28 s send-rest was missed and the phase ended at a later send. Live: plan-1791826579427234545 sent g14 sequence 647 and shanks 649; the next walk (plan-1791827489963890447) sent them 648 and 650, so no other send came between, and the first walk's apply ended at 17:55:06.6, 3 s after the next walk's send-rest.
Change.
SentDeclaration keeps at, the machine's own send time (node.sent_at), read by SentTo; the walk's rest and the gate's sent carry it.
FirstAppliedAfter(node, send, walkSent) reads candidate rows and FirstReportOf picks: with at kept, the duration of that very send and digest; with only the digest kept (walks from before), the first duration about that declaration within 5 min before the walk's record; with neither, the old 2 s rule.
A report of a later send is never this walk's: such a machine is waiting, then silent past 15 min, never moving the end. A machine sent twice by one walk is heard by its later send of the same walk.
delivery-walks shows phases.rest: per machine its send time, sequence, report time, outcome and state (ADR 0282 decision 6).
Tests.TestTheApplyPhaseEndsAtEachMachinesOwnReport (20 s send-rest, the first machine reporting 5 s after its own send) fails under main's selection rule (ends 17:54:49, at the next walk's send) and passes here. Also: an older walk read by its digest, a later send's report never taken, a machine sent twice by one walk. Store test TestAWalksRestIsReadFromEachMachinesOwnSend added to testdata/store-tests. gofmt, go vet, go test -race on internal/inventory and cmd/mesh-controller pass.
The node-engine's report carries no sequence into the apply duration row, so matching is by the controller's own send time and digest; nothing is needed from mesh-host.
Walk-phase durations already kept are not recomputed: delivery times kept before this change stay as they were.
Fixes novox/hq issue 582 (a core delivery's apply phase ends at the next walk's send).
**Cause, proven.** The `apply` duration is written on the controller from the machine's report (`internal/link/enrolment.go` → `RecordApplyDuration`), starting at `node.sent_at`, set per machine at its own send. The walk records `SentAt` for the rest only after `sendRollout` returned for every machine (`cmd/mesh-controller/release_plan.go`, the loop after `sentNow`). `FirstAppliedAfter` (`internal/inventory/walkphases.go`) took the first duration started no earlier than 2 s before that record, so a machine sent first in a 20-28 s send-rest was missed and the phase ended at a later send. Live: plan-1791826579427234545 sent g14 sequence 647 and shanks 649; the next walk (plan-1791827489963890447) sent them 648 and 650, so no other send came between, and the first walk's apply ended at 17:55:06.6, 3 s after the next walk's send-rest.
**Change.**
- `SentDeclaration` keeps `at`, the machine's own send time (`node.sent_at`), read by `SentTo`; the walk's `rest` and the gate's `sent` carry it.
- `FirstAppliedAfter(node, send, walkSent)` reads candidate rows and `FirstReportOf` picks: with `at` kept, the duration of that very send and digest; with only the digest kept (walks from before), the first duration about that declaration within 5 min before the walk's record; with neither, the old 2 s rule.
- A report of a later send is never this walk's: such a machine is waiting, then silent past 15 min, never moving the end. A machine sent twice by one walk is heard by its later send of the same walk.
- `delivery-walks` shows `phases.rest`: per machine its send time, sequence, report time, outcome and state (ADR 0282 decision 6).
**Tests.** `TestTheApplyPhaseEndsAtEachMachinesOwnReport` (20 s send-rest, the first machine reporting 5 s after its own send) fails under main's selection rule (ends 17:54:49, at the next walk's send) and passes here. Also: an older walk read by its digest, a later send's report never taken, a machine sent twice by one walk. Store test `TestAWalksRestIsReadFromEachMachinesOwnSend` added to testdata/store-tests. gofmt, go vet, go test -race on internal/inventory and cmd/mesh-controller pass.
The node-engine's report carries no sequence into the `apply` duration row, so matching is by the controller's own send time and digest; nothing is needed from mesh-host.
Walk-phase durations already kept are not recomputed: delivery times kept before this change stay as they were.
The walk records its send to the rest only after every machine was sent,
which takes 20-28 s, so the machine sent first fell outside the 2 s slack,
its report was missed and the phase ended at the next walk's send to it.
Keep each machine's own send time with what it was sent, match its apply
duration by that send and digest, and show each machine's report in the
walk's phases (ADR 0282 decision 6).
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
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 build-agent, route-proxy is judged on its first machine
Machines
mesh-controller on novox: passed — healthy 3 times over 3m40s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 1 times over 40s
build-agent on the rest running it: sent
Transitions
2026-10-12 21:19 (new) → proposed (announced): novox/mesh-controller#278's head announced
2026-10-12 21:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-12 21:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 21:36 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 21:36 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 21:43 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@e727589e483b` — **delivered** since 2026-10-12T21:43:58Z
**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
- 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 build-agent, route-proxy is judged on its first machine
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m40s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 1 times over 40s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-12 21:19 (new) → proposed (announced): novox/mesh-controller#278's head announced
- 2026-10-12 21:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-12 21:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 21:36 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 21:36 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 21:43 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
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 build-agent, route-proxy is judged on its first machine
Run by the build seat on shanks as build-1791839944442560054 (builds --log build-1791839944442560054).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 58 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-12T21:18:25Z 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-12T21:18:25Z
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.039s
ok github.com/novox/mesh-controller/cmd/mesh-controller 282.010s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.047s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.071s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.067s
ok github.com/novox/mesh-controller/examples/route-proxy 1.227s
ok github.com/novox/mesh-controller/internal/artifacts 1.110s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.475s
ok github.com/novox/mesh-controller/internal/builder 40.669s
ok github.com/novox/mesh-controller/internal/catalogue 8.892s
ok github.com/novox/mesh-controller/internal/conditions 2.728s
ok github.com/novox/mesh-controller/internal/envfile 1.059s
ok github.com/novox/mesh-controller/internal/facts 1.060s
ok github.com/novox/mesh-controller/internal/identity 5.079s
ok github.com/novox/mesh-controller/internal/inventory 103.999s
ok github.com/novox/mesh-controller/internal/lease 17.639s
ok github.com/novox/mesh-controller/internal/licences 4.537s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.057s
ok github.com/novox/mesh-controller/internal/link 62.725s
ok github.com/novox/mesh-controller/internal/lint 2.496s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.087s
ok github.com/novox/mesh-controller/internal/secrets 1.561s
ok github.com/novox/mesh-controller/internal/store 3.606s
ok github.com/novox/mesh-controller/internal/testbus 1.265s
ok github.com/novox/mesh-controller/internal/token 1.015s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.49s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.49s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.42s)
./cmd/mesh-controller --- PASS: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (4.39s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.47s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.33s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.43s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.44s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.47s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.48s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.44s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.43s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.43s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.42s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.45s)
./cmd/mesh-controller --- PASS: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.51s)
./cmd/mesh-controller --- PASS: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.51s)
./cmd/mesh-controller --- PASS: TestReplay201 (0.38s)
./cmd/mesh-controller --- PASS: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.62s)
./cmd/mesh-controller --- PASS: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.48s)
./cmd/mesh-controller --- PASS: TestReplay401 (0.53s)
./cmd/mesh-controller --- PASS: TestReplay201ThePlansSend (0.48s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.28s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.27s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.27s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.29s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.28s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.27s)
Out of date when it landed: out of date: judged against trunk 2f157148c6, the trunk is now 961f2e82ea1c; judged again on a recheck or when it is merged
**Merge check** at `e727589e`
Judged: head `e727589e483b` merged into trunk `2f157148c6c8`; read beside it: mesh-catalog `9c9a76d220f8`, mesh-controller-main `2f157148c6c8`, mesh-host `8e95c1d9ed2d`, mesh-tools `954e1a53eef9`
- `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
- 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 build-agent, route-proxy is judged on its first machine
Run by the build seat on shanks as `build-1791839944442560054` (`builds --log build-1791839944442560054`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 58 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-12T21:18:25Z 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-12T21:18:25Z
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.039s
ok github.com/novox/mesh-controller/cmd/mesh-controller 282.010s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.047s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.071s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.067s
ok github.com/novox/mesh-controller/examples/route-proxy 1.227s
ok github.com/novox/mesh-controller/internal/artifacts 1.110s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.475s
ok github.com/novox/mesh-controller/internal/builder 40.669s
ok github.com/novox/mesh-controller/internal/catalogue 8.892s
ok github.com/novox/mesh-controller/internal/conditions 2.728s
ok github.com/novox/mesh-controller/internal/envfile 1.059s
ok github.com/novox/mesh-controller/internal/facts 1.060s
ok github.com/novox/mesh-controller/internal/identity 5.079s
ok github.com/novox/mesh-controller/internal/inventory 103.999s
ok github.com/novox/mesh-controller/internal/lease 17.639s
ok github.com/novox/mesh-controller/internal/licences 4.537s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.057s
ok github.com/novox/mesh-controller/internal/link 62.725s
ok github.com/novox/mesh-controller/internal/lint 2.496s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.087s
ok github.com/novox/mesh-controller/internal/secrets 1.561s
ok github.com/novox/mesh-controller/internal/store 3.606s
ok github.com/novox/mesh-controller/internal/testbus 1.265s
ok github.com/novox/mesh-controller/internal/token 1.015s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.49s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.49s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.42s)
./cmd/mesh-controller --- PASS: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (4.39s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.47s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.33s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.43s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.44s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.47s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.48s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.44s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.43s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.43s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.42s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.45s)
./cmd/mesh-controller --- PASS: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.51s)
./cmd/mesh-controller --- PASS: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.51s)
./cmd/mesh-controller --- PASS: TestReplay201 (0.38s)
./cmd/mesh-controller --- PASS: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.62s)
./cmd/mesh-controller --- PASS: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.48s)
./cmd/mesh-controller --- PASS: TestReplay401 (0.53s)
./cmd/mesh-controller --- PASS: TestReplay201ThePlansSend (0.48s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.28s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.27s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.27s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.29s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.28s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.27s)
```
**Out of date when it landed**: out of date: judged against trunk 2f157148c6c8, the trunk is now 961f2e82ea1c; judged again on a recheck or when it is merged
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
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 build-agent, route-proxy is judged on its first machine
Run by the build seat on shanks as build-1791840498252739070 (builds --log build-1791840498252739070).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 58 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-12T21:22:43Z 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-12T21:22:43Z
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.039s
ok github.com/novox/mesh-controller/cmd/mesh-controller 308.687s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.062s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.034s
ok github.com/novox/mesh-controller/examples/route-proxy 1.244s
ok github.com/novox/mesh-controller/internal/artifacts 1.096s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.786s
ok github.com/novox/mesh-controller/internal/builder 52.861s
ok github.com/novox/mesh-controller/internal/catalogue 9.536s
ok github.com/novox/mesh-controller/internal/conditions 2.725s
ok github.com/novox/mesh-controller/internal/envfile 1.069s
ok github.com/novox/mesh-controller/internal/facts 1.073s
ok github.com/novox/mesh-controller/internal/identity 5.433s
ok github.com/novox/mesh-controller/internal/inventory 120.707s
ok github.com/novox/mesh-controller/internal/lease 17.657s
ok github.com/novox/mesh-controller/internal/licences 4.914s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.046s
ok github.com/novox/mesh-controller/internal/link 79.321s
ok github.com/novox/mesh-controller/internal/lint 2.544s
ok github.com/novox/mesh-controller/internal/outward 1.095s
ok github.com/novox/mesh-controller/internal/overlay 1.087s
ok github.com/novox/mesh-controller/internal/secrets 1.575s
ok github.com/novox/mesh-controller/internal/store 3.603s
ok github.com/novox/mesh-controller/internal/testbus 1.282s
ok github.com/novox/mesh-controller/internal/token 1.017s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.45s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.44s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.45s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.39s)
./cmd/mesh-controller --- PASS: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (4.40s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.33s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.59s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.45s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.53s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.45s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.48s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.44s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.42s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.43s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.42s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.46s)
./cmd/mesh-controller --- PASS: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.52s)
./cmd/mesh-controller --- PASS: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.49s)
./cmd/mesh-controller --- PASS: TestReplay201 (0.41s)
./cmd/mesh-controller --- PASS: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.38s)
./cmd/mesh-controller --- PASS: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.39s)
./cmd/mesh-controller --- PASS: TestReplay401 (0.53s)
./cmd/mesh-controller --- PASS: TestReplay201ThePlansSend (0.48s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.29s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.30s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.28s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.28s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.28s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.27s)
**Merge check** at `e727589e`
Judged: head `e727589e483b` merged into trunk `961f2e82ea1c`; read beside it: mesh-catalog `9c9a76d220f8`, mesh-controller-main `961f2e82ea1c`, mesh-host `8e95c1d9ed2d`, mesh-tools `954e1a53eef9`
- `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
- 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 build-agent, route-proxy is judged on its first machine
Run by the build seat on shanks as `build-1791840498252739070` (`builds --log build-1791840498252739070`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 58 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-12T21:22:43Z 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-12T21:22:43Z
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.039s
ok github.com/novox/mesh-controller/cmd/mesh-controller 308.687s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.062s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.034s
ok github.com/novox/mesh-controller/examples/route-proxy 1.244s
ok github.com/novox/mesh-controller/internal/artifacts 1.096s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.786s
ok github.com/novox/mesh-controller/internal/builder 52.861s
ok github.com/novox/mesh-controller/internal/catalogue 9.536s
ok github.com/novox/mesh-controller/internal/conditions 2.725s
ok github.com/novox/mesh-controller/internal/envfile 1.069s
ok github.com/novox/mesh-controller/internal/facts 1.073s
ok github.com/novox/mesh-controller/internal/identity 5.433s
ok github.com/novox/mesh-controller/internal/inventory 120.707s
ok github.com/novox/mesh-controller/internal/lease 17.657s
ok github.com/novox/mesh-controller/internal/licences 4.914s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.046s
ok github.com/novox/mesh-controller/internal/link 79.321s
ok github.com/novox/mesh-controller/internal/lint 2.544s
ok github.com/novox/mesh-controller/internal/outward 1.095s
ok github.com/novox/mesh-controller/internal/overlay 1.087s
ok github.com/novox/mesh-controller/internal/secrets 1.575s
ok github.com/novox/mesh-controller/internal/store 3.603s
ok github.com/novox/mesh-controller/internal/testbus 1.282s
ok github.com/novox/mesh-controller/internal/token 1.017s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.45s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.44s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.45s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.39s)
./cmd/mesh-controller --- PASS: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (4.40s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.33s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.59s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.45s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.53s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.45s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.48s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.44s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.42s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.43s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.42s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.46s)
./cmd/mesh-controller --- PASS: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.52s)
./cmd/mesh-controller --- PASS: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.49s)
./cmd/mesh-controller --- PASS: TestReplay201 (0.41s)
./cmd/mesh-controller --- PASS: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.38s)
./cmd/mesh-controller --- PASS: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.39s)
./cmd/mesh-controller --- PASS: TestReplay401 (0.53s)
./cmd/mesh-controller --- PASS: TestReplay201ThePlansSend (0.48s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.29s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.30s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.28s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.28s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.28s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.27s)
```
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 582 (a core delivery's apply phase ends at the next walk's send).
Cause, proven. The
applyduration is written on the controller from the machine's report (internal/link/enrolment.go→RecordApplyDuration), starting atnode.sent_at, set per machine at its own send. The walk recordsSentAtfor the rest only aftersendRolloutreturned for every machine (cmd/mesh-controller/release_plan.go, the loop aftersentNow).FirstAppliedAfter(internal/inventory/walkphases.go) took the first duration started no earlier than 2 s before that record, so a machine sent first in a 20-28 s send-rest was missed and the phase ended at a later send. Live: plan-1791826579427234545 sent g14 sequence 647 and shanks 649; the next walk (plan-1791827489963890447) sent them 648 and 650, so no other send came between, and the first walk's apply ended at 17:55:06.6, 3 s after the next walk's send-rest.Change.
SentDeclarationkeepsat, the machine's own send time (node.sent_at), read bySentTo; the walk'srestand the gate'ssentcarry it.FirstAppliedAfter(node, send, walkSent)reads candidate rows andFirstReportOfpicks: withatkept, the duration of that very send and digest; with only the digest kept (walks from before), the first duration about that declaration within 5 min before the walk's record; with neither, the old 2 s rule.delivery-walksshowsphases.rest: per machine its send time, sequence, report time, outcome and state (ADR 0282 decision 6).Tests.
TestTheApplyPhaseEndsAtEachMachinesOwnReport(20 s send-rest, the first machine reporting 5 s after its own send) fails under main's selection rule (ends 17:54:49, at the next walk's send) and passes here. Also: an older walk read by its digest, a later send's report never taken, a machine sent twice by one walk. Store testTestAWalksRestIsReadFromEachMachinesOwnSendadded to testdata/store-tests. gofmt, go vet, go test -race on internal/inventory and cmd/mesh-controller pass.The node-engine's report carries no sequence into the
applyduration row, so matching is by the controller's own send time and digest; nothing is needed from mesh-host.Walk-phase durations already kept are not recomputed: delivery times kept before this change stay as they were.
Delivery
novox/mesh-controller@e727589e483b— delivered since 2026-10-12T21:43:58ZDelivery 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
e727589eJudged: head
e727589e483bmerged into trunk2f157148c6c8; read beside it: mesh-catalog9c9a76d220f8, mesh-controller-main2f157148c6c8, mesh-host8e95c1d9ed2d, mesh-tools954e1a53eef9mesh/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-1791839944442560054(builds --log build-1791839944442560054).Out of date when it landed: out of date: judged against trunk
2f157148c6, the trunk is now 961f2e82ea1c; judged again on a recheck or when it is mergedMerge check at
e727589eJudged: head
e727589e483bmerged into trunk961f2e82ea1c; read beside it: mesh-catalog9c9a76d220f8, mesh-controller-main961f2e82ea1c, mesh-host8e95c1d9ed2d, mesh-tools954e1a53eef9mesh/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-1791840498252739070(builds --log build-1791840498252739070).