Fixes novox/hq issue 485 (status and node show do not say what a machine was last sent, by whom and from which generation).
The send record of issue 234 (#227, declaration_send) can be read only through the controller's verbs now: issue 506 was closed because the store's reader may not read the controller's tables. Until now only plan <node> said the last send.
What changes
inventory.LastSends reads every machine's last recorded send in one query. LastSend now carries the machine's answer too (Send.Answer: applied, failed or refused, the refusal's words, and when). A report counts as the send's answer only when it names the send's digest and arrived after the send, so a report about an earlier send is never taken for this one's answer.
status prints one line per machine: laptop 2026-10-11 18:40 by a one-shot push by jochen at a shell on anchor, generation 40 — applied. A machine with no recorded send says no send recorded. If the record cannot be read, status says so and does not call the mesh well.
status --json carries lastSent: node, sequence, sentAt, sender, epoch, generation, digest, modules, answer, refused, failed, answeredAt, refusedForGeneration and appliedGeneration. lastSentUnread says why the record could not be read.
node show <n> and plan <n> print the last send in full: sequence and time, sender, lease epoch, generation, modules, and the machine's answer, with a refusal in the machine's own words.
Not changed: plan --json. It prints the exact bytes a push would send, through one marshaller, so the output cannot show a declaration other than the one sent. Adding the last send there would break that. The same fields are in status --json, which the status seat verb answers.
Tests (cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go). All of them fail to build on main, because lastSendLines, answers.lastSent, Send.Answer and LastSends do not exist there. The four pure tests pass. Two store tests are listed in testdata/store-tests: TestTheLastSendSaysWhatTheMachineAnswered and TestNodeShowAndStatusReadTheLastSendFromTheStore. They skipped locally (no database was used), so the merge check must prove them. Ran go vet and go test on ./internal/inventory and ./cmd/mesh-controller. The files of open #232 are not touched.
Fixes novox/hq issue 485 (status and node show do not say what a machine was last sent, by whom and from which generation).
The send record of issue 234 (#227, `declaration_send`) can be read only through the controller's verbs now: issue 506 was closed because the store's reader may not read the controller's tables. Until now only `plan <node>` said the last send.
**What changes**
- `inventory.LastSends` reads every machine's last recorded send in one query. `LastSend` now carries the machine's answer too (`Send.Answer`: applied, failed or refused, the refusal's words, and when). A report counts as the send's answer only when it names the send's digest and arrived after the send, so a report about an earlier send is never taken for this one's answer.
- `status` prints one line per machine: `laptop 2026-10-11 18:40 by a one-shot push by jochen at a shell on anchor, generation 40 — applied`. A machine with no recorded send says `no send recorded`. If the record cannot be read, status says so and does not call the mesh well.
- `status --json` carries `lastSent`: node, sequence, sentAt, sender, epoch, generation, digest, modules, answer, refused, failed, answeredAt, refusedForGeneration and appliedGeneration. `lastSentUnread` says why the record could not be read.
- `node show <n>` and `plan <n>` print the last send in full: sequence and time, sender, lease epoch, generation, modules, and the machine's answer, with a refusal in the machine's own words.
**Not changed: `plan --json`.** It prints the exact bytes a push would send, through one marshaller, so the output cannot show a declaration other than the one sent. Adding the last send there would break that. The same fields are in `status --json`, which the `status` seat verb answers.
**Tests** (`cmd/mesh-controller/last_send_test.go`, `internal/inventory/sends_test.go`). All of them fail to build on main, because `lastSendLines`, `answers.lastSent`, `Send.Answer` and `LastSends` do not exist there. The four pure tests pass. Two store tests are listed in `testdata/store-tests`: `TestTheLastSendSaysWhatTheMachineAnswered` and `TestNodeShowAndStatusReadTheLastSendFromTheStore`. They skipped locally (no database was used), so the merge check must prove them. Ran `go vet` and `go test` on `./internal/inventory` and `./cmd/mesh-controller`. The files of open #232 are not touched.
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
The send record of issue 234 is now readable only through the controller's
verbs (issue 506), and only plan said it. status says per machine when it was
last sent a declaration, by whom, from which generation and what it answered;
node show says it in full with the refusal's words. A machine's answer is read
from its report only when that report is about the send and came after it.
Deliverynovox/mesh-controller@e2801773c300 — delivered since 2026-10-11T19:17:32Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent 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 is judged on its first machine
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 3m24s
build-agent on the rest running it: sent
Transitions
2026-10-11 18:45 (new) → proposed (announced): novox/mesh-controller#234's head announced
2026-10-11 18:51 proposed → checked (checked): the verdict names this commit
2026-10-11 18:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 19:07 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 19:07 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 19:17 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@e2801773c300` — **delivered** since 2026-10-11T19:17:32Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent 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 is judged on its first machine
**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 3m24s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-11 18:45 (new) → proposed (announced): novox/mesh-controller#234's head announced
- 2026-10-11 18:51 proposed → checked (checked): the verdict names this commit
- 2026-10-11 18:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 19:07 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 19:07 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 19:17 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: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
A periodic report about an identical earlier send names the same digest and
can arrive after a later send the machine never received, so the digest and
the time read it as applied. The digest-and-time rule stays for engines that
report no order. Tests now hold the digest condition and the sequence one.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent 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 is judged on its first machine
read by no module's build: cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go, testdata/store-tests
Run by the build seat on novox as build-1791744072332917245 (builds --log build-1791744072332917245).
--- the gate: build-agent, mesh-controller
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-11T18:32:22Z 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-11T18:32:22Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go and testdata/store-tests 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.064s
ok github.com/novox/mesh-controller/cmd/mesh-controller 289.244s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/route-proxy 1.141s
ok github.com/novox/mesh-controller/internal/artifacts 1.060s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.236s
ok github.com/novox/mesh-controller/internal/builder 20.122s
ok github.com/novox/mesh-controller/internal/catalogue 8.089s
ok github.com/novox/mesh-controller/internal/conditions 2.557s
ok github.com/novox/mesh-controller/internal/envfile 1.028s
ok github.com/novox/mesh-controller/internal/facts 1.034s
ok github.com/novox/mesh-controller/internal/identity 14.103s
ok github.com/novox/mesh-controller/internal/inventory 117.145s
ok github.com/novox/mesh-controller/internal/lease 17.868s
ok github.com/novox/mesh-controller/internal/licences 13.395s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.020s
ok github.com/novox/mesh-controller/internal/link 69.131s
ok github.com/novox/mesh-controller/internal/lint 2.480s
ok github.com/novox/mesh-controller/internal/outward 1.044s
ok github.com/novox/mesh-controller/internal/overlay 1.034s
ok github.com/novox/mesh-controller/internal/secrets 1.493s
ok github.com/novox/mesh-controller/internal/store 9.020s
ok github.com/novox/mesh-controller/internal/testbus 1.238s
ok github.com/novox/mesh-controller/internal/token 1.045s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.58s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.29s)
**Merge check** at `fae6bd0a`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent 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 is judged on its first machine
- read by no module's build: cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go, testdata/store-tests
Run by the build seat on novox as `build-1791744072332917245` (`builds --log build-1791744072332917245`).
```
--- the gate: build-agent, mesh-controller
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-11T18:32:22Z 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-11T18:32:22Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go and testdata/store-tests 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.064s
ok github.com/novox/mesh-controller/cmd/mesh-controller 289.244s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/route-proxy 1.141s
ok github.com/novox/mesh-controller/internal/artifacts 1.060s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.236s
ok github.com/novox/mesh-controller/internal/builder 20.122s
ok github.com/novox/mesh-controller/internal/catalogue 8.089s
ok github.com/novox/mesh-controller/internal/conditions 2.557s
ok github.com/novox/mesh-controller/internal/envfile 1.028s
ok github.com/novox/mesh-controller/internal/facts 1.034s
ok github.com/novox/mesh-controller/internal/identity 14.103s
ok github.com/novox/mesh-controller/internal/inventory 117.145s
ok github.com/novox/mesh-controller/internal/lease 17.868s
ok github.com/novox/mesh-controller/internal/licences 13.395s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.020s
ok github.com/novox/mesh-controller/internal/link 69.131s
ok github.com/novox/mesh-controller/internal/lint 2.480s
ok github.com/novox/mesh-controller/internal/outward 1.044s
ok github.com/novox/mesh-controller/internal/overlay 1.034s
ok github.com/novox/mesh-controller/internal/secrets 1.493s
ok github.com/novox/mesh-controller/internal/store 9.020s
ok github.com/novox/mesh-controller/internal/testbus 1.238s
ok github.com/novox/mesh-controller/internal/token 1.045s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.58s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.29s)
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent 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 is judged on its first machine
read by no module's build: cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go, testdata/store-tests
Run by the build seat on shanks as build-1791744316991075303 (builds --log build-1791744316991075303).
--- the gate: build-agent, mesh-controller
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-11T18:32:22Z 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-11T18:32:22Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go and testdata/store-tests 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 241.160s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.040s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.047s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.030s
ok github.com/novox/mesh-controller/examples/route-proxy 1.202s
ok github.com/novox/mesh-controller/internal/artifacts 1.079s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.158s
ok github.com/novox/mesh-controller/internal/builder 18.691s
ok github.com/novox/mesh-controller/internal/catalogue 8.056s
ok github.com/novox/mesh-controller/internal/conditions 2.642s
ok github.com/novox/mesh-controller/internal/envfile 1.056s
ok github.com/novox/mesh-controller/internal/facts 1.056s
ok github.com/novox/mesh-controller/internal/identity 4.940s
ok github.com/novox/mesh-controller/internal/inventory 96.979s
ok github.com/novox/mesh-controller/internal/lease 17.712s
ok github.com/novox/mesh-controller/internal/licences 4.446s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.045s
ok github.com/novox/mesh-controller/internal/link 61.419s
ok github.com/novox/mesh-controller/internal/lint 2.442s
ok github.com/novox/mesh-controller/internal/outward 1.082s
ok github.com/novox/mesh-controller/internal/overlay 1.059s
ok github.com/novox/mesh-controller/internal/secrets 1.527s
ok github.com/novox/mesh-controller/internal/store 3.559s
ok github.com/novox/mesh-controller/internal/testbus 1.233s
ok github.com/novox/mesh-controller/internal/token 1.015s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.27s)
**Merge check** at `e2801773`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent 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 is judged on its first machine
- read by no module's build: cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go, testdata/store-tests
Run by the build seat on shanks as `build-1791744316991075303` (`builds --log build-1791744316991075303`).
```
--- the gate: build-agent, mesh-controller
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-11T18:32:22Z 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-11T18:32:22Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/last_send_test.go, internal/inventory/sends_test.go and testdata/store-tests 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 241.160s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.040s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.047s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.030s
ok github.com/novox/mesh-controller/examples/route-proxy 1.202s
ok github.com/novox/mesh-controller/internal/artifacts 1.079s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.158s
ok github.com/novox/mesh-controller/internal/builder 18.691s
ok github.com/novox/mesh-controller/internal/catalogue 8.056s
ok github.com/novox/mesh-controller/internal/conditions 2.642s
ok github.com/novox/mesh-controller/internal/envfile 1.056s
ok github.com/novox/mesh-controller/internal/facts 1.056s
ok github.com/novox/mesh-controller/internal/identity 4.940s
ok github.com/novox/mesh-controller/internal/inventory 96.979s
ok github.com/novox/mesh-controller/internal/lease 17.712s
ok github.com/novox/mesh-controller/internal/licences 4.446s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.045s
ok github.com/novox/mesh-controller/internal/link 61.419s
ok github.com/novox/mesh-controller/internal/lint 2.442s
ok github.com/novox/mesh-controller/internal/outward 1.082s
ok github.com/novox/mesh-controller/internal/overlay 1.059s
ok github.com/novox/mesh-controller/internal/secrets 1.527s
ok github.com/novox/mesh-controller/internal/store 3.559s
ok github.com/novox/mesh-controller/internal/testbus 1.233s
ok github.com/novox/mesh-controller/internal/token 1.015s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (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 485 (status and node show do not say what a machine was last sent, by whom and from which generation).
The send record of issue 234 (#227,
declaration_send) can be read only through the controller's verbs now: issue 506 was closed because the store's reader may not read the controller's tables. Until now onlyplan <node>said the last send.What changes
inventory.LastSendsreads every machine's last recorded send in one query.LastSendnow carries the machine's answer too (Send.Answer: applied, failed or refused, the refusal's words, and when). A report counts as the send's answer only when it names the send's digest and arrived after the send, so a report about an earlier send is never taken for this one's answer.statusprints one line per machine:laptop 2026-10-11 18:40 by a one-shot push by jochen at a shell on anchor, generation 40 — applied. A machine with no recorded send saysno send recorded. If the record cannot be read, status says so and does not call the mesh well.status --jsoncarrieslastSent: node, sequence, sentAt, sender, epoch, generation, digest, modules, answer, refused, failed, answeredAt, refusedForGeneration and appliedGeneration.lastSentUnreadsays why the record could not be read.node show <n>andplan <n>print the last send in full: sequence and time, sender, lease epoch, generation, modules, and the machine's answer, with a refusal in the machine's own words.Not changed:
plan --json. It prints the exact bytes a push would send, through one marshaller, so the output cannot show a declaration other than the one sent. Adding the last send there would break that. The same fields are instatus --json, which thestatusseat verb answers.Tests (
cmd/mesh-controller/last_send_test.go,internal/inventory/sends_test.go). All of them fail to build on main, becauselastSendLines,answers.lastSent,Send.AnswerandLastSendsdo not exist there. The four pure tests pass. Two store tests are listed intestdata/store-tests:TestTheLastSendSaysWhatTheMachineAnsweredandTestNodeShowAndStatusReadTheLastSendFromTheStore. They skipped locally (no database was used), so the merge check must prove them. Rango vetandgo teston./internal/inventoryand./cmd/mesh-controller. The files of open #232 are not touched.Delivery
novox/mesh-controller@e2801773c300— delivered since 2026-10-11T19:17:32ZDelivery plan — builds build-agent, mesh-controller → 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
fae6bd0amesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791744072332917245(builds --log build-1791744072332917245).Merge check at
e2801773mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791744316991075303(builds --log build-1791744316991075303).