The gate takes over today's mesh-delivery: mesh-delivery-gate holds the seat, asks and merges through the parts, and today's module leaves (design 47 R3e, issues 1346-1351) #380

Merged

mesh-tools merged 15 commits from feat/r3e-the-gate into main 2026-10-20 06:49:18 +00:00

Conversation 2 Commits 15 Files Changed 85

+23704 -7

mesh-tools commented 2026-10-20 06:36:01 +00:00

Member

Copy Link

Copy Source

Design 47 release R3e (ADR 0437, ADR 0441, ADR 0450 with its 2026-10-20 correction, ADR 0449 §4, ADR 0454). Delivery group feat/r3e-the-gate with mesh-delivery and mesh-tools.

• 1346: today's module's code becomes modules/mesh-delivery-gate; it claims the seat mesh-delivery with its own buckets and reads, declaring mesh-controller.assignments and node-engine.have (ADR 0450 §6).
• 1347: silent until it holds the seat (a standing assignment of its own, none of mesh-delivery, at least one have key of mesh-delivery and every one removed, both watches current); carries today's state over once at the first holding.
• 1348: writes asks (each asking its own id: Asking, AskingID, issue 1370), reads the teller's answers, hands merges to the bridge one member at a time, moves source.main once per group, announces merged naming the answered asking.
• 1349: owed keys for statuses, views, notes and comments; a delivery's plan from plans as data, never delivery-plan; an empty check answer is an error naming the delivery.
• 1350: mesh-issues takes the gate's transition under either owner's name.
• 1351 (this half): the catalogue's test allows exactly two claimants of the seat, mesh-delivery and the gate, until the follow-up removal; README says the handover by verbs.

Today's module stays in the catalogue, unchanged (ADR 0454): the first merge check refused removing modules/mesh-delivery while novox runs it (ADR 0237 §2), and it cannot be unassigned before the merge it makes. 41f18b24 restores it byte-identical to main (copy_from at a3a9b874, 70 files). Its removal is a pull request of its own after the handover, merged by the gate. The seat pass counts only assigned claimants (ADR 0449 §4).
The carry bed test now compares only the fields the carry copies (1d9c72c4); the first try's failure was the test reading after the gate acted.

Review: three rounds by review-r3e@shanks, and a review of the merge-check fix (41f18b24..1d9c72c4) against ADR 0454. cf5c0273 only re-pins mesh-sdk to 88581d0a, the same go/ tree as ba684e54.

After delivery, the handover by verbs (no terminal): assign novox mesh-delivery-gate; seats still mesh-delivery; unassign novox mesh-delivery; push novox.

Reviewed-by: review-r3e@shanks at 1d9c72c476

Design 47 release R3e (ADR 0437, ADR 0441, ADR 0450 with its 2026-10-20 correction, ADR 0449 §4, ADR 0454). Delivery group feat/r3e-the-gate with mesh-delivery and mesh-tools. - 1346: today's module's code becomes modules/mesh-delivery-gate; it claims the seat mesh-delivery with its own buckets and reads, declaring mesh-controller.assignments and node-engine.have (ADR 0450 §6). - 1347: silent until it holds the seat (a standing assignment of its own, none of mesh-delivery, at least one have key of mesh-delivery and every one removed, both watches current); carries today's state over once at the first holding. - 1348: writes asks (each asking its own id: Asking, AskingID, issue 1370), reads the teller's answers, hands merges to the bridge one member at a time, moves source.main once per group, announces merged naming the answered asking. - 1349: owed keys for statuses, views, notes and comments; a delivery's plan from `plans` as data, never delivery-plan; an empty check answer is an error naming the delivery. - 1350: mesh-issues takes the gate's transition under either owner's name. - 1351 (this half): the catalogue's test allows exactly two claimants of the seat, mesh-delivery and the gate, until the follow-up removal; README says the handover by verbs. **Today's module stays in the catalogue, unchanged (ADR 0454):** the first merge check refused removing modules/mesh-delivery while novox runs it (ADR 0237 §2), and it cannot be unassigned before the merge it makes. 41f18b24 restores it byte-identical to main (copy_from at a3a9b874, 70 files). Its removal is a pull request of its own after the handover, merged by the gate. The seat pass counts only assigned claimants (ADR 0449 §4). The carry bed test now compares only the fields the carry copies (1d9c72c4); the first try's failure was the test reading after the gate acted. Review: three rounds by review-r3e@shanks, and a review of the merge-check fix (41f18b24..1d9c72c4) against ADR 0454. cf5c0273 only re-pins mesh-sdk to 88581d0a, the same go/ tree as ba684e54. After delivery, the handover by verbs (no terminal): assign novox mesh-delivery-gate; seats still mesh-delivery; unassign novox mesh-delivery; push novox. Reviewed-by: review-r3e@shanks at 1d9c72c476f8297cb3d656b418eaff7c46c5b976

mesh-tools added 12 commits 2026-10-20 06:36:02 +00:00

Move the delivery module to the gate: mesh-delivery-gate claims the seat with its own buckets and reads (issue 1346) 09f0b0d5ab

Take a stray key out of the gate's reads (issue 1346) a390bb40f8

Keep the gate silent until it holds the seat, and carry today's state over once when it first does (issue 1347) dd462a80e2

Ask the Approve through the gate's asks, hand merges to the bridge one member at a time, and move source.main once a group is merged (issue 1348) beafa55d97

Owe the forge its statuses, views, notes and comments as keys, read the plan from plans as data, and call an empty check answer an error (issue 1349) 6a39da5485

Hear the gate's transitions beside today's delivery module's in mesh-issues, and name the gate among the owners (issue 1350) d16fa1e052

Check that the catalogue holds no module mesh-delivery but through the names its handover needs, and say how the seat passes (issue 1351) 3b03c220ad

Hold the seat only when no assignment stands, every have key says removed and both watches are current; fix the two bed tests that failed the try (review round 1, G1) 68117bd74d

Test that the carry copies a group, a pull key and an unasked delivery byte for byte (review round 1) 1a985d68fd

Pin mesh-sdk at issue 1370's commit and read the phase removed by its name (review round 1) 67fe9a4dbe

Give each asking at unchanged heads its own router id, overwrite the ask instead of taking it away, and announce the answered asking (review round 1, G2; issue 1370) 83adc46fe0

Pin mesh-sdk to main's merge of #47 (88581d0a), the same tree as ba684e54 the review read cf5c02737b

mesh-tools commented 2026-10-20 06:36:10 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@1d9c72c476f8 — failed since 2026-10-20T06:55:42Z

Covered: covered after its failure: a later walk that contains it was delivered: plan-1792499270059758752 (novox/mesh-catalog at db32f8ac into main, done, contains its merge bb0fe93b)

Delivery plan — builds mesh-issues, new: modules/mesh-delivery-gate → novox; no bus step

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

Group feat/r3e-the-gate: novox/mesh-catalog@1d9c72c476, novox/mesh-delivery@c93954e53c, novox/mesh-tools@06e6721ed6

• composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Machines

• mesh-delivery-forge-bridge on every machine running it: sent
• mesh-delivery-indexer on every machine running it: sent
• mesh-delivery-teller on every machine running it: sent
• mesh-delivery-view on every machine running it: sent
• mesh-issues on every machine running it: sent
• mesh-tools on every machine running it: sent
• node-tools on every machine running it: sent

Transitions

• 2026-10-20 06:43 (new) → proposed (announced): novox/mesh-catalog#380's head announced
• 2026-10-20 06:45 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-20 06:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-20 06:51 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 06:51 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 06:55 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@1d9c72c476f8` — **failed** since 2026-10-20T06:55:42Z **Covered**: covered after its failure: a later walk that contains it was delivered: plan-1792499270059758752 (novox/mesh-catalog at db32f8ac into main, done, contains its merge bb0fe93b) **Delivery plan** — builds mesh-issues, new: modules/mesh-delivery-gate → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues **Group** `feat/r3e-the-gate`: novox/mesh-catalog@1d9c72c476f8, novox/mesh-delivery@c93954e53c8e, novox/mesh-tools@06e6721ed677 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-delivery-forge-bridge on every machine running it: sent - mesh-delivery-indexer on every machine running it: sent - mesh-delivery-teller on every machine running it: sent - mesh-delivery-view on every machine running it: sent - mesh-issues on every machine running it: sent - mesh-tools on every machine running it: sent - node-tools on every machine running it: sent **Transitions** - 2026-10-20 06:43 (new) → proposed (announced): novox/mesh-catalog#380's head announced - 2026-10-20 06:45 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-20 06:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-20 06:51 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 06:51 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 06:55 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools commented 2026-10-20 06:39:14 +00:00

Author

Member

Copy Link

Copy Source

Merge check at cf5c0273
Judged: head cf5c02737bdb merged into trunk a3a9b8749d12; read beside it: mesh-controller 6c2a8d62100c, mesh-controller-main 6c2a8d62100c, mesh-host 454be9b2693d, mesh-tools 7412c5b6c9c5

• mesh/merge-gate: FAIL — 3 problem(s) the change brings; the first: mesh-delivery 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: mesh-delivery (modules: mesh-delivery, mesh-issues, new:modules/mesh-delivery-gate)
• mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheGateCarriesALiveCapturesDeliveriesAndGroupsOnceOverARealBus (1.62s)

Delivery plan — builds mesh-delivery, mesh-issues, new: modules/mesh-delivery-gate → novox; no bus step

• tier 0: mesh-issues
• novox: receives mesh-issues
• read by no module's build: 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/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-delivery/README.md, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-issues/cmd/mesh-issues/delivery_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go

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

--- the gate: mesh-delivery, mesh-issues, new:modules/mesh-delivery-gate
mesh-delivery-gate: ok, 1 tool(s), invokes seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-backups-again, seat:mesh-controller.delivery-walks, seat:mesh-controller.delivery-check, seat:mesh-controller.forget-checks, seat:mesh-controller.plans, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups, pulls, asks, merges, owed, source, reads mesh-delivery.deliveries, mesh-delivery.groups, mesh-delivery.pulls, mesh-delivery-teller.answers, mesh-controller.assignments, node-engine.have
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
2 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-20T06:33:12Z 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
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
merge gate: FAIL — 3 problem(s) the change brings; the first: mesh-delivery 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: mesh-delivery
judged by controller development build against the facts of 2026-10-20T06:33:12Z

fails:
  - mesh-delivery 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: mesh-delivery
  - mesh-delivery is removed from novox/mesh-catalog, 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)
  - ygcyr's hold of mesh-delivery is not kept: recording mesh-delivery on ygcyr as the holder of mesh-delivery: mesh-delivery is not assigned to ygcyr

modules the change moves:
  - mesh-delivery (removed)
  - mesh-delivery-gate (added)
  - 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-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; the change adds 0 resource(s) and removes 2 (-archive:mesh-delivery.bundle-tools, -directory:mesh-delivery.state)
  - a machine (yvbpsm): composes

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

notes:
  - 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/delivery_test.go and modules/mesh-issues/cmd/mesh-issues/manifest_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 55150 strings of 831 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.015s
~/.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.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.250s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.013s
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.205s
testing modules/mesh-delivery-gate
--- FAIL: TestTheGateCarriesALiveCapturesDeliveriesAndGroupsOnceOverARealBus (1.62s)
    bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet
    bus_test.go:164: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved, mesh-delivery-forge-bridge.forge.**
    bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet
    bus_test.go:164: bundle: [mesh-delivery] today's state is carried: map[deliveries:8 groups:1] copied, 2 ask id(s) cleared
    bus_test.go:164: bundle: [mesh-delivery] read back 8 delivery(ies) and 1 group(s)
    bus_test.go:164: bundle: [mesh-delivery] the gate holds the seat: today's module is on no machine
    bus_test.go:164: bundle: [mesh-delivery] novox/hq@1552b0e0a3ec: its check asked of the controller as check-1 — proposed for 86h41m1s with no verdict and no check asked
    bus_test.go:899: the delivery novox_2f_hq_40_1552b0e0a3ec changed in the carry:
         got {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","check_ask":{"id":"check-1","at":"2026-10-20T06:39:06.097063845Z","by":"mesh-delivery","why":"proposed for 86h41m1s with no verdict and no check asked"},"merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z","owed":[{"kind":"note","commit":"1552b0e0a3ec","line":"2026-10-20T06:39:06Z delivery novox/hq@1552b0e0a3ec: its check asked by mesh-delivery as check-1: proposed for 86h41m1s with no verdict and no check asked","since":"2026-10-20T06:39:06.097075987Z"}]}
        want {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z"}
    bus_test.go:164: bundle: [mesh-delivery] novox/mesh-controller@0350b4e22276: its check asked of the controller as check-1 — proposed for 137h16m40s with no verdict and no check asked
FAIL
FAIL	mesh-delivery-gate/cmd/mesh-delivery-gate	12.828s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheGateCarriesALiveCapturesDeliveriesAndGroupsOnceOverARealBus (1.62s)
    bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet
    bus_test.go:164: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved, mesh-delivery-forge-bridge.forge.**
    bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet
    bus_test.go:164: bundle: [mesh-delivery] today's state is carried: map[deliveries:8 groups:1] copied, 2 ask id(s) cleared
    bus_test.go:164: bundle: [mesh-delivery] read back 8 delivery(ies) and 1 group(s)
    bus_test.go:164: bundle: [mesh-delivery] the gate holds the seat: today's module is on no machine
    bus_test.go:164: bundle: [mesh-delivery] novox/hq@1552b0e0a3ec: its check asked of the controller as check-1 — proposed for 86h41m1s with no verdict and no check asked
    bus_test.go:899: the delivery novox_2f_hq_40_1552b0e0a3ec changed in the carry:
         got {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","check_ask":{"id":"check-1","at":"2026-10-20T06:39:06.097063845Z","by":"mesh-delivery","why":"proposed for 86h41m1s with no verdict and no check asked"},"merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z","owed":[{"kind":"note","commit":"1552b0e0a3ec","line":"2026-10-20T06:39:06Z delivery novox/hq@1552b0e0a3ec: its check asked by mesh-delivery as check-1: proposed for 86h41m1s with no verdict and no check asked","since":"2026-10-20T06:39:06.097075987Z"}]}
        want {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z"}
    bus_test.go:164: bundle: [mesh-delivery] novox/mesh-controller@0350b4e22276: its check asked of the controller as check-1 — proposed for 137h16m40s with no verdict and no check asked
FAIL	mesh-delivery-gate/cmd/mesh-delivery-gate	12.828s

**Merge check** at `cf5c0273` Judged: head `cf5c02737bdb` merged into trunk `a3a9b8749d12`; read beside it: mesh-controller `6c2a8d62100c`, mesh-controller-main `6c2a8d62100c`, mesh-host `454be9b2693d`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **FAIL** — 3 problem(s) the change brings; the first: mesh-delivery 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: mesh-delivery (modules: mesh-delivery, mesh-issues, new:modules/mesh-delivery-gate) - `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheGateCarriesALiveCapturesDeliveriesAndGroupsOnceOverARealBus (1.62s) **Delivery plan** — builds mesh-delivery, mesh-issues, new: modules/mesh-delivery-gate → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: 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/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-delivery/README.md, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-issues/cmd/mesh-issues/delivery_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go Run by the build seat on ace as `build-1792478165119343870` (`builds --log build-1792478165119343870`). ``` --- the gate: mesh-delivery, mesh-issues, new:modules/mesh-delivery-gate mesh-delivery-gate: ok, 1 tool(s), invokes seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-backups-again, seat:mesh-controller.delivery-walks, seat:mesh-controller.delivery-check, seat:mesh-controller.forget-checks, seat:mesh-controller.plans, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups, pulls, asks, merges, owed, source, reads mesh-delivery.deliveries, mesh-delivery.groups, mesh-delivery.pulls, mesh-delivery-teller.answers, mesh-controller.assignments, node-engine.have 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 2 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-20T06:33:12Z 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 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 merge gate: FAIL — 3 problem(s) the change brings; the first: mesh-delivery 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: mesh-delivery judged by controller development build against the facts of 2026-10-20T06:33:12Z fails: - mesh-delivery 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: mesh-delivery - mesh-delivery is removed from novox/mesh-catalog, 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) - ygcyr's hold of mesh-delivery is not kept: recording mesh-delivery on ygcyr as the holder of mesh-delivery: mesh-delivery is not assigned to ygcyr modules the change moves: - mesh-delivery (removed) - mesh-delivery-gate (added) - 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-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; the change adds 0 resource(s) and removes 2 (-archive:mesh-delivery.bundle-tools, -directory:mesh-delivery.state) - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - 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/delivery_test.go and modules/mesh-issues/cmd/mesh-issues/manifest_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 55150 strings of 831 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.015s ~/.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.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.250s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.013s 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.205s testing modules/mesh-delivery-gate --- FAIL: TestTheGateCarriesALiveCapturesDeliveriesAndGroupsOnceOverARealBus (1.62s) bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet bus_test.go:164: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved, mesh-delivery-forge-bridge.forge.** bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet bus_test.go:164: bundle: [mesh-delivery] today's state is carried: map[deliveries:8 groups:1] copied, 2 ask id(s) cleared bus_test.go:164: bundle: [mesh-delivery] read back 8 delivery(ies) and 1 group(s) bus_test.go:164: bundle: [mesh-delivery] the gate holds the seat: today's module is on no machine bus_test.go:164: bundle: [mesh-delivery] novox/hq@1552b0e0a3ec: its check asked of the controller as check-1 — proposed for 86h41m1s with no verdict and no check asked bus_test.go:899: the delivery novox_2f_hq_40_1552b0e0a3ec changed in the carry: got {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","check_ask":{"id":"check-1","at":"2026-10-20T06:39:06.097063845Z","by":"mesh-delivery","why":"proposed for 86h41m1s with no verdict and no check asked"},"merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z","owed":[{"kind":"note","commit":"1552b0e0a3ec","line":"2026-10-20T06:39:06Z delivery novox/hq@1552b0e0a3ec: its check asked by mesh-delivery as check-1: proposed for 86h41m1s with no verdict and no check asked","since":"2026-10-20T06:39:06.097075987Z"}]} want {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z"} bus_test.go:164: bundle: [mesh-delivery] novox/mesh-controller@0350b4e22276: its check asked of the controller as check-1 — proposed for 137h16m40s with no verdict and no check asked FAIL FAIL mesh-delivery-gate/cmd/mesh-delivery-gate 12.828s FAIL --- what failed, picked from the whole of its output (the whole is in the build's log) --- FAIL: TestTheGateCarriesALiveCapturesDeliveriesAndGroupsOnceOverARealBus (1.62s) bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet bus_test.go:164: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved, mesh-delivery-forge-bridge.forge.** bus_test.go:164: bundle: [mesh-delivery] cannot tell who has the seat yet: the watches of the assignments and the have keys have not both delivered their current values yet bus_test.go:164: bundle: [mesh-delivery] today's state is carried: map[deliveries:8 groups:1] copied, 2 ask id(s) cleared bus_test.go:164: bundle: [mesh-delivery] read back 8 delivery(ies) and 1 group(s) bus_test.go:164: bundle: [mesh-delivery] the gate holds the seat: today's module is on no machine bus_test.go:164: bundle: [mesh-delivery] novox/hq@1552b0e0a3ec: its check asked of the controller as check-1 — proposed for 86h41m1s with no verdict and no check asked bus_test.go:899: the delivery novox_2f_hq_40_1552b0e0a3ec changed in the carry: got {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","check_ask":{"id":"check-1","at":"2026-10-20T06:39:06.097063845Z","by":"mesh-delivery","why":"proposed for 86h41m1s with no verdict and no check asked"},"merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z","owed":[{"kind":"note","commit":"1552b0e0a3ec","line":"2026-10-20T06:39:06Z delivery novox/hq@1552b0e0a3ec: its check asked by mesh-delivery as check-1: proposed for 86h41m1s with no verdict and no check asked","since":"2026-10-20T06:39:06.097075987Z"}]} want {"id":"novox/hq@1552b0e0a3ec","repository":"novox/hq","commit":"1552b0e0a3ec","number":384,"base":"main","state":"proposed","since":"2026-10-16T15:58:05Z","created":"2026-10-16T15:58:05Z","merged_at":"0001-01-01T00:00:00Z","let_go":"0001-01-01T00:00:00Z"} bus_test.go:164: bundle: [mesh-delivery] novox/mesh-controller@0350b4e22276: its check asked of the controller as check-1 — proposed for 137h16m40s with no verdict and no check asked FAIL mesh-delivery-gate/cmd/mesh-delivery-gate 12.828s ```

mesh-tools added 1 commit 2026-10-20 06:41:50 +00:00

Keep today's module mesh-delivery in the catalogue, unchanged: its removal follows the handover as a pull request of its own 41f18b2452

mesh-tools added 1 commit 2026-10-20 06:43:19 +00:00

Let the catalogue hold the gate and today's module as the two claimants of the seat, and say the removal follows the handover (issue 1351) 1f193f6d01

mesh-tools added 1 commit 2026-10-20 06:43:29 +00:00

Compare in the carry bed what the carry copies, not what the gate does after it; keep today's module among mesh-issues' owners 1d9c72c476

mesh-tools merged commit bb0fe93bbd into main 2026-10-20 06:49:18 +00:00

mesh-tools deleted branch feat/r3e-the-gate 2026-10-20 06:49:18 +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

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#380