Moved from #251 (reviewed and approved at 3647928, review 41) so it leaves the group fix/345-reminder-test; rebased onto main (4b1dee6), conflicts: none. git range-diff: both commits = (9d108fe = b849af5, 3647928 = b0c4b84).
What. The build seat's part of novox/hq ADR 0316 §2 and §6 (to-be 56 §7), for issue 345.
catalogue.Artifact gains url, sha256, version, file or within, and names-on-purpose, for an archive only. Checked: an archive with a URL names no from, is fetched over https from a public name (an address, a name without a domain, or one under a reserved suffix such as .internal or .lan is refused), is pinned by a 64-hex sha256 and a version; file is a plain file name, within a plain directory, not both (upstreamFileProblems).
The build seat (internal/builder/upstream_file.go) fetches the file once and keeps it in its workspace under its sha256. A download whose digest is not the pin's fails the build and names both digests, and nothing is kept. A redirect off https is not followed. The file is laid out as the artifact says (a single file kept whole under file, or a tar archive in gzip, bzip2 or xz with the content of within, a nested within's parents and a pax global header accepted) and packed with the same pack as every archive. A link, a device, an entry outside the archive or outside within, or more than 100,000 entries refuses the build. xz's output is drained before it is waited for. The node-engine is unchanged.
cmd/mesh-builder/Dockerfile: xz added to the image.
InstallationProblems (ADR 0112 check): an upstream pin's url is judged like any value, its vendor's host declared in the artifact's names-on-purpose; only the version's dotted-quad reading is skipped (Owl 1.5.6.1), a name in it still judged.
Why. A Betterbird release is about 80 MB per version, too large to keep in a repository at every upgrade, and Owl's licence forbids copying it to third parties. The vendor serves only Owl's newest version at one address: keeping the fetched file by digest lets a later build of the same pin succeed.
How it was tested.internal/builder/upstream_file_test.go and internal/catalogue/upstream_file_test.go (fetch, pin mismatch naming both digests, fetched once, xpi kept whole, refused entries, xz, entry cap, pax header, nested within, xz trailing data, no https downgrade; the shapes accepted and refused; the vendor named on purpose, an installation's host, an address and a reserved name refused). By hand: the real Betterbird 153.4.0esr-bb10 .tar.xz packed to 55 files, 120,342,573 bytes. sh merge-check.sh passes locally on this head (store tests skipped, no MESH_TEST_POSTGRES).
Order. This first: mesh-catalog #240 (the betterbird module) uses the new fields, which the running controller refuses as unknown. A controller rollout: merge only while mesh-controller.plans says no plan is mid-gate.
Limits (follow-ups). The kept files are never collected; about 1 GiB of memory at the caps. version is said, not checked against the file. The first build of the Owl pin must happen while the vendor still serves 1.5.6.1.
Part of issue 345. Not merged.
Moved from #251 (reviewed and approved at 3647928, review 41) so it leaves the group fix/345-reminder-test; rebased onto main (4b1dee6), conflicts: none. `git range-diff`: both commits `=` (9d108fe = b849af5, 3647928 = b0c4b84).
**What.** The build seat's part of novox/hq ADR 0316 §2 and §6 (to-be 56 §7), for issue 345.
- `catalogue.Artifact` gains `url`, `sha256`, `version`, `file` or `within`, and `names-on-purpose`, for an `archive` only. Checked: an archive with a URL names no `from`, is fetched over https from a public name (an address, a name without a domain, or one under a reserved suffix such as .internal or .lan is refused), is pinned by a 64-hex sha256 and a version; `file` is a plain file name, `within` a plain directory, not both (`upstreamFileProblems`).
- The build seat (`internal/builder/upstream_file.go`) fetches the file **once** and keeps it in its workspace under its sha256. A download whose digest is not the pin's **fails the build and names both digests**, and nothing is kept. A redirect off https is not followed. The file is laid out as the artifact says (a single file kept whole under `file`, or a tar archive in gzip, bzip2 or xz with the content of `within`, a nested `within`'s parents and a pax global header accepted) and packed with the same `pack` as every archive. A link, a device, an entry outside the archive or outside `within`, or more than 100,000 entries refuses the build. xz's output is drained before it is waited for. The node-engine is unchanged.
- `cmd/mesh-builder/Dockerfile`: `xz` added to the image.
- `InstallationProblems` (ADR 0112 check): an upstream pin's `url` is judged like any value, its vendor's host declared in the artifact's `names-on-purpose`; only the version's dotted-quad reading is skipped (Owl 1.5.6.1), a name in it still judged.
**Why.** A Betterbird release is about 80 MB per version, too large to keep in a repository at every upgrade, and Owl's licence forbids copying it to third parties. The vendor serves only Owl's newest version at one address: keeping the fetched file by digest lets a later build of the same pin succeed.
**How it was tested.** `internal/builder/upstream_file_test.go` and `internal/catalogue/upstream_file_test.go` (fetch, pin mismatch naming both digests, fetched once, xpi kept whole, refused entries, xz, entry cap, pax header, nested within, xz trailing data, no https downgrade; the shapes accepted and refused; the vendor named on purpose, an installation's host, an address and a reserved name refused). By hand: the real Betterbird 153.4.0esr-bb10 `.tar.xz` packed to 55 files, 120,342,573 bytes. `sh merge-check.sh` passes locally on this head (store tests skipped, no `MESH_TEST_POSTGRES`).
**Order.** This first: mesh-catalog #240 (the betterbird module) uses the new fields, which the running controller refuses as unknown. A controller rollout: merge only while `mesh-controller.plans` says no plan is mid-gate.
**Limits (follow-ups).** The kept files are never collected; about 1 GiB of memory at the caps. `version` is said, not checked against the file. The first build of the Owl pin must happen while the vendor still serves 1.5.6.1.
Part of issue 345. Not merged.
A mail client's release is about 80 MB per version, too large to keep in a
repository at every upgrade, and an add-on whose licence forbids copying it
to third parties may not be in a repository at all. An archive artifact may
now name url, sha256 and version (and file or within) instead of from: the
build seat fetches it once, refuses it when its digest is not the pin's and
names both, keeps it in its workspace under the digest (a vendor that serves
only its newest version cannot break a later build of the same pin), and
packs it like any archive, so a node gets the mesh's own archive by digest
and never asks the vendor. The build seat's image carries xz, which Go's
standard library does not read. The installation check takes the vendor's
address and version of such a pin for the world's, as a registry is an
image's.
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 url was skipped by the installation check, so an installation's host or
an address passed; it is judged whole now, the vendor's host declared in the
artifact's names-on-purpose, and an address or a reserved name as the host
is refused. Only the version's dotted-quad reading is skipped. The unpack
caps its entries, drains xz before waiting for it, reads a pax global
header and a nested within's parents, and a redirect off https is not
followed.
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 4m7s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 1 times over 1m29s
build-agent on the rest running it: sent
Transitions
2026-10-12 11:53 (new) → proposed (announced): novox/mesh-controller#255's head announced
2026-10-12 12:08 proposed → checked (checked): the verdict names this commit
2026-10-12 12:08 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 12:34 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:34 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:45 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@b0c4b849a7e5` — **delivered** since 2026-10-12T12:45:24Z
**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 4m7s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 1 times over 1m29s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-12 11:53 (new) → proposed (announced): novox/mesh-controller#255's head announced
- 2026-10-12 12:08 proposed → checked (checked): the verdict names this commit
- 2026-10-12 12:08 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 12:34 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:34 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:45 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 novox as build-1791806007719453212 (builds --log build-1791806007719453212).
--- the gate: build-agent, 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.133s
ok github.com/novox/mesh-controller/cmd/mesh-controller 358.892s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.034s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.153s
ok github.com/novox/mesh-controller/internal/artifacts 1.057s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 7.670s
ok github.com/novox/mesh-controller/internal/builder 76.674s
ok github.com/novox/mesh-controller/internal/catalogue 8.423s
ok github.com/novox/mesh-controller/internal/conditions 2.647s
ok github.com/novox/mesh-controller/internal/envfile 1.016s
ok github.com/novox/mesh-controller/internal/facts 1.014s
ok github.com/novox/mesh-controller/internal/identity 12.094s
ok github.com/novox/mesh-controller/internal/inventory 155.060s
ok github.com/novox/mesh-controller/internal/lease 17.993s
ok github.com/novox/mesh-controller/internal/licences 9.221s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.013s
ok github.com/novox/mesh-controller/internal/link 84.316s
ok github.com/novox/mesh-controller/internal/lint 2.560s
ok github.com/novox/mesh-controller/internal/outward 1.048s
ok github.com/novox/mesh-controller/internal/overlay 1.026s
ok github.com/novox/mesh-controller/internal/secrets 1.505s
ok github.com/novox/mesh-controller/internal/store 8.314s
ok github.com/novox/mesh-controller/internal/testbus 1.187s
ok github.com/novox/mesh-controller/internal/token 1.013s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.49s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.44s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.44s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.43s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.59s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.35s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.51s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.55s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.49s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.51s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.49s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.38s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.59s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.32s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.28s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.31s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.55s)
**Merge check** at `b0c4b849`
- `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 novox as `build-1791806007719453212` (`builds --log build-1791806007719453212`).
```
--- the gate: build-agent, 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.133s
ok github.com/novox/mesh-controller/cmd/mesh-controller 358.892s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.034s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.153s
ok github.com/novox/mesh-controller/internal/artifacts 1.057s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 7.670s
ok github.com/novox/mesh-controller/internal/builder 76.674s
ok github.com/novox/mesh-controller/internal/catalogue 8.423s
ok github.com/novox/mesh-controller/internal/conditions 2.647s
ok github.com/novox/mesh-controller/internal/envfile 1.016s
ok github.com/novox/mesh-controller/internal/facts 1.014s
ok github.com/novox/mesh-controller/internal/identity 12.094s
ok github.com/novox/mesh-controller/internal/inventory 155.060s
ok github.com/novox/mesh-controller/internal/lease 17.993s
ok github.com/novox/mesh-controller/internal/licences 9.221s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.013s
ok github.com/novox/mesh-controller/internal/link 84.316s
ok github.com/novox/mesh-controller/internal/lint 2.560s
ok github.com/novox/mesh-controller/internal/outward 1.048s
ok github.com/novox/mesh-controller/internal/overlay 1.026s
ok github.com/novox/mesh-controller/internal/secrets 1.505s
ok github.com/novox/mesh-controller/internal/store 8.314s
ok github.com/novox/mesh-controller/internal/testbus 1.187s
ok github.com/novox/mesh-controller/internal/token 1.013s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.49s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.44s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.44s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.43s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.59s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.35s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.51s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.55s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.49s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.51s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.49s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.38s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.59s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.32s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.28s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.31s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.55s)
```
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: internal/builder/upstream_file_test.go, internal/catalogue/upstream_file_test.go
Run by the build seat on shanks as build-1791806908985873254 (builds --log build-1791806908985873254).
--- the gate: build-agent, 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-12T12:01: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-12T12:01: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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/builder/upstream_file_test.go and internal/catalogue/upstream_file_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.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 266.798s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.065s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.069s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.053s
ok github.com/novox/mesh-controller/examples/route-proxy 1.278s
ok github.com/novox/mesh-controller/internal/artifacts 1.100s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.440s
ok github.com/novox/mesh-controller/internal/builder 38.841s
ok github.com/novox/mesh-controller/internal/catalogue 8.163s
ok github.com/novox/mesh-controller/internal/conditions 2.687s
ok github.com/novox/mesh-controller/internal/envfile 1.073s
ok github.com/novox/mesh-controller/internal/facts 1.078s
ok github.com/novox/mesh-controller/internal/identity 5.027s
ok github.com/novox/mesh-controller/internal/inventory 100.800s
ok github.com/novox/mesh-controller/internal/lease 17.721s
ok github.com/novox/mesh-controller/internal/licences 4.459s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.042s
ok github.com/novox/mesh-controller/internal/link 61.610s
ok github.com/novox/mesh-controller/internal/lint 2.502s
ok github.com/novox/mesh-controller/internal/outward 1.094s
ok github.com/novox/mesh-controller/internal/overlay 1.077s
ok github.com/novox/mesh-controller/internal/secrets 1.531s
ok github.com/novox/mesh-controller/internal/store 3.519s
ok github.com/novox/mesh-controller/internal/testbus 1.257s
ok github.com/novox/mesh-controller/internal/token 1.016s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.47s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.41s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.45s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.33s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.45s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.41s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.41s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.44s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.26s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.25s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.25s)
**Merge check** at `b0c4b849`
- `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: internal/builder/upstream_file_test.go, internal/catalogue/upstream_file_test.go
Run by the build seat on shanks as `build-1791806908985873254` (`builds --log build-1791806908985873254`).
```
--- the gate: build-agent, 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-12T12:01: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-12T12:01: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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/builder/upstream_file_test.go and internal/catalogue/upstream_file_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.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 266.798s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.065s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.069s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.053s
ok github.com/novox/mesh-controller/examples/route-proxy 1.278s
ok github.com/novox/mesh-controller/internal/artifacts 1.100s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.440s
ok github.com/novox/mesh-controller/internal/builder 38.841s
ok github.com/novox/mesh-controller/internal/catalogue 8.163s
ok github.com/novox/mesh-controller/internal/conditions 2.687s
ok github.com/novox/mesh-controller/internal/envfile 1.073s
ok github.com/novox/mesh-controller/internal/facts 1.078s
ok github.com/novox/mesh-controller/internal/identity 5.027s
ok github.com/novox/mesh-controller/internal/inventory 100.800s
ok github.com/novox/mesh-controller/internal/lease 17.721s
ok github.com/novox/mesh-controller/internal/licences 4.459s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.042s
ok github.com/novox/mesh-controller/internal/link 61.610s
ok github.com/novox/mesh-controller/internal/lint 2.502s
ok github.com/novox/mesh-controller/internal/outward 1.094s
ok github.com/novox/mesh-controller/internal/overlay 1.077s
ok github.com/novox/mesh-controller/internal/secrets 1.531s
ok github.com/novox/mesh-controller/internal/store 3.519s
ok github.com/novox/mesh-controller/internal/testbus 1.257s
ok github.com/novox/mesh-controller/internal/token 1.016s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.47s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.41s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.45s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.33s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.45s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.41s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.41s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.46s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.44s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.26s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.25s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.25s)
```
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.
Moved from #251 (reviewed and approved at
3647928, review 41) so it leaves the group fix/345-reminder-test; rebased onto main (4b1dee6), conflicts: none.git range-diff: both commits=(9d108fe=b849af5,3647928=b0c4b84).What. The build seat's part of novox/hq ADR 0316 §2 and §6 (to-be 56 §7), for issue 345.
catalogue.Artifactgainsurl,sha256,version,fileorwithin, andnames-on-purpose, for anarchiveonly. Checked: an archive with a URL names nofrom, is fetched over https from a public name (an address, a name without a domain, or one under a reserved suffix such as .internal or .lan is refused), is pinned by a 64-hex sha256 and a version;fileis a plain file name,withina plain directory, not both (upstreamFileProblems).internal/builder/upstream_file.go) fetches the file once and keeps it in its workspace under its sha256. A download whose digest is not the pin's fails the build and names both digests, and nothing is kept. A redirect off https is not followed. The file is laid out as the artifact says (a single file kept whole underfile, or a tar archive in gzip, bzip2 or xz with the content ofwithin, a nestedwithin's parents and a pax global header accepted) and packed with the samepackas every archive. A link, a device, an entry outside the archive or outsidewithin, or more than 100,000 entries refuses the build. xz's output is drained before it is waited for. The node-engine is unchanged.cmd/mesh-builder/Dockerfile:xzadded to the image.InstallationProblems(ADR 0112 check): an upstream pin'surlis judged like any value, its vendor's host declared in the artifact'snames-on-purpose; only the version's dotted-quad reading is skipped (Owl 1.5.6.1), a name in it still judged.Why. A Betterbird release is about 80 MB per version, too large to keep in a repository at every upgrade, and Owl's licence forbids copying it to third parties. The vendor serves only Owl's newest version at one address: keeping the fetched file by digest lets a later build of the same pin succeed.
How it was tested.
internal/builder/upstream_file_test.goandinternal/catalogue/upstream_file_test.go(fetch, pin mismatch naming both digests, fetched once, xpi kept whole, refused entries, xz, entry cap, pax header, nested within, xz trailing data, no https downgrade; the shapes accepted and refused; the vendor named on purpose, an installation's host, an address and a reserved name refused). By hand: the real Betterbird 153.4.0esr-bb10.tar.xzpacked to 55 files, 120,342,573 bytes.sh merge-check.shpasses locally on this head (store tests skipped, noMESH_TEST_POSTGRES).Order. This first: mesh-catalog #240 (the betterbird module) uses the new fields, which the running controller refuses as unknown. A controller rollout: merge only while
mesh-controller.planssays no plan is mid-gate.Limits (follow-ups). The kept files are never collected; about 1 GiB of memory at the caps.
versionis said, not checked against the file. The first build of the Owl pin must happen while the vendor still serves 1.5.6.1.Part of issue 345. Not merged.
Delivery
novox/mesh-controller@b0c4b849a7e5— delivered since 2026-10-12T12:45:24ZDelivery 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
b0c4b849mesh/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 novox as
build-1791806007719453212(builds --log build-1791806007719453212).Merge check at
b0c4b849mesh/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-1791806908985873254(builds --log build-1791806908985873254).