novox/mesh-controller
Archived
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

A mergeable file's own keys are the terminal's (hq issue 340) #172

Merged
mesh-admin merged 2 commits from fix/340-a-mergeable-files-own-keys-are-the-terminals into main 2026-10-09 07:46:40 +00:00
Conversation 4 Commits 2 Files Changed 4
+225 -8
mesh-admin commented 2026-10-09 00:34:08 +00:00
Contributor
Copy Link
Copy Source

TerminalKeys counted only ${setting:} placeholders, so a mergeable file's keys were any verb caller's. The claude-code module keeps managed_settings (hooks, permissions, status line) and mcp_servers in one, so any caller of mesh-controller.settings, an agent included, could plant a hook in every operator session on the mesh (hq issue 340).

Now a mergeable file not marked "trusted": false asks for every top-level key its content names; each is terminal-only like issue 339's keys. Refusal names issue 340.

Wider effect, said: 12 other catalogue files and 5 in the media catalogue now count as trusted (baserow, licence manager, grafana, letta, element, watcher/messenger chat ids, nodered, route-adapter, searxng, supabase pooler, unifi; kometa and four download configs). module check's unsaid count goes 9 → 22 on the catalogue. Opting harmless ones out with trusted: false waits for the node-engine to accept the field (mesh-host #65), as issue 339 says.

Tests through the real verb dispatch (TestTheAgentsManagedSettingsAreRefusedThroughAVerb) and TerminalKeys/UnsaidTrust cases: failed on main, pass here. Full suite passes without race; under race locally one unrelated timing test (TestATierPutsABrokenModuleBackAtOnce) failed once in the full run and passed 5/5 alone on this branch and on main.

Do not merge before review; pairs with mesh-catalog #149.

`TerminalKeys` counted only `${setting:}` placeholders, so a mergeable file's keys were any verb caller's. The claude-code module keeps `managed_settings` (hooks, permissions, status line) and `mcp_servers` in one, so any caller of `mesh-controller.settings`, an agent included, could plant a hook in every operator session on the mesh (hq issue 340). Now a mergeable file not marked `"trusted": false` asks for every top-level key its content names; each is terminal-only like issue 339's keys. Refusal names issue 340. **Wider effect, said:** 12 other catalogue files and 5 in the media catalogue now count as trusted (baserow, licence manager, grafana, letta, element, watcher/messenger chat ids, nodered, route-adapter, searxng, supabase pooler, unifi; kometa and four download configs). `module check`'s unsaid count goes 9 → 22 on the catalogue. Opting harmless ones out with `trusted: false` waits for the node-engine to accept the field (mesh-host #65), as issue 339 says. Tests through the real verb dispatch (`TestTheAgentsManagedSettingsAreRefusedThroughAVerb`) and `TerminalKeys`/`UnsaidTrust` cases: failed on main, pass here. Full suite passes without race; under race locally one unrelated timing test (`TestATierPutsABrokenModuleBackAtOnce`) failed once in the full run and passed 5/5 alone on this branch and on main. Do not merge before review; pairs with mesh-catalog #149.
mesh-admin added 1 commit 2026-10-09 00:34:08 +00:00
Make a mergeable file's own keys the terminal's, so no verb can set what every agent session obeys
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery superseded: a newer head of the same pull request
Details
f476494173 
The claude-code module keeps the managed settings and tool servers every
Claude Code session on a node runs in a mergeable file, and TerminalKeys
only counted ${setting:} placeholders, so any caller of the settings verb,
an agent included, could plant a hook in the operator's sessions on every
node (hq issue 340).
mesh-admin commented 2026-10-09 00:34:18 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-controller@55d8b43f303c — delivered since 2026-10-09T08:04:57Z

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-controller
  • tier 1: build-agent
  • tier 2: route-proxy
  • ace: receives build-agent, route-proxy
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent, route-proxy
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • route-proxy provides route: its consumers are sent again after it
  • route-proxy keeps data (ADR 0233): what it holds is backed up before it moves

Machines

  • mesh-controller on novox: passed — healthy 3 times over 3m39s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 3m37s
  • build-agent on the rest running it: sent
  • route-proxy on ace: passed — healthy 3 times over 3m37s
  • route-proxy on the rest running it: sent

Transitions

  • 2026-10-09 00:54 (new) → proposed (announced): novox/mesh-controller#172's head announced
  • 2026-10-09 01:00 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 01:00 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 07:39 ready → proposed (recheck): checked at 01:00Z before #171 and #173 merged; issue 341: checks judge the head, so recheck against today's main before merging
  • 2026-10-09 07:43 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 07:43 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 07:46 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-09 07:46 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
  • 2026-10-09 08:04 delivering → delivered (done): its walk is done: 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@55d8b43f303c` — **delivered** since 2026-10-09T08:04:57Z **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - mesh-controller on novox: passed — healthy 3 times over 3m39s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m37s - build-agent on the rest running it: sent - route-proxy on ace: passed — healthy 3 times over 3m37s - route-proxy on the rest running it: sent **Transitions** - 2026-10-09 00:54 (new) → proposed (announced): novox/mesh-controller#172's head announced - 2026-10-09 01:00 proposed → checked (checked): the verdict names this commit - 2026-10-09 01:00 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 07:39 ready → proposed (recheck): checked at 01:00Z before #171 and #173 merged; issue 341: checks judge the head, so recheck against today's main before merging - 2026-10-09 07:43 proposed → checked (checked): the verdict names this commit - 2026-10-09 07:43 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 07:46 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 07:46 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 - 2026-10-09 08:04 delivering → delivered (done): its walk is done: 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-admin commented 2026-10-09 00:41:00 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at f4764941

  • 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

Run by the build seat on novox as build-1791506066330797441 (builds --log build-1791506066330797441).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); 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: 0
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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:26:57Z 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-09T00:26:57Z

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.045s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	233.186s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.014s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.016s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.012s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.120s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.061s
ok  	github.com/novox/mesh-controller/internal/broker	8.640s
ok  	github.com/novox/mesh-controller/internal/builder	13.290s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.777s
ok  	github.com/novox/mesh-controller/internal/conditions	4.063s
ok  	github.com/novox/mesh-controller/internal/envfile	1.025s
ok  	github.com/novox/mesh-controller/internal/facts	1.032s
ok  	github.com/novox/mesh-controller/internal/identity	12.047s
ok  	github.com/novox/mesh-controller/internal/inventory	103.156s
ok  	github.com/novox/mesh-controller/internal/lease	18.064s
ok  	github.com/novox/mesh-controller/internal/licences	11.528s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.017s
ok  	github.com/novox/mesh-controller/internal/link	56.526s
ok  	github.com/novox/mesh-controller/internal/lint	2.033s
ok  	github.com/novox/mesh-controller/internal/outward	1.040s
ok  	github.com/novox/mesh-controller/internal/overlay	1.027s
ok  	github.com/novox/mesh-controller/internal/secrets	1.432s
ok  	github.com/novox/mesh-controller/internal/store	5.680s
ok  	github.com/novox/mesh-controller/internal/testbus	1.524s
ok  	github.com/novox/mesh-controller/internal/token	1.019s
**Merge check** at `f4764941` - `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 Run by the build seat on novox as `build-1791506066330797441` (`builds --log build-1791506066330797441`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 tool(s); 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: 0 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:26:57Z 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-09T00:26:57Z 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.045s ok github.com/novox/mesh-controller/cmd/mesh-controller 233.186s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.016s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.012s ok github.com/novox/mesh-controller/examples/route-proxy 1.120s ok github.com/novox/mesh-controller/internal/artifacts 1.061s ok github.com/novox/mesh-controller/internal/broker 8.640s ok github.com/novox/mesh-controller/internal/builder 13.290s ok github.com/novox/mesh-controller/internal/catalogue 4.777s ok github.com/novox/mesh-controller/internal/conditions 4.063s ok github.com/novox/mesh-controller/internal/envfile 1.025s ok github.com/novox/mesh-controller/internal/facts 1.032s ok github.com/novox/mesh-controller/internal/identity 12.047s ok github.com/novox/mesh-controller/internal/inventory 103.156s ok github.com/novox/mesh-controller/internal/lease 18.064s ok github.com/novox/mesh-controller/internal/licences 11.528s ok github.com/novox/mesh-controller/internal/licences/adapters 1.017s ok github.com/novox/mesh-controller/internal/link 56.526s ok github.com/novox/mesh-controller/internal/lint 2.033s ok github.com/novox/mesh-controller/internal/outward 1.040s ok github.com/novox/mesh-controller/internal/overlay 1.027s ok github.com/novox/mesh-controller/internal/secrets 1.432s ok github.com/novox/mesh-controller/internal/store 5.680s ok github.com/novox/mesh-controller/internal/testbus 1.524s ok github.com/novox/mesh-controller/internal/token 1.019s ```
jschoubben added 1 commit 2026-10-09 00:54:45 +00:00
Refuse any change through a verb to a module with a trusted mergeable file
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
55d8b43f30 
A mergeable file takes any key, not only those its content names, so an
empty runtime configuration a provider reads took a url of the caller's
through the settings verb (hq issue 340 review).
mesh-admin commented 2026-10-09 01:00:05 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 55d8b43f

  • 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

Run by the build seat on shanks as build-1791507294583076708 (builds --log build-1791507294583076708).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); 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: 0
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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:53:55Z 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-09T00:53:55Z

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.032s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	194.498s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.042s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.051s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.037s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.192s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.086s
ok  	github.com/novox/mesh-controller/internal/broker	2.733s
ok  	github.com/novox/mesh-controller/internal/builder	1.987s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.958s
ok  	github.com/novox/mesh-controller/internal/conditions	2.520s
ok  	github.com/novox/mesh-controller/internal/envfile	1.053s
ok  	github.com/novox/mesh-controller/internal/facts	1.060s
ok  	github.com/novox/mesh-controller/internal/identity	4.711s
ok  	github.com/novox/mesh-controller/internal/inventory	84.114s
ok  	github.com/novox/mesh-controller/internal/lease	17.704s
ok  	github.com/novox/mesh-controller/internal/licences	4.288s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.055s
ok  	github.com/novox/mesh-controller/internal/link	53.050s
ok  	github.com/novox/mesh-controller/internal/lint	2.181s
ok  	github.com/novox/mesh-controller/internal/outward	1.087s
ok  	github.com/novox/mesh-controller/internal/overlay	1.068s
ok  	github.com/novox/mesh-controller/internal/secrets	1.519s
ok  	github.com/novox/mesh-controller/internal/store	3.451s
ok  	github.com/novox/mesh-controller/internal/testbus	1.229s
ok  	github.com/novox/mesh-controller/internal/token	1.017s
**Merge check** at `55d8b43f` - `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 Run by the build seat on shanks as `build-1791507294583076708` (`builds --log build-1791507294583076708`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 tool(s); 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: 0 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:53:55Z 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-09T00:53:55Z 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.032s ok github.com/novox/mesh-controller/cmd/mesh-controller 194.498s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.042s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.051s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.037s ok github.com/novox/mesh-controller/examples/route-proxy 1.192s ok github.com/novox/mesh-controller/internal/artifacts 1.086s ok github.com/novox/mesh-controller/internal/broker 2.733s ok github.com/novox/mesh-controller/internal/builder 1.987s ok github.com/novox/mesh-controller/internal/catalogue 4.958s ok github.com/novox/mesh-controller/internal/conditions 2.520s ok github.com/novox/mesh-controller/internal/envfile 1.053s ok github.com/novox/mesh-controller/internal/facts 1.060s ok github.com/novox/mesh-controller/internal/identity 4.711s ok github.com/novox/mesh-controller/internal/inventory 84.114s ok github.com/novox/mesh-controller/internal/lease 17.704s ok github.com/novox/mesh-controller/internal/licences 4.288s ok github.com/novox/mesh-controller/internal/licences/adapters 1.055s ok github.com/novox/mesh-controller/internal/link 53.050s ok github.com/novox/mesh-controller/internal/lint 2.181s ok github.com/novox/mesh-controller/internal/outward 1.087s ok github.com/novox/mesh-controller/internal/overlay 1.068s ok github.com/novox/mesh-controller/internal/secrets 1.519s ok github.com/novox/mesh-controller/internal/store 3.451s ok github.com/novox/mesh-controller/internal/testbus 1.229s ok github.com/novox/mesh-controller/internal/token 1.017s ```
mesh-admin commented 2026-10-09 07:43:59 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 55d8b43f

  • 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

Run by the build seat on ace as build-1791531567705606849 (builds --log build-1791531567705606849).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); 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: 0
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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T07:35:08Z 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-09T07:35:08Z

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.031s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	170.458s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.015s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.017s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.014s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.118s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.037s
ok  	github.com/novox/mesh-controller/internal/broker	2.537s
ok  	github.com/novox/mesh-controller/internal/builder	1.875s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.406s
ok  	github.com/novox/mesh-controller/internal/conditions	2.441s
ok  	github.com/novox/mesh-controller/internal/envfile	1.072s
ok  	github.com/novox/mesh-controller/internal/facts	1.069s
ok  	github.com/novox/mesh-controller/internal/identity	4.142s
ok  	github.com/novox/mesh-controller/internal/inventory	71.052s
ok  	github.com/novox/mesh-controller/internal/lease	17.712s
ok  	github.com/novox/mesh-controller/internal/licences	3.778s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.062s
ok  	github.com/novox/mesh-controller/internal/link	50.756s
ok  	github.com/novox/mesh-controller/internal/lint	2.014s
ok  	github.com/novox/mesh-controller/internal/outward	1.099s
ok  	github.com/novox/mesh-controller/internal/overlay	1.086s
ok  	github.com/novox/mesh-controller/internal/secrets	1.444s
ok  	github.com/novox/mesh-controller/internal/store	3.308s
ok  	github.com/novox/mesh-controller/internal/testbus	1.243s
ok  	github.com/novox/mesh-controller/internal/token	1.020s
**Merge check** at `55d8b43f` - `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 Run by the build seat on ace as `build-1791531567705606849` (`builds --log build-1791531567705606849`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 tool(s); 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: 0 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T07:35:08Z 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-09T07:35:08Z 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.031s ok github.com/novox/mesh-controller/cmd/mesh-controller 170.458s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.015s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.017s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.014s ok github.com/novox/mesh-controller/examples/route-proxy 1.118s ok github.com/novox/mesh-controller/internal/artifacts 1.037s ok github.com/novox/mesh-controller/internal/broker 2.537s ok github.com/novox/mesh-controller/internal/builder 1.875s ok github.com/novox/mesh-controller/internal/catalogue 4.406s ok github.com/novox/mesh-controller/internal/conditions 2.441s ok github.com/novox/mesh-controller/internal/envfile 1.072s ok github.com/novox/mesh-controller/internal/facts 1.069s ok github.com/novox/mesh-controller/internal/identity 4.142s ok github.com/novox/mesh-controller/internal/inventory 71.052s ok github.com/novox/mesh-controller/internal/lease 17.712s ok github.com/novox/mesh-controller/internal/licences 3.778s ok github.com/novox/mesh-controller/internal/licences/adapters 1.062s ok github.com/novox/mesh-controller/internal/link 50.756s ok github.com/novox/mesh-controller/internal/lint 2.014s ok github.com/novox/mesh-controller/internal/outward 1.099s ok github.com/novox/mesh-controller/internal/overlay 1.086s ok github.com/novox/mesh-controller/internal/secrets 1.444s ok github.com/novox/mesh-controller/internal/store 3.308s ok github.com/novox/mesh-controller/internal/testbus 1.243s ok github.com/novox/mesh-controller/internal/token 1.020s ```
mesh-admin merged commit 4d60628f37 into main 2026-10-09 07:46:40 +00:00
mesh-admin deleted branch fix/340-a-mergeable-files-own-keys-are-the-terminals 2026-10-09 07:46:40 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#172