modules/lab/tools/runs.ts: a run's MESH_LAB_BUNDLE now names mesh-host/examples/foundation-first-node.lock.
Why
mesh-host #96 (issue 146, ADR 0331 §2) left one genesis bundle and deleted foundation-first-node-nats.lock, so every lab run pointed at a file that is gone.
How it was tested
MESH_CHECK_MODULES=lab sh merge-check-typescript.sh with a node_modules holding TypeScript, @types/node and mesh-sdk main built from source: modules/lab type-checks. The lab module has no tests of its own, and the check says "NOT TESTED".
MESH_CHECK_MODULES=lab sh merge-check.sh: pass. No controller was built beside the check, so the manifests were not read by one; the build seat's gate does that.
Fixes the catalogue's part of issue 146's fallout.
## What
`modules/lab/tools/runs.ts`: a run's `MESH_LAB_BUNDLE` now names `mesh-host/examples/foundation-first-node.lock`.
## Why
mesh-host #96 (issue 146, ADR 0331 §2) left one genesis bundle and deleted `foundation-first-node-nats.lock`, so every lab run pointed at a file that is gone.
## How it was tested
- `MESH_CHECK_MODULES=lab sh merge-check-typescript.sh` with a node_modules holding TypeScript, @types/node and mesh-sdk main built from source: modules/lab type-checks. The lab module has no tests of its own, and the check says "NOT TESTED".
- `MESH_CHECK_MODULES=lab sh merge-check.sh`: pass. No controller was built beside the check, so the manifests were not read by one; the build seat's gate does that.
Fixes the catalogue's part of issue 146's fallout.
mesh/merge-gate head 84911b94f3be merged into trunk 8f80cd471634 — pass: builds lab → shanks; no bus step; every machine composes with the change as it did…
mesh/repo-check head 84911b94f3be merged into trunk 8f80cd471634 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh-host now carries one genesis bundle, foundation-first-node.lock; the -nats one the
lab's runs named is deleted, so every run would have raised from a file that is gone.
Deliverynovox/mesh-catalog@84911b94f3be — delivered since 2026-10-12T23:23:56Z
Delivery plan — builds lab → shanks; no bus step
tier 0: lab
shanks: receives lab
lab keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine
Machines
lab on shanks: passed — healthy 1 times over 43s
lab on the rest running it: sent
Transitions
2026-10-12 23:18 (new) → proposed (announced): novox/mesh-catalog#261's head announced
2026-10-12 23:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-12 23:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 23:22 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 23:22 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-12 23:23 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@84911b94f3be` — **delivered** since 2026-10-12T23:23:56Z
**Delivery plan** — builds lab → shanks; no bus step
- tier 0: lab
- shanks: receives lab
- lab keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine
**Machines**
- lab on shanks: passed — healthy 1 times over 43s
- lab on the rest running it: sent
**Transitions**
- 2026-10-12 23:18 (new) → proposed (announced): novox/mesh-catalog#261's head announced
- 2026-10-12 23:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-12 23:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 23:22 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 23:22 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-12 23:23 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`.
The diff is one line in modules/lab/tools/runs.ts (MESH_LAB_BUNDLE now names mesh-host/examples/foundation-first-node.lock), on top of main 8f80cd4 (the merge base is main's head). Nothing else changes.
The new path exists on mesh-host main (7a41e12): examples/foundation-first-node.lock, blob 289e3e2. foundation-first-node-nats.lock is gone there.
No other reference to foundation-first-node-nats remains anywhere in this repository at this head (grep, no matches).
Statuses at this head when I read them: mesh/merge-gate pending (building on novox), mesh/delivery pending, mesh/repo-check not yet posted. Merge only after both required checks are green and read.
Verdict: approve at 84911b94f3be15ff8a0b56363cdf6f1434442161
What I checked:
1. The diff is one line in modules/lab/tools/runs.ts (MESH_LAB_BUNDLE now names mesh-host/examples/foundation-first-node.lock), on top of main 8f80cd4 (the merge base is main's head). Nothing else changes.
2. The new path exists on mesh-host main (7a41e12): examples/foundation-first-node.lock, blob 289e3e2. foundation-first-node-nats.lock is gone there.
3. No other reference to foundation-first-node-nats remains anywhere in this repository at this head (grep, no matches).
Statuses at this head when I read them: mesh/merge-gate pending (building on novox), mesh/delivery pending, mesh/repo-check not yet posted. Merge only after both required checks are green and read.
Merge check at 84911b94
Judged: head 84911b94f3be merged into trunk 8f80cd471634; read beside it: mesh-controller cbac703e817d, mesh-controller-main cbac703e817d, mesh-host 7a41e120635b, mesh-tools 954e1a53eef9
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: lab)
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 lab → shanks; no bus step
tier 0: lab
shanks: receives lab
lab keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine
Run by the build seat on novox as build-1791847102342877490 (builds --log build-1791847102342877490).
--- the gate: lab
lab: ok, keeps work (cache); WARNING: runtime-env ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T23:09:52Z 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-12T23:09:52Z
modules the change moves:
- lab (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 1 module(s) in 1 tier(s): lab
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 45130 strings of 705 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.007s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 67, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.273s
modules/lab is TypeScript: merge-check-typescript.sh type-checks and tests it
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/lab (TypeScript)
NOT TESTED: modules/lab is TypeScript and has no tests of its own
**Merge check** at `84911b94`
Judged: head `84911b94f3be` merged into trunk `8f80cd471634`; read beside it: mesh-controller `cbac703e817d`, mesh-controller-main `cbac703e817d`, mesh-host `7a41e120635b`, mesh-tools `954e1a53eef9`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: lab)
- `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 lab → shanks; no bus step
- tier 0: lab
- shanks: receives lab
- lab keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine
Run by the build seat on novox as `build-1791847102342877490` (`builds --log build-1791847102342877490`).
```
--- the gate: lab
lab: ok, keeps work (cache); WARNING: runtime-env ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T23:09:52Z 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-12T23:09:52Z
modules the change moves:
- lab (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 1 module(s) in 1 tier(s): lab
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 45130 strings of 705 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.007s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 67, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.273s
modules/lab is TypeScript: merge-check-typescript.sh type-checks and tests it
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/lab (TypeScript)
NOT TESTED: modules/lab is TypeScript and has no tests of its own
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
modules/lab/tools/runs.ts: a run'sMESH_LAB_BUNDLEnow namesmesh-host/examples/foundation-first-node.lock.Why
mesh-host #96 (issue 146, ADR 0331 §2) left one genesis bundle and deleted
foundation-first-node-nats.lock, so every lab run pointed at a file that is gone.How it was tested
MESH_CHECK_MODULES=lab sh merge-check-typescript.shwith a node_modules holding TypeScript, @types/node and mesh-sdk main built from source: modules/lab type-checks. The lab module has no tests of its own, and the check says "NOT TESTED".MESH_CHECK_MODULES=lab sh merge-check.sh: pass. No controller was built beside the check, so the manifests were not read by one; the build seat's gate does that.Fixes the catalogue's part of issue 146's fallout.
Delivery
novox/mesh-catalog@84911b94f3be— delivered since 2026-10-12T23:23:56ZDelivery plan — builds lab → shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: approve at
84911b94f3What I checked:
8f80cd4(the merge base is main's head). Nothing else changes.Statuses at this head when I read them: mesh/merge-gate pending (building on novox), mesh/delivery pending, mesh/repo-check not yet posted. Merge only after both required checks are green and read.
Merge check at
84911b94Judged: head
84911b94f3bemerged into trunk8f80cd471634; read beside it: mesh-controllercbac703e817d, mesh-controller-maincbac703e817d, mesh-host7a41e120635b, mesh-tools954e1a53eef9mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: lab)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 lab → shanks; no bus step
Run by the build seat on novox as
build-1791847102342877490(builds --log build-1791847102342877490).