jochen 8ad121d5c3 lab: take the registry's address only from the forge's own host, built from the parsed URL (hq issue 624, review of #275) ...

What the registry answers may come over plain HTTP, so it must not choose
where packages come from, nor reach the run's npm configuration as a raw
string.

2026-10-13 16:26:48 +02:00

..

test

lab: take the registry's address only from the forge's own host, built from the parsed URL (hq issue 624, review of #275)

2026-10-13 16:26:48 +02:00

tools

lab: take the registry's address only from the forge's own host, built from the parsed URL (hq issue 624, review of #275)

2026-10-13 16:26:48 +02:00

module.json

lab: name the bound credential in the tools bundle's env, and skip the locked-tree test as root (hq issue 624, reviews 198, 199)

2026-10-13 14:51:18 +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