mesh-delivery: end a merge that moves nothing or that a later merge delivered, and lift a group hold its check answered (hq issues 319, 316) #150

Merged
mesh-admin merged 5 commits from fix/319-316-covered-and-lifted into main 2026-10-09 07:30:16 +00:00
Contributor

Builds hq ADR 0270 (proposed, hq PR for 0270/0271).

Why. Fifteen deliveries were held for a person with no right answer: hq merges that build nothing, merges that only add a module the controller sends nowhere, controller merges whose change a later delivered walk of the same trunk already carried, and a group member held because its composed check had not answered yet. Only stop ended them, which sets mesh/delivery to error on a change that runs.

What.

  • MovesNothing() no longer counts Plan.New. A merged delivery whose plan moves nothing goes to delivered from proposed, checked, rejected or held (row before merged unchecked).
  • New final state covered: every module its plan moves was sent by a finished walk of a delivered delivery of the same repository and trunk, merged after it. Read from the walk's record (WalkSeen.Sent, new) or the machine steps already kept. Shown as success covered: delivered with … (merged as …, walk …). A group counts it as delivered.
  • A group member waits in published while its composed check is asked and unanswered; a member held for it is lifted back to published when it passes or warns for the heads that merged and its own walk is still open.
  • Held deliveries are read every tick, so the ones held today end by themselves after the rollout; a restart moves nothing again.

Tests (fail first, then pass): covered_test.go, table tests for every variation; the table's own tests cover the new rows.

Independent of mesh-controller's fix/336 PR. Merge after hq ADR 0270 is accepted.

Builds hq ADR 0270 (proposed, hq PR for 0270/0271). **Why.** Fifteen deliveries were held for a person with no right answer: hq merges that build nothing, merges that only add a module the controller sends nowhere, controller merges whose change a later delivered walk of the same trunk already carried, and a group member held because its composed check had not answered yet. Only `stop` ended them, which sets `mesh/delivery` to error on a change that runs. **What.** - `MovesNothing()` no longer counts `Plan.New`. A merged delivery whose plan moves nothing goes to `delivered` from proposed, checked, rejected or held (row before *merged unchecked*). - New final state `covered`: every module its plan moves was sent by a finished walk of a delivered delivery of the same repository and trunk, merged after it. Read from the walk's record (`WalkSeen.Sent`, new) or the machine steps already kept. Shown as `success covered: delivered with … (merged as …, walk …)`. A group counts it as delivered. - A group member waits in `published` while its composed check is asked and unanswered; a member held for it is *lifted* back to `published` when it passes or warns for the heads that merged and its own walk is still open. - Held deliveries are read every tick, so the ones held today end by themselves after the rollout; a restart moves nothing again. **Tests** (fail first, then pass): `covered_test.go`, table tests for every variation; the table's own tests cover the new rows. Independent of mesh-controller's fix/336 PR. Merge after hq ADR 0270 is accepted.
Author
Contributor

Delivery novox/mesh-catalog@7e510998d9e6 — delivered since 2026-10-09T07:34:00Z

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

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

Machines

  • gitea on novox: passed — healthy 3 times over 2m28s
  • mesh-delivery on novox: passed — judged with gitea: healthy 3 times over 2m28s
  • gitea on the rest running it: sent
  • mesh-delivery on the rest running it: sent

Transitions

  • 2026-10-09 01:29 (new) → proposed (announced): novox/mesh-catalog#150's head announced
  • 2026-10-09 01:31 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 01:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 07:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-09 07:30 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
  • 2026-10-09 07:34 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@7e510998d9e6` — **delivered** since 2026-10-09T07:34:00Z **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery **Machines** - gitea on novox: passed — healthy 3 times over 2m28s - mesh-delivery on novox: passed — judged with gitea: healthy 3 times over 2m28s - gitea on the rest running it: sent - mesh-delivery on the rest running it: sent **Transitions** - 2026-10-09 01:29 (new) → proposed (announced): novox/mesh-catalog#150's head announced - 2026-10-09 01:31 proposed → checked (checked): the verdict names this commit - 2026-10-09 01:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 07:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 07:30 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-09 07:34 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at 2d1d4bf9

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

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

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

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

--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, keeps state deliveries, groups
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-09T00:26:57Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T00:26:57Z

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

a merge would rebuild 1 module(s) in 1 tier(s): mesh-delivery
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 33712 strings of 600 files
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: 70, as kept
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	1.211s
**Merge check** at `2d1d4bf9` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery Run by the build seat on ace as `build-1791506086913852967` (`builds --log build-1791506086913852967`). ``` --- the gate: mesh-delivery mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, keeps state deliveries, groups 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-09T00:26:57Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-09T00:26:57Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-delivery --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 33712 strings of 600 files 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: 70, as kept testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 1.211s ```
Author
Contributor

Merge check at 6327f297

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

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

  • tier 0: gitea, mesh-delivery
  • novox: receives gitea, mesh-delivery
  • gitea provides npm-package-registry, git: its consumers are sent again after it
  • gitea keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791507446691862913 (builds --log build-1791507446691862913).

--- the gate: gitea, mesh-delivery
gitea: ok, keeps data (valuable); WARNING: server stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, keeps state deliveries, groups
long-running resources without health: 1
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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:53:55Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T00:53:55Z

modules the change moves:
  - gitea (changed)
  - mesh-delivery (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-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 2 module(s) in 1 tier(s): gitea, mesh-delivery
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 33743 strings of 600 files
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: 70, as kept
testing modules/gitea
ok  	gitea/cmd/npm-registry	1.871s
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	1.237s
**Merge check** at `6327f297` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea, mesh-delivery) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds gitea, mesh-delivery → novox; no bus step - tier 0: gitea, mesh-delivery - novox: receives gitea, mesh-delivery - gitea provides npm-package-registry, git: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791507446691862913` (`builds --log build-1791507446691862913`). ``` --- the gate: gitea, mesh-delivery gitea: ok, keeps data (valuable); WARNING: server stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, keeps state deliveries, groups long-running resources without health: 1 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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T00:53:55Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-09T00:53:55Z modules the change moves: - gitea (changed) - mesh-delivery (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-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 2 module(s) in 1 tier(s): gitea, mesh-delivery --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 33743 strings of 600 files 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: 70, as kept testing modules/gitea ok gitea/cmd/npm-registry 1.871s testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 1.237s ```
mesh-admin changed target branch from main to check/typescript-modules-tested 2026-10-09 01:23:29 +00:00
Author
Contributor

Merge check at 0bd50fce

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

  • tier 0: mesh-delivery
  • novox: receives mesh-delivery
  • read by no module's build: modules/gitea/checks.ts, modules/gitea/client.ts, modules/gitea/test/checks.test.ts, modules/gitea/test/token.test.ts, modules/gitea/tools/index.ts

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

--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, keeps state deliveries, groups
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-09T01:13:55Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T01:13:55Z

modules the change moves:
  - gitea (changed)
  - mesh-delivery (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-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 2 module(s) in 1 tier(s): gitea, mesh-delivery
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 34076 strings of 601 files
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: 70, as kept
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	1.328s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `0bd50fce` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery) - `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 → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery - read by no module's build: modules/gitea/checks.ts, modules/gitea/client.ts, modules/gitea/test/checks.test.ts, modules/gitea/test/token.test.ts, modules/gitea/tools/index.ts Run by the build seat on novox as `build-1791509018523515707` (`builds --log build-1791509018523515707`). ``` --- the gate: mesh-delivery mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, keeps state deliveries, groups 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-09T01:13:55Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-09T01:13:55Z modules the change moves: - gitea (changed) - mesh-delivery (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-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 2 module(s) in 1 tier(s): gitea, mesh-delivery --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 34076 strings of 601 files 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: 70, as kept testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 1.328s --- its merge-check-typescript.sh (typescript toolchain) ```
Author
Contributor

Merge check at 7e510998

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

  • tier 0: mesh-delivery
  • novox: receives mesh-delivery
  • read by no module's build: modules/gitea/checks.ts, modules/gitea/client.ts, modules/gitea/test/checks.test.ts, modules/gitea/test/token.test.ts, modules/gitea/tools/index.ts

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

--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, keeps state deliveries, groups
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-09T01:23:55Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T01:23:55Z

modules the change moves:
  - gitea (changed)
  - mesh-delivery (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-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 2 module(s) in 1 tier(s): gitea, mesh-delivery
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 34076 strings of 601 files
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: 70, as kept
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	1.324s
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/gitea (TypeScript)
testing modules/gitea (TypeScript)
✔ the newest status of each context is kept, with what it said, when and by whom (13.566003ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.499638ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.222353ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.67633ms)
✔ a note line is appended once, as the forge's user, in its own repository (6.04231ms)
✔ a note that cannot be written is said, never read as written (0.350635ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.524808ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (23.223656ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.386606ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (11.164146ms)
✔ a lookup the forge refuses is thrown, not read as no module (3.833768ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (5.722206ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.291875ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (4.187183ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.911423ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.66778ms)
✔ no verdict sets warning on a required check; only a person's decision fails (0.787412ms)
✔ a commit status is set on the commit, under the merge check's context (33.304717ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.453626ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (28.83882ms)
✔ second start: reuses the kept token, mints nothing (17.270858ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (18.381224ms)
✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (25.498651ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (17.773494ms)
✔ concurrent first calls share one mint (10.265553ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (12.588628ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (1.068756ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (21.49116ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (3.585824ms)
✔ nothing to mint with and no token: the client says what is missing (0.217373ms)
[gitea] no tools — no Gitea token, and nothing to mint one with — set MESH_GITEA_TOKEN, or MESH_GITEA_ADMIN_USER, MESH_GITEA_ADMIN_PASSWORD_FILE, MESH_GITEA_STATE_DIR
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-admin" (write:repository, write:issue, read:user, write:admin), kept at /tmp/gitea-5n9gfk/state/token
✔ the tools register once there is a way to a token, and the first call mints it (9.747495ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-admin" (write:repository, write:issue, read:user, write:admin), kept at /tmp/gitea-LtLpOm/state/token
✔ a pull request can be closed, read and cleaned up through the tools (22.885031ms)
ℹ tests 32
ℹ suites 0
ℹ pass 32
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 326.917495
**Merge check** at `7e510998` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery) - `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 → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery - read by no module's build: modules/gitea/checks.ts, modules/gitea/client.ts, modules/gitea/test/checks.test.ts, modules/gitea/test/token.test.ts, modules/gitea/tools/index.ts Run by the build seat on shanks as `build-1791509353373266855` (`builds --log build-1791509353373266855`). ``` --- the gate: mesh-delivery mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, keeps state deliveries, groups 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-09T01:23:55Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-09T01:23:55Z modules the change moves: - gitea (changed) - mesh-delivery (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-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 2 module(s) in 1 tier(s): gitea, mesh-delivery --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 34076 strings of 601 files 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: 70, as kept testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 1.324s --- its merge-check-typescript.sh (typescript toolchain) type-checking modules/gitea (TypeScript) testing modules/gitea (TypeScript) ✔ the newest status of each context is kept, with what it said, when and by whom (13.566003ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.499638ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.222353ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.67633ms) ✔ a note line is appended once, as the forge's user, in its own repository (6.04231ms) ✔ a note that cannot be written is said, never read as written (0.350635ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.524808ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (23.223656ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.386606ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (11.164146ms) ✔ a lookup the forge refuses is thrown, not read as no module (3.833768ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (5.722206ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.291875ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (4.187183ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.911423ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.66778ms) ✔ no verdict sets warning on a required check; only a person's decision fails (0.787412ms) ✔ a commit status is set on the commit, under the merge check's context (33.304717ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.453626ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (28.83882ms) ✔ second start: reuses the kept token, mints nothing (17.270858ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (18.381224ms) ✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (25.498651ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (17.773494ms) ✔ concurrent first calls share one mint (10.265553ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (12.588628ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (1.068756ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (21.49116ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (3.585824ms) ✔ nothing to mint with and no token: the client says what is missing (0.217373ms) [gitea] no tools — no Gitea token, and nothing to mint one with — set MESH_GITEA_TOKEN, or MESH_GITEA_ADMIN_USER, MESH_GITEA_ADMIN_PASSWORD_FILE, MESH_GITEA_STATE_DIR [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-admin" (write:repository, write:issue, read:user, write:admin), kept at /tmp/gitea-5n9gfk/state/token ✔ the tools register once there is a way to a token, and the first call mints it (9.747495ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-admin" (write:repository, write:issue, read:user, write:admin), kept at /tmp/gitea-LtLpOm/state/token ✔ a pull request can be closed, read and cleaned up through the tools (22.885031ms) ℹ tests 32 ℹ suites 0 ℹ pass 32 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 326.917495 ```
mesh-admin changed target branch from check/typescript-modules-tested to main 2026-10-09 07:29:36 +00:00
mesh-admin added 5 commits 2026-10-09 07:29:36 +00:00
End a merge that moves nothing or that a later merge delivered, and lift a group hold its check answered (hq issues 319, 316)
mesh/merge-gate pass: builds mesh-delivery → novox; 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 superseded: a newer head of the same pull request
2d1d4bf988
A held delivery asked a person a question with no right answer: four hq merges that build nothing,
merges adding a module the controller sends nowhere, controller merges whose change a later walk of
the same trunk already delivered, and a group member held because its composed check had not yet
answered. Only stop could end them, which marks a delivered change as an error on its pull request.

- A merge whose plan moves no module (nothing, or only a new module sent nowhere) is delivered at once.
- A new final state, covered: every module a merge moves was sent by a finished walk of a later merge
  into the same trunk, which contains it. Shown as success on the pull request; a group counts it as
  delivered.
- A group member waits published while its composed check is asked and unanswered, and a member held
  for it is lifted back to published once it passes for the heads that merged.

Read again each tick, so the deliveries already held end by themselves after the rollout.
Cover a held merge only when the forge says a later delivered merge contains it (review of #150)
mesh/merge-gate pass: builds gitea, mesh-delivery → novox; 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 superseded: a newer head of the same pull request
6327f297ea
Merge order on a protected trunk was the whole proof; the review asked for ancestry. The gitea module
gains gitea_contains, a read-only compare of two commits (total_commits 0 is contained), and mesh-delivery
asks it once per pair, off the lock like its plan ask, keeping the answer on the delivery. A forge that
cannot say leaves the merge held, not covered. Merge order stays the cheap first filter.

A later delivery now carries a module only when its own check passed (so a merge held without a passing
check is closed only by one that passed), its walk is of its own merge commit on the same trunk, and its
steps say the module reached every machine running it, not one. The words say what is known: a later
merge that contains it was delivered.
The forge module's tool list test names the statuses and contains tools
mesh/merge-gate pass: builds mesh-delivery → novox; 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
0bd50fce0a
It had not been run before a merge: its expected list lacked gitea_commit_statuses since that tool came,
and now gitea_contains. The catalogue's TypeScript check, merged in from #151, runs it.
Merge branch 'check/typescript-modules-tested' into fix/319-316-covered-and-lifted
mesh/merge-gate pass: builds mesh-delivery → novox; 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
7e510998d9
mesh-admin merged commit 73eef94101 into main 2026-10-09 07:30:16 +00:00
mesh-admin deleted branch fix/319-316-covered-and-lifted 2026-10-09 07:30:16 +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-catalog#150