jochen c6a9c52dc7 Install each lab checkout where its lock file is, check out mesh-tools-go, and have lab_check catch both (hq issue 624) ...

lab_run ran npm ci at the root of mesh-sdk, mesh-tools and mesh-lab; mesh-tools keeps its package in
node-tools/ with no lock file at its root, so every run failed at its setup in nine seconds. A run now
installs (and, for the SDK and the base, builds) where a package-lock.json is: the root, or each
directory one level down; a package.json with no lock file fails the run naming it. It checks out
mesh-tools-go, which genesis builds since issue 616, and tells the beds where its checkouts are
(MESH_LAB_REPOS). lab_check asks the forge for every repository a run clones and applies the same install
rule to the ones it installs, so a run's setup failure is found before a run.

2026-10-13 11:55:01 +02:00

..

test

Install each lab checkout where its lock file is, check out mesh-tools-go, and have lab_check catch both (hq issue 624)

2026-10-13 11:55:01 +02:00

tools

Install each lab checkout where its lock file is, check out mesh-tools-go, and have lab_check catch both (hq issue 624)

2026-10-13 11:55:01 +02:00

module.json

Declare every module's data; the backup holder measures it (hq ADR 0233)

2026-10-06 16:47:49 +02:00

package.json

Install each lab checkout where its lock file is, check out mesh-tools-go, and have lab_check catch both (hq issue 624)

2026-10-13 11:55:01 +02:00

tsconfig.json

lab: the lab as a module, running beds when the mesh asks

2026-10-02 14:15:42 +02:00