Carry the controller's grant to ask mesh-delivery for its delivery times in the installer's first user list (hq ADR 0282, issue 382) #77

Merged
mesh-admin merged 1 commits from feat/382-carry-times-grant into main 2026-10-10 18:39:44 +00:00
Contributor

mesh-controller #206 adds mesh.seat.mesh-delivery.tool.times to the controller's bus grant (probe D16 reads delivery times). mesh-controller's TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose compares the controller's derived grant with this template's first user list, so the template must carry the same subject or a mesh raised from it would refuse the controller that question. One subject added after mesh.seat.mesh-delivery.tool.stop, as b196cab did for stalled and close.

Order: this merges before mesh-controller #206 is rechecked (its check reads mesh-host main beside it).

mesh-controller #206 adds `mesh.seat.mesh-delivery.tool.times` to the controller's bus grant (probe D16 reads delivery times). mesh-controller's TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose compares the controller's derived grant with this template's first user list, so the template must carry the same subject or a mesh raised from it would refuse the controller that question. One subject added after `mesh.seat.mesh-delivery.tool.stop`, as b196cab did for stalled and close. Order: this merges before mesh-controller #206 is rechecked (its check reads mesh-host main beside it).
mesh-admin added 1 commit 2026-10-10 18:35:34 +00:00
Carry the controller's grant to ask the delivery's owner for its delivery times in the installer's first user list (hq ADR 0282)
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
212a3cc113
Author
Contributor

Delivery novox/mesh-host@212a3cc11309 — delivered since 2026-10-10T18:44:58Z

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

Machines

  • mesh-host on ace: passed — healthy 3 times over 2m22s
  • mesh-host on the rest running it: sent

Transitions

  • 2026-10-10 18:35 (new) → proposed (announced): novox/mesh-host#77's head announced
  • 2026-10-10 18:39 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 18:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 18:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 18:41 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-10 18:44 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-host@212a3cc11309` — **delivered** since 2026-10-10T18:44:58Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Machines** - mesh-host on ace: passed — healthy 3 times over 2m22s - mesh-host on the rest running it: sent **Transitions** - 2026-10-10 18:35 (new) → proposed (announced): novox/mesh-host#77's head announced - 2026-10-10 18:39 proposed → checked (checked): the verdict names this commit - 2026-10-10 18:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 18:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 18:41 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-10 18:44 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`.
Author
Contributor

Merge check at 212a3cc1

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

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

--- the gate: mesh-host
mesh-host: ok
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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T17:55:04Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-10T17:55:04Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.015s
ok  	github.com/novox/mesh-host/cmd/mesh-host	6.970s
ok  	github.com/novox/mesh-host/examples	1.018s
ok  	github.com/novox/mesh-host/internal/accounts	2.376s
ok  	github.com/novox/mesh-host/internal/apply	24.457s
ok  	github.com/novox/mesh-host/internal/bootstrap	2.898s
ok  	github.com/novox/mesh-host/internal/bundle	1.025s
ok  	github.com/novox/mesh-host/internal/declaration	1.068s
ok  	github.com/novox/mesh-host/internal/firewall	1.840s
ok  	github.com/novox/mesh-host/internal/identity	1.612s
ok  	github.com/novox/mesh-host/internal/image	1.031s
ok  	github.com/novox/mesh-host/internal/inventory	1.025s
ok  	github.com/novox/mesh-host/internal/link	10.479s
ok  	github.com/novox/mesh-host/internal/liveness	2.458s
ok  	github.com/novox/mesh-host/internal/meshcli	1.344s
ok  	github.com/novox/mesh-host/internal/network	1.047s
ok  	github.com/novox/mesh-host/internal/outward	1.016s
ok  	github.com/novox/mesh-host/internal/profile	1.482s
ok  	github.com/novox/mesh-host/internal/reachable	1.011s
ok  	github.com/novox/mesh-host/internal/store	1.854s
ok  	github.com/novox/mesh-host/internal/system	1.012s
ok  	github.com/novox/mesh-host/internal/tunnel	1.015s
ok  	github.com/novox/mesh-host/internal/units	1.008s
ok  	github.com/novox/mesh-host/internal/upgrade	1.753s
ok  	github.com/novox/mesh-host/internal/witness	37.102s
ok  	github.com/novox/mesh-host/packaging	1.009s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.008s
**Merge check** at `212a3cc1` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host Run by the build seat on novox as `build-1791657343075653614` (`builds --log build-1791657343075653614`). ``` --- the gate: mesh-host mesh-host: ok 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T17:55:04Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-10T17:55:04Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-host --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.015s ok github.com/novox/mesh-host/cmd/mesh-host 6.970s ok github.com/novox/mesh-host/examples 1.018s ok github.com/novox/mesh-host/internal/accounts 2.376s ok github.com/novox/mesh-host/internal/apply 24.457s ok github.com/novox/mesh-host/internal/bootstrap 2.898s ok github.com/novox/mesh-host/internal/bundle 1.025s ok github.com/novox/mesh-host/internal/declaration 1.068s ok github.com/novox/mesh-host/internal/firewall 1.840s ok github.com/novox/mesh-host/internal/identity 1.612s ok github.com/novox/mesh-host/internal/image 1.031s ok github.com/novox/mesh-host/internal/inventory 1.025s ok github.com/novox/mesh-host/internal/link 10.479s ok github.com/novox/mesh-host/internal/liveness 2.458s ok github.com/novox/mesh-host/internal/meshcli 1.344s ok github.com/novox/mesh-host/internal/network 1.047s ok github.com/novox/mesh-host/internal/outward 1.016s ok github.com/novox/mesh-host/internal/profile 1.482s ok github.com/novox/mesh-host/internal/reachable 1.011s ok github.com/novox/mesh-host/internal/store 1.854s ok github.com/novox/mesh-host/internal/system 1.012s ok github.com/novox/mesh-host/internal/tunnel 1.015s ok github.com/novox/mesh-host/internal/units 1.008s ok github.com/novox/mesh-host/internal/upgrade 1.753s ok github.com/novox/mesh-host/internal/witness 37.102s ok github.com/novox/mesh-host/packaging 1.009s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.008s ```
mesh-admin merged commit 9d8aa9d6f0 into main 2026-10-10 18:39:44 +00:00
mesh-admin deleted branch feat/382-carry-times-grant 2026-10-10 18:39:44 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-host#77