Issue 616. The installer's base step now builds mesh-tools-go, from the repository beside --tools-source (mesh-host PR for issue 616). The genesis-keeps-its-bus bed's forge serves the repositories in MESH_LAB_REPOS, and now includes mesh-tools-go. Without it, the base step would ask for git://192.0.2.30/mesh-tools-go.git and find nothing.
Tested: npm run typecheck passes. The change is to a bed's list, and the bed run is its test.
Issue 616. The installer's base step now builds mesh-tools-go, from the repository beside --tools-source (mesh-host PR for issue 616). The genesis-keeps-its-bus bed's forge serves the repositories in MESH_LAB_REPOS, and now includes mesh-tools-go. Without it, the base step would ask for git://192.0.2.30/mesh-tools-go.git and find nothing.
Tested: `npm run typecheck` passes. The change is to a bed's list, and the bed run is its test.
mesh/repo-check head d21949c04150 merged into trunk f71250c3ddd5 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…
Genesis's base step now builds mesh-tools-go beside mesh-tools, from the repository beside --tools-source;
the bed's forge served only the four repositories genesis cloned before, so the step would find nothing
there.
Deliverynovox/mesh-lab@d21949c04150 — delivered since 2026-10-13T09:23:35Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-13 09:14 (new) → proposed (announced): novox/mesh-lab#101's head announced
2026-10-13 09:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 09:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 09:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-13 09:23 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-lab@d21949c04150` — **delivered** since 2026-10-13T09:23:35Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-13 09:14 (new) → proposed (announced): novox/mesh-lab#101's head announced
- 2026-10-13 09:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 09:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 09:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-13 09:23 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
The change is minimal and correct. It adds "mesh-tools-go" to the genesis-keeps-its-bus bed's REPOS list (test/integration/genesis-keeps-its-bus.test.ts) and updates the MESH_LAB_REPOS doc comment to match, so the forge the bed starts now serves git://192.0.2.30/mesh-tools-go.git alongside the existing checkouts.
This is the correct complement to mesh-host PR #106. The bed's bootstrap call passes toolsSource: forge("mesh-tools") and no tools-go-source, so it relies on the installer's default beside-discovery (the new --tools-go-source behaviour in mesh-host #106), which looks for mesh-tools-go next to mesh-tools. This PR is what makes that lookup succeed inside the lab instead of asking the forge for a repository it never served.
npm run typecheck (both the main and test tsconfig), run niced, passes with no errors.
The PR head's own statuses already say pass: mesh/merge-gate reports "head d21949c041 merged into trunk f71250c3dd — pass: the change touches no module of the mesh's graph" and mesh/repo-check reports "head d21949c041 merged into trunk f71250c3dd — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…".
Verdict: approve at d21949c04150817a6efab365c31b8b46b27cf312
The change is minimal and correct. It adds "mesh-tools-go" to the genesis-keeps-its-bus bed's REPOS list (test/integration/genesis-keeps-its-bus.test.ts) and updates the MESH_LAB_REPOS doc comment to match, so the forge the bed starts now serves git://192.0.2.30/mesh-tools-go.git alongside the existing checkouts.
This is the correct complement to mesh-host PR #106. The bed's bootstrap call passes toolsSource: forge("mesh-tools") and no tools-go-source, so it relies on the installer's default beside-discovery (the new --tools-go-source behaviour in mesh-host #106), which looks for mesh-tools-go next to mesh-tools. This PR is what makes that lookup succeed inside the lab instead of asking the forge for a repository it never served.
npm run typecheck (both the main and test tsconfig), run niced, passes with no errors.
npm test, run niced, passes completely: 170 tests, 168 passed, 2 skipped, 0 failed.
The PR head's own statuses already say pass: mesh/merge-gate reports "head d21949c04150 merged into trunk f71250c3ddd5 — pass: the change touches no module of the mesh's graph" and mesh/repo-check reports "head d21949c04150 merged into trunk f71250c3ddd5 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…".
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.
Issue 616. The installer's base step now builds mesh-tools-go, from the repository beside --tools-source (mesh-host PR for issue 616). The genesis-keeps-its-bus bed's forge serves the repositories in MESH_LAB_REPOS, and now includes mesh-tools-go. Without it, the base step would ask for git://192.0.2.30/mesh-tools-go.git and find nothing.
Tested:
npm run typecheckpasses. The change is to a bed's list, and the bed run is its test.Delivery
novox/mesh-lab@d21949c04150— delivered since 2026-10-13T09:23:35ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: approve at
d21949c041The change is minimal and correct. It adds "mesh-tools-go" to the genesis-keeps-its-bus bed's REPOS list (test/integration/genesis-keeps-its-bus.test.ts) and updates the MESH_LAB_REPOS doc comment to match, so the forge the bed starts now serves git://192.0.2.30/mesh-tools-go.git alongside the existing checkouts.
This is the correct complement to mesh-host PR #106. The bed's bootstrap call passes toolsSource: forge("mesh-tools") and no tools-go-source, so it relies on the installer's default beside-discovery (the new --tools-go-source behaviour in mesh-host #106), which looks for mesh-tools-go next to mesh-tools. This PR is what makes that lookup succeed inside the lab instead of asking the forge for a repository it never served.
npm run typecheck (both the main and test tsconfig), run niced, passes with no errors.
npm test, run niced, passes completely: 170 tests, 168 passed, 2 skipped, 0 failed.
The PR head's own statuses already say pass: mesh/merge-gate reports "head
d21949c041merged into trunkf71250c3dd— pass: the change touches no module of the mesh's graph" and mesh/repo-check reports "headd21949c041merged into trunkf71250c3dd— pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…".