novox/mesh-catalog
13
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Remove today's delivery module now that the gate holds its seat (design 47 R3e, issue 1351, ADR 0454) #381

Merged
mesh-tools merged 2 commits from fix/1351-remove-todays-delivery-module into main 2026-10-20 12:27:48 +00:00
Conversation 2 Commits 2 Files Changed 75
+24 -21231
mesh-tools commented 2026-10-20 12:10:23 +00:00
Member
Copy Link
Copy Source

Design 47 release R3e's last step (ADR 0454, issue 1351 AC1/AC2). Since 2026-10-20 11:40 UTC the gate (modules/mesh-delivery-gate) holds the seat mesh-delivery on novox, and today's module is assigned nowhere (mesh-controller.modules: mesh-delivery on []). This removes modules/mesh-delivery from the catalogue.

  • 1ef19030: modules/mesh-delivery deleted (70 files).
  • 1c702422: the catalogue test is strict, so the gate is the seat's only claimant (TestTheCatalogueHoldsTheGateAsTheOnlyClaimantOfTheSeat, seen failing with today's module present). The gate's README says the removal happened. .gitignore loses the old module's build output. A mesh-issues comment points at the gate's IDOf. The owner "mesh-catalog modules/mesh-delivery" stays registered for old issues, and the mesh-issues manifest test names it as retired.

Kept: the seat name mesh-delivery, the buckets mesh-delivery.deliveries/.groups/.pulls the gate carried from, and the asker name accepted until release 4 (ADR 0450 §8).

Nothing sent to a machine changes: the module runs nowhere.

Checks before this pull request: try build-1792498093112085741 passed (gate PASS; merge-check.sh and merge-check-typescript.sh passed). A first try failed a timed gate test that waits 5 s for an ask on a loaded build node (issue 1404); the same test passed in the second run.
Opened along the way: 1404, and by the review 1405, 1406 and 1407.

Reviewed-by: review-1351@shanks at 1c7024224d

Issues: 1351

Design 47 release R3e's last step (ADR 0454, issue 1351 AC1/AC2). Since 2026-10-20 11:40 UTC the gate (modules/mesh-delivery-gate) holds the seat `mesh-delivery` on novox, and today's module is assigned nowhere (`mesh-controller.modules`: mesh-delivery on []). This removes modules/mesh-delivery from the catalogue. - 1ef19030: modules/mesh-delivery deleted (70 files). - 1c702422: the catalogue test is strict, so the gate is the seat's only claimant (TestTheCatalogueHoldsTheGateAsTheOnlyClaimantOfTheSeat, seen failing with today's module present). The gate's README says the removal happened. .gitignore loses the old module's build output. A mesh-issues comment points at the gate's IDOf. The owner "mesh-catalog modules/mesh-delivery" stays registered for old issues, and the mesh-issues manifest test names it as retired. Kept: the seat name `mesh-delivery`, the buckets `mesh-delivery.deliveries/.groups/.pulls` the gate carried from, and the asker name accepted until release 4 (ADR 0450 §8). Nothing sent to a machine changes: the module runs nowhere. Checks before this pull request: try build-1792498093112085741 passed (gate PASS; merge-check.sh and merge-check-typescript.sh passed). A first try failed a timed gate test that waits 5 s for an ask on a loaded build node (issue 1404); the same test passed in the second run. Opened along the way: 1404, and by the review 1405, 1406 and 1407. Reviewed-by: review-1351@shanks at 1c7024224dd77c5b603299378883e0993b2e2fdd Issues: 1351
mesh-tools added 2 commits 2026-10-20 12:10:23 +00:00
Remove today's mesh-delivery module: the gate holds the seat since the handover (ADR 0454, issue 1351) 1ef19030f1
Make the catalogue test strict: the gate alone claims the seat, and say the old module is gone (ADR 0454, issue 1351)
mesh/merge-gate head 1c7024224dd7 merged into trunk bb0fe93bbddd — pass: builds mesh-delivery, mesh-issues → novox; no bus step; every machine composes wit…
Details
mesh/repo-check head 1c7024224dd7 merged into trunk bb0fe93bbddd — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Details
mesh/delivery delivered
Details
1c7024224d
mesh-tools commented 2026-10-20 12:10:34 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@1c7024224dd7 — delivered since 2026-10-20T12:28:46Z

Delivery plan — builds mesh-delivery, mesh-issues → novox; no bus step

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

Machines

  • mesh-issues on every machine running it: sent

Transitions

  • 2026-10-20 12:10 (new) → proposed (announced): novox/mesh-catalog#381's head announced
  • 2026-10-20 12:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-20 12:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-20 12:27 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-20 12:27 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-20 12:28 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@1c7024224dd7` — **delivered** since 2026-10-20T12:28:46Z **Delivery plan** — builds mesh-delivery, mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues **Machines** - mesh-issues on every machine running it: sent **Transitions** - 2026-10-20 12:10 (new) → proposed (announced): novox/mesh-catalog#381's head announced - 2026-10-20 12:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-20 12:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-20 12:27 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-20 12:27 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-20 12:28 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-tools commented 2026-10-20 12:14:35 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 1c702422
Judged: head 1c7024224dd7 merged into trunk bb0fe93bbddd; read beside it: mesh-controller b718d24f84b9, mesh-controller-main b718d24f84b9, mesh-host cdcba9ca7375, mesh-tools 7412c5b6c9c5

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery, mesh-issues)
  • 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-delivery, mesh-issues → novox; no bus step

  • tier 0: mesh-issues
  • novox: receives mesh-issues
  • read by no module's build: .gitignore, modules/mesh-delivery-gate/README.md, modules/mesh-delivery-gate/cmd/mesh-delivery-gate/catalogue_test.go, modules/mesh-delivery/README.md, modules/mesh-delivery/cmd/mesh-delivery/adr350_test.go, modules/mesh-delivery/cmd/mesh-delivery/approval_test.go, modules/mesh-delivery/cmd/mesh-delivery/backup_test.go, modules/mesh-delivery/cmd/mesh-delivery/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/checks_test.go, modules/mesh-delivery/cmd/mesh-delivery/covered_test.go, modules/mesh-delivery/cmd/mesh-delivery/events_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/history_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1079_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1083_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1107_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1114_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1275_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue326_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue341_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue362_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue403_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue407_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue438_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue441_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue442_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue443_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue451_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue459_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue474_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue480_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue611_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue747_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue753_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue783_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue902_test.go, modules/mesh-delivery/cmd/mesh-delivery/manifest_test.go, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/recheck_test.go, modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go, modules/mesh-delivery/cmd/mesh-delivery/table_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_source_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/times_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go

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

--- the gate: mesh-delivery, mesh-issues
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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-20T12:07:19Z 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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-20T12:07:19Z

modules the change moves:
  - mesh-delivery (removed)
  - mesh-issues (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, 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:
  - .gitignore, modules/mesh-delivery-gate/README.md, modules/mesh-delivery-gate/cmd/mesh-delivery-gate/catalogue_test.go, modules/mesh-delivery/README.md, modules/mesh-delivery/cmd/mesh-delivery/adr350_test.go, modules/mesh-delivery/cmd/mesh-delivery/approval_test.go, modules/mesh-delivery/cmd/mesh-delivery/backup_test.go, modules/mesh-delivery/cmd/mesh-delivery/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/checks_test.go, modules/mesh-delivery/cmd/mesh-delivery/covered_test.go, modules/mesh-delivery/cmd/mesh-delivery/events_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/history_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1079_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1083_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1107_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1114_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1275_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue326_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue341_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue362_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue403_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue407_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue438_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue441_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue442_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue443_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue451_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue459_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue474_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue480_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue611_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue747_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue753_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue783_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue902_test.go, modules/mesh-delivery/cmd/mesh-delivery/manifest_test.go, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/recheck_test.go, modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go, modules/mesh-delivery/cmd/mesh-delivery/table_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_source_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/times_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_test.go and modules/mesh-issues/cmd/mesh-issues/manifest_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 55150 strings of 831 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.019s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/owned	0.008s
owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
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.267s
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.231s
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	10.785s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `1c702422` Judged: head `1c7024224dd7` merged into trunk `bb0fe93bbddd`; read beside it: mesh-controller `b718d24f84b9`, mesh-controller-main `b718d24f84b9`, mesh-host `cdcba9ca7375`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery, mesh-issues) - `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-delivery, mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: .gitignore, modules/mesh-delivery-gate/README.md, modules/mesh-delivery-gate/cmd/mesh-delivery-gate/catalogue_test.go, modules/mesh-delivery/README.md, modules/mesh-delivery/cmd/mesh-delivery/adr350_test.go, modules/mesh-delivery/cmd/mesh-delivery/approval_test.go, modules/mesh-delivery/cmd/mesh-delivery/backup_test.go, modules/mesh-delivery/cmd/mesh-delivery/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/checks_test.go, modules/mesh-delivery/cmd/mesh-delivery/covered_test.go, modules/mesh-delivery/cmd/mesh-delivery/events_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/history_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1079_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1083_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1107_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1114_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1275_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue326_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue341_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue362_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue403_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue407_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue438_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue441_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue442_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue443_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue451_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue459_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue474_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue480_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue611_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue747_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue753_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue783_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue902_test.go, modules/mesh-delivery/cmd/mesh-delivery/manifest_test.go, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/recheck_test.go, modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go, modules/mesh-delivery/cmd/mesh-delivery/table_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_source_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/times_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go Run by the build seat on shanks as `build-1792498228646587095` (`builds --log build-1792498228646587095`). ``` --- the gate: mesh-delivery, mesh-issues 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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-20T12:07:19Z 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, 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-20T12:07:19Z modules the change moves: - mesh-delivery (removed) - mesh-issues (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, 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: - .gitignore, modules/mesh-delivery-gate/README.md, modules/mesh-delivery-gate/cmd/mesh-delivery-gate/catalogue_test.go, modules/mesh-delivery/README.md, modules/mesh-delivery/cmd/mesh-delivery/adr350_test.go, modules/mesh-delivery/cmd/mesh-delivery/approval_test.go, modules/mesh-delivery/cmd/mesh-delivery/backup_test.go, modules/mesh-delivery/cmd/mesh-delivery/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/checks_test.go, modules/mesh-delivery/cmd/mesh-delivery/covered_test.go, modules/mesh-delivery/cmd/mesh-delivery/events_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/history_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1079_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1083_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1107_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1114_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue1275_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue326_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue341_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue362_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue403_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue407_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue438_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue441_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue442_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue443_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue451_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue459_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue474_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue480_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue611_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue747_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue753_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue783_test.go, modules/mesh-delivery/cmd/mesh-delivery/issue902_test.go, modules/mesh-delivery/cmd/mesh-delivery/manifest_test.go, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/recheck_test.go, modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go, modules/mesh-delivery/cmd/mesh-delivery/table_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_source_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/times_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_test.go and modules/mesh-issues/cmd/mesh-issues/manifest_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 55150 strings of 831 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.019s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/owned 0.008s owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s 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.267s 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.231s testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 10.785s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools merged commit db32f8ac56 into main 2026-10-20 12:27:48 +00:00
mesh-tools deleted branch fix/1351-remove-todays-delivery-module 2026-10-20 12:27:49 +00:00
Sign in to join this conversation.
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
Projects
Clear projects
No projects
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#381