build-agent and route-proxy leave for mesh-controller (issue 1019, ADR 0420) #350

2026-10-17T16:25:07Z

mesh-tools commented

2026-10-17 16:25:07 +00:00

Design 47 phase II release 2 (playbook 07). One delivery group with mesh-controller's feat/whole-modules, which brings the two modules in whole; the merge gate judges the pair as a move (ADR 0420 §6).

modules/build-agent and modules/route-proxy removed.
mesh-issues' owners: "mesh-catalog modules/build-agent|route-proxy" become "mesh-controller modules/build-agent|route-proxy".

Reviewed (round 1, approve).

Order: the controller that recognizes the move and holds ADR 0420 §1's refusals merges first; "built by" points both ways while build-agent moves, version skew puts the controller first.

after: novox/mesh-controller

Design 47 phase II release 2 (playbook 07). One delivery group with mesh-controller's feat/whole-modules, which brings the two modules in whole; the merge gate judges the pair as a move (ADR 0420 §6). - modules/build-agent and modules/route-proxy removed. - mesh-issues' owners: "mesh-catalog modules/build-agent|route-proxy" become "mesh-controller modules/build-agent|route-proxy". Reviewed (round 1, approve). Order: the controller that recognizes the move and holds ADR 0420 §1's refusals merges first; "built by" points both ways while build-agent moves, version skew puts the controller first. after: novox/mesh-controller

mesh-tools added 2 commits 2026-10-17 16:25:08 +00:00

Build-agent and route-proxy leave for mesh-controller (issue 1019) 4c6e0b625e

Repoint the build-agent and route-proxy owners to mesh-controller (issue 1019)

mesh/delivery-group group feat/whole-modules rejected: its order contradicts itself: novox/mesh-catalog@c47d94925811 and novox/mesh-controller@48f5a7d3a99a: bu…

Details

mesh/merge-gate checking again: issue 1043: mesh-controller #370's new head 0125ccd7 lets a member's own gate see the move through the clones beside it; th…

Details

mesh/repo-check checking again: issue 1043: mesh-controller #370's new head 0125ccd7 lets a member's own gate see the move through the clones beside it; th…

Details

mesh/delivery superseded: a newer head of the same pull request

Details

c47d949258

mesh-tools commented

2026-10-17 16:25:13 +00:00

Delivery novox/mesh-catalog@629aafdea205 — stopped since 2026-10-17T17:54:59Z

Covered: covered after its stop: a later walk that contains it was delivered: plan-1792260860441586760 (novox/mesh-catalog at 5e7567e5 into main, done, contains its merge 5e6f5b8f)

Delivery plan — builds mesh-issues, new: modules/build-agent, modules/route-proxy → novox; no bus step

tier 0: mesh-issues
novox: receives mesh-issues

Transitions

2026-10-17 17:36 (new) → proposed (announced): novox/mesh-catalog#350's head announced
2026-10-17 17:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 17:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 17:44 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-17 17:44 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-17 17:54 delivering → stopped (stop): its walk plan-1792259058725870333 was stopped by a person (mesh-controller): deadlock (issue 1049): this plan waits at novox behind mesh-controller #370's unsent builds, and #370's retry is refused while this plan is open. Stopped so #370's plan sends mesh-controller and route-proxy; this merge is walked again after it. The operator said to build and deploy it (19:5x).

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@629aafdea205` — **stopped** since 2026-10-17T17:54:59Z **Covered**: covered after its stop: a later walk that contains it was delivered: plan-1792260860441586760 (novox/mesh-catalog at 5e7567e5 into main, done, contains its merge 5e6f5b8f) **Delivery plan** — builds mesh-issues, new: modules/build-agent, modules/route-proxy → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues **Transitions** - 2026-10-17 17:36 (new) → proposed (announced): novox/mesh-catalog#350's head announced - 2026-10-17 17:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-17 17:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-17 17:44 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-17 17:44 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-17 17:54 delivering → stopped (stop): its walk plan-1792259058725870333 was stopped by a person (mesh-controller): deadlock (issue 1049): this plan waits at novox behind mesh-controller #370's unsent builds, and #370's retry is refused while this plan is open. Stopped so #370's plan sends mesh-controller and route-proxy; this merge is walked again after it. The operator said to build and deploy it (19:5x). The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools referenced this pull request from novox/mesh-controller

2026-10-17 16:31:11 +00:00

build-agent and route-proxy live whole in mesh-controller (issue 1019, ADR 0420) #370

mesh-tools commented

2026-10-17 16:32:56 +00:00

Merge check at c47d9492
Judged: head c47d94925811 merged into trunk 54b3ce503e79; read beside it: mesh-controller b9c35ee08fce, mesh-controller-main c43772fd94eb, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5
Siblings read beside it: novox/mesh-controller#370 48f5a7d3a99a merged onto c43772fd94eb (main); judged by sibling novox/mesh-controller#370 merge b9c35ee08fce

mesh/merge-gate: FAIL — 12 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node (modules: build-agent, mesh-issues, route-proxy)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds build-agent, mesh-issues, route-proxy → novox; no bus step

tier 0: mesh-issues
novox: receives mesh-issues
read by no module's build: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md, modules/route-proxy/cmd/route-provider/provider_test.go

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

--- the gate: build-agent, mesh-issues, route-proxy
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, gitea.gitea_pull_reviews, records.records_status, records.records_list, records.records_read, mesh-knowledge.knowledge_highest, keeps state issues, counters, grooming, reservations, keeps log changes (1024 MiB)
long-running resources without health: 0
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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-17T16:23:34Z says they run
composing every machine as the mesh is
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
composing every machine with the change
merge gate: FAIL — 12 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node
judged by controller development build against the facts of 2026-10-17T16:23:34Z

fails:
  - a machine (f35): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node
  - a machine (yvbpsm): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node
  - build-agent cannot be assigned to a machine (f35): no module of that name: build-agent
  - build-agent cannot be assigned to a machine (yvbpsm): no module of that name: build-agent
  - build-agent cannot be assigned to holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): no module of that name: build-agent
  - build-agent cannot be assigned to holds mesh-dns-resolver (idt): no module of that name: build-agent
  - build-agent is removed from novox/mesh-catalog, and a machine (f35), holds mesh-dns-resolver (idt), holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr) and a machine (yvbpsm) run(s) it: unassign it first (ADR 0236)
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node
  - holds mesh-dns-resolver (idt): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node
  - route-proxy cannot be assigned to holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): no module of that name: route-proxy
  - route-proxy cannot be assigned to holds mesh-dns-resolver (idt): no module of that name: route-proxy
  - route-proxy is removed from novox/mesh-catalog, and holds mesh-dns-resolver (idt) and holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr) run(s) it: unassign it first (ADR 0236)

modules the change moves:
  - build-agent (removed)
  - mesh-issues (changed)
  - route-proxy (removed)

machines:
  - a machine (f35): does not compose; the change adds 0 resource(s) and removes 417
  - holds mesh-dns-resolver (idt): does not compose; the change adds 0 resource(s) and removes 756
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): does not compose; the change adds 0 resource(s) and removes 615
  - a machine (yvbpsm): does not compose; the change adds 0 resource(s) and removes 395

a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues

notes:
  - modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md and modules/route-proxy/cmd/route-provider/provider_test.go read by no module's build, and rebuild nothing (issue 280)
mesh-controller: the change fails the merge gate
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words and 70 daemons' lines, none in the 53656 strings of 805 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.010s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.007s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.013s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.011s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.219s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.018s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.196s
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	9.408s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `c47d9492` Judged: head `c47d94925811` merged into trunk `54b3ce503e79`; read beside it: mesh-controller `b9c35ee08fce`, mesh-controller-main `c43772fd94eb`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5` Siblings read beside it: novox/mesh-controller#370 `48f5a7d3a99a` merged onto `c43772fd94eb` (main); judged by sibling novox/mesh-controller#370 merge b9c35ee08fce - `mesh/merge-gate`: **FAIL** — 12 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node (modules: build-agent, mesh-issues, route-proxy) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds build-agent, mesh-issues, route-proxy → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md, modules/route-proxy/cmd/route-provider/provider_test.go Run by the build seat on ace as `build-1792254313051980393` (`builds --log build-1792254313051980393`). ``` --- the gate: build-agent, mesh-issues, route-proxy mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, gitea.gitea_pull_reviews, records.records_status, records.records_list, records.records_read, mesh-knowledge.knowledge_highest, keeps state issues, counters, grooming, reservations, keeps log changes (1024 MiB) long-running resources without health: 0 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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-17T16:23:34Z says they run composing every machine as the mesh is HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus composing every machine with the change merge gate: FAIL — 12 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node judged by controller development build against the facts of 2026-10-17T16:23:34Z fails: - a machine (f35): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node - a machine (yvbpsm): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node - build-agent cannot be assigned to a machine (f35): no module of that name: build-agent - build-agent cannot be assigned to a machine (yvbpsm): no module of that name: build-agent - build-agent cannot be assigned to holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): no module of that name: build-agent - build-agent cannot be assigned to holds mesh-dns-resolver (idt): no module of that name: build-agent - build-agent is removed from novox/mesh-catalog, and a machine (f35), holds mesh-dns-resolver (idt), holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr) and a machine (yvbpsm) run(s) it: unassign it first (ADR 0236) - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node - holds mesh-dns-resolver (idt): nothing could be sent to it with this change — the private network cannot be computed: this mesh has no hub, so there is no path between sites and 2 node(s) could not be resolved at all, which is probably why: idt: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by baserow — assign route-adapter to a node ygcyr: these assignments cannot be applied: - nothing in this mesh provides "route", wanted by de-spiegel — assign route-adapter to a node - route-proxy cannot be assigned to holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): no module of that name: route-proxy - route-proxy cannot be assigned to holds mesh-dns-resolver (idt): no module of that name: route-proxy - route-proxy is removed from novox/mesh-catalog, and holds mesh-dns-resolver (idt) and holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr) run(s) it: unassign it first (ADR 0236) modules the change moves: - build-agent (removed) - mesh-issues (changed) - route-proxy (removed) machines: - a machine (f35): does not compose; the change adds 0 resource(s) and removes 417 - holds mesh-dns-resolver (idt): does not compose; the change adds 0 resource(s) and removes 756 - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): does not compose; the change adds 0 resource(s) and removes 615 - a machine (yvbpsm): does not compose; the change adds 0 resource(s) and removes 395 a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md and modules/route-proxy/cmd/route-provider/provider_test.go read by no module's build, and rebuild nothing (issue 280) mesh-controller: the change fails the merge gate --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words and 70 daemons' lines, none in the 53656 strings of 805 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.007s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.013s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/secrets 0.011s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.219s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.018s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.196s testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 9.408s --- its merge-check-typescript.sh (typescript toolchain) ```

jschoubben referenced this issue from a commit

2026-10-17 16:43:10 +00:00

Declare the group's order: after novox/mesh-controller (issue 1019)

jschoubben added 1 commit 2026-10-17 16:43:10 +00:00

Declare the group's order: after novox/mesh-controller (issue 1019)

mesh/merge-gate waiting in the build queue since 19:32: asked by the merge tool against trunk 54b3ce503e79

Details

mesh/repo-check waiting in the build queue since 19:32: asked by the merge tool against trunk 54b3ce503e79

Details

mesh/delivery stopped: its group feat/whole-modules stopped: novox/mesh-controller@874a91a3c64f failed

Details

mesh/delivery-group group feat/whole-modules delivering: 1 of 2 delivered; novox/mesh-catalog@795806efa7ad, stopped for a member delivered since, waits for a l…

Details

795806efa7

mesh-delivery reads a pull request's after: lines only when it records a new head, so the
line added to #350's description takes effect with this head.

mesh-tools commented

2026-10-17 16:45:53 +00:00

Merge check at 795806ef
Judged: head 795806efa7ad merged into trunk 54b3ce503e79; read beside it: mesh-controller b2b57cc3c163, mesh-controller-main c43772fd94eb, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5
Siblings read beside it: novox/mesh-controller#370 0125ccd7d200 merged onto c43772fd94eb (main); judged by sibling novox/mesh-controller#370 merge b2b57cc3c163

mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-issues, route-proxy)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds build-agent, mesh-issues, route-proxy → novox; no bus step

tier 0: mesh-issues
novox: receives mesh-issues
read by no module's build: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md, modules/route-proxy/cmd/route-provider/provider_test.go

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

--- the gate: build-agent, mesh-issues, route-proxy
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, gitea.gitea_pull_reviews, records.records_status, records.records_list, records.records_read, mesh-knowledge.knowledge_highest, keeps state issues, counters, grooming, reservations, keeps log changes (1024 MiB)
long-running resources without health: 0
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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-17T16:23:34Z says they run
composing every machine as the mesh is
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
composing every machine with the change
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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-17T16:23:34Z

modules the change moves:
  - build-agent (moved)
  - mesh-issues (changed)
  - route-proxy (moved)

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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues

notes:
  - modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md and modules/route-proxy/cmd/route-provider/provider_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words and 70 daemons' lines, none in the 53656 strings of 805 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.011s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.008s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.014s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.011s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.217s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.012s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.010s
templates: no module keeps a file's text inline but the 0 listed
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.200s
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	10.368s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `795806ef` Judged: head `795806efa7ad` merged into trunk `54b3ce503e79`; read beside it: mesh-controller `b2b57cc3c163`, mesh-controller-main `c43772fd94eb`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5` Siblings read beside it: novox/mesh-controller#370 `0125ccd7d200` merged onto `c43772fd94eb` (main); judged by sibling novox/mesh-controller#370 merge b2b57cc3c163 - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-issues, route-proxy) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds build-agent, mesh-issues, route-proxy → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md, modules/route-proxy/cmd/route-provider/provider_test.go Run by the build seat on ace as `build-1792255392836213353` (`builds --log build-1792255392836213353`). ``` --- the gate: build-agent, mesh-issues, route-proxy mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, gitea.gitea_pull_reviews, records.records_status, records.records_list, records.records_read, mesh-knowledge.knowledge_highest, keeps state issues, counters, grooming, reservations, keeps log changes (1024 MiB) long-running resources without health: 0 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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-17T16:23:34Z says they run composing every machine as the mesh is HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus composing every machine with the change HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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-17T16:23:34Z modules the change moves: - build-agent (moved) - mesh-issues (changed) - route-proxy (moved) 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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md and modules/route-proxy/cmd/route-provider/provider_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words and 70 daemons' lines, none in the 53656 strings of 805 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.008s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.014s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/secrets 0.011s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.217s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.012s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.010s templates: no module keeps a file's text inline but the 0 listed ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.200s testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 10.368s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-tools added the mesh/ready label 2026-10-17 16:48:13 +00:00

mesh-tools commented

2026-10-17 16:48:13 +00:00

ready at 795806efa7

Reviewed by reviewer-1019@shanks: Approved: identical tree to reviewed c47d9492 (empty commit adds only the after: line); gate pass 4 of 4 with build-agent and route-proxy seen as moved, repo-check pass (issue 1019, ADR 0420). Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at 795806efa7ad95fa5cb3210b527117ad0316f4b9 Reviewed by reviewer-1019@shanks: Approved: identical tree to reviewed c47d9492 (empty commit adds only the after: line); gate pass 4 of 4 with build-agent and route-proxy seen as moved, repo-check pass (issue 1019, ADR 0420). Marked through mesh-delivery.mark-ready (novox/hq issue 913).

mesh-tools referenced this pull request from novox/mesh-controller

2026-10-17 16:49:12 +00:00

build-agent and route-proxy live whole in mesh-controller (issue 1019, ADR 0420) #370

mesh-tools referenced this pull request from novox/mesh-controller

2026-10-17 17:28:07 +00:00

build-agent and route-proxy live whole in mesh-controller (issue 1019, ADR 0420) #370

jschoubben added 1 commit 2026-10-17 17:36:34 +00:00

Check again after the group's delivery stopped (issue 1019)

mesh/merge-gate head 629aafdea205 merged into trunk 54b3ce503e79 — pass: builds mesh-issues, new: modules/build-agent, modules/route-proxy → novox; no bus …

Details

mesh/repo-check head 629aafdea205 merged into trunk 54b3ce503e79 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…

Details

mesh/delivery covered after its stop: a later walk that contains it was delivered: plan-1792260860441586760 (novox/mesh-catalog at 5e7567e5 into main, do…

Details

629aafdea2

mesh-controller #370 merged and registered route-proxy from mesh-controller; its plan then built
route-proxy from the catalogue, which still held it, and failed. This member removes it there.

mesh-tools removed the mesh/ready label 2026-10-17 17:37:39 +00:00

mesh-tools commented

2026-10-17 17:37:39 +00:00

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now 629aafdea2. Review it and mark that head with mesh-delivery.mark-ready, which writes label and comment in the order the forge counts.

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now 629aafdea205d6ca1e01a3aa81762b92fa51485f. Review it and mark that head with `mesh-delivery.mark-ready`, which writes label and comment in the order the forge counts.

mesh-tools commented

2026-10-17 17:40:05 +00:00

Merge check at 629aafde
Judged: head 629aafdea205 merged into trunk 54b3ce503e79; read beside it: mesh-controller d5d54498358e, mesh-controller-main d5d54498358e, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5

mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues, new:modules/build-agent, new:modules/route-proxy)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-issues, new: modules/build-agent, modules/route-proxy → novox; no bus step

tier 0: mesh-issues
novox: receives mesh-issues

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

--- the gate: mesh-issues, new:modules/build-agent, new:modules/route-proxy
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, gitea.gitea_pull_reviews, records.records_status, records.records_list, records.records_read, mesh-knowledge.knowledge_highest, keeps state issues, counters, grooming, reservations, keeps log changes (1024 MiB)
long-running resources without health: 0
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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-17T17:22:36Z says they run
composing every machine as the mesh is
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
composing every machine with the change
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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-17T17:22:36Z

modules the change moves:
  - build-agent (moved)
  - mesh-issues (changed)
  - route-proxy (moved)

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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues

notes:
  - modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md and modules/route-proxy/cmd/route-provider/provider_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 53656 strings of 805 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.018s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.016s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.278s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.016s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.237s
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	12.847s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `629aafde` Judged: head `629aafdea205` merged into trunk `54b3ce503e79`; read beside it: mesh-controller `d5d54498358e`, mesh-controller-main `d5d54498358e`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues, new:modules/build-agent, new:modules/route-proxy) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-issues, new: modules/build-agent, modules/route-proxy → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues Run by the build seat on shanks as `build-1792258597739164357` (`builds --log build-1792258597739164357`). ``` --- the gate: mesh-issues, new:modules/build-agent, new:modules/route-proxy mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, gitea.gitea_pull_reviews, records.records_status, records.records_list, records.records_read, mesh-knowledge.knowledge_highest, keeps state issues, counters, grooming, reservations, keeps log changes (1024 MiB) long-running resources without health: 0 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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-17T17:22:36Z says they run composing every machine as the mesh is HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus composing every machine with the change HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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-17T17:22:36Z modules the change moves: - build-agent (moved) - mesh-issues (changed) - route-proxy (moved) 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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go, modules/build-agent/templates_test.go, modules/route-proxy/README.md and modules/route-proxy/cmd/route-provider/provider_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 53656 strings of 805 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.018s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/secrets 0.016s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.278s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.016s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.237s testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 12.847s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-tools added the mesh/ready label 2026-10-17 17:43:32 +00:00

mesh-tools commented

2026-10-17 17:43:32 +00:00

ready at 629aafdea2

Reviewed by reviewer-1019@shanks: Approved: same tree as reviewed c47d9492 (two empty commits); gate pass 4 of 4 with mesh-controller beside at merged d5d54498 and build-agent and route-proxy seen as moved, repo-check pass (issue 1019, ADR 0420). Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at 629aafdea205d6ca1e01a3aa81762b92fa51485f Reviewed by reviewer-1019@shanks: Approved: same tree as reviewed c47d9492 (two empty commits); gate pass 4 of 4 with mesh-controller beside at merged d5d54498 and build-agent and route-proxy seen as moved, repo-check pass (issue 1019, ADR 0420). Marked through mesh-delivery.mark-ready (novox/hq issue 913).

mesh-tools merged commit 5e6f5b8f6d into main

2026-10-17 17:44:17 +00:00

mesh-tools deleted branch feat/whole-modules

2026-10-17 17:44:17 +00:00

mesh-tools referenced this issue from a commit

2026-10-17 17:55:09 +00:00

Take in main's move of build-agent and route-proxy to mesh-controller (issue 1024)

mesh-tools referenced this pull request

2026-10-17 18:09:30 +00:00

Every directory says how it treats files it does not know, and the catalogue checks it (issue 1024) #349

mesh-tools commented

2026-10-17 20:20:31 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 795806efa7 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 795806efa7ad is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#350