Fixes issue 624 (the lab module's lab_run fails at setup), its third setup failure.
What happened
Lab run run-2026-10-13T13-15-26-634Z on shanks (mesh-tools at the branch of #33, now merged) installed mesh-sdk, then stopped in mesh-tools' node-tools: npm error code EALLOWREMOTE … Refusing to fetch "@novox/mesh-sdk@https://git.novox.be/api/packages/novox/npm/%40novox%2Fmesh-sdk/-/0.1.14/mesh-sdk-0.1.14.tgz"
Cause (seen, not guessed)
shanks runs npm 12.2.0 (Arch package npm 12.2.0-1, node 26.10.0), which the lab's npm package declaration installs. No npmrc on shanks sets allow-remote: the debug log loads only npm's builtin npmrc (globalconfig=/etc/npmrc, which does not exist), the run's .npmrc, and a node-tools .npmrc that does not exist. npm 12's own default for allow-remote is none (its config definitions: "As of npm 12 the default is none. Tarballs that share a hostname with the configured registry … are still installed normally").
arborist's reify lets a locked tarball through only when its resolved origin and path are the configured scope registry's (#isRegistryResolvedTarball); anything else is a "remote" tarball and refused.
The run's .npmrc held @novox:registry=http://novox.internal:20000/api/packages/novox/npm/ (the forge setting's address). The lock holds https://git.novox.be/…, because the forge writes every tarball URL at its own public address however it is asked: on shanks, the packument fetched at http://novox.internal:20000/… gives "tarball":"https://git.novox.be/…". So the two never match, and replace-registry-host cannot help: it rewrites to the default registry, not a scope's.
Reproduced on g14 with npx npm@12.2.0 ci in mesh-tools main's node-tools: with @novox:registry=https://git.novox.internal/… the same EALLOWREMOTE; with @novox:registry=https://git.novox.be/… 108 packages are added.
The binding (package-registry.json) would not fix it: it gives the forge's mesh address (as the builder's .npmrc uses), which is again not the address in the tarballs. A token is not needed either: the registry answers reads anonymously.
Fix
npmRegistry(forge) in tools/runs.ts asks the registry, at the forge, for @novox/mesh-sdk's packument and names the registry by the address in its newest tarball URL (https://git.novox.be/api/packages/novox/npm/ today). When the registry does not say (an error, a non-200, no tarball, a tarball not under the npm path), it falls back to the forge's own address and says why.
lab_run writes that address into the run's .npmrc (script/start take it; without one the forge's address stands, as before), and answers with registry and any problem.
lab_check names the problem when the registry does not say its address.
Tests
New in test/runs.test.ts: the registry is named by the address of its tarballs (and asked at the forge); each way a registry may not say leaves the forge's address with the reason; the script's .npmrc names the registry given. On main the file fails at import (npmRegistry does not exist); with the fix 21 of 21 pass.
merge-check-typescript.sh with MESH_CHECK_MODULES=lab (toolchain from mesh-tools main's node-tools) type-checks and passes.
Live: npmRegistry("https://git.novox.internal") from g14 answers https://git.novox.be/api/packages/novox/npm/.
The bed itself (genesis-keeps-its-bus) is to be rerun on shanks once this is delivered: lab_run uses the lab's installed tools bundle, so a ref cannot test it before.
Fixes issue 624 (the lab module's lab_run fails at setup), its third setup failure.
## What happened
Lab run run-2026-10-13T13-15-26-634Z on shanks (mesh-tools at the branch of #33, now merged) installed mesh-sdk, then stopped in mesh-tools' node-tools:
`npm error code EALLOWREMOTE … Refusing to fetch "@novox/mesh-sdk@https://git.novox.be/api/packages/novox/npm/%40novox%2Fmesh-sdk/-/0.1.14/mesh-sdk-0.1.14.tgz"`
## Cause (seen, not guessed)
- shanks runs npm 12.2.0 (Arch package `npm 12.2.0-1`, node 26.10.0), which the lab's `npm` package declaration installs. No npmrc on shanks sets `allow-remote`: the debug log loads only npm's builtin npmrc (`globalconfig=/etc/npmrc`, which does not exist), the run's `.npmrc`, and a node-tools `.npmrc` that does not exist. **npm 12's own default for `allow-remote` is `none`** (its config definitions: "As of npm 12 the default is `none`. Tarballs that share a hostname with the configured registry … are still installed normally").
- arborist's reify lets a locked tarball through only when its `resolved` origin and path are the configured scope registry's (`#isRegistryResolvedTarball`); anything else is a "remote" tarball and refused.
- The run's `.npmrc` held `@novox:registry=http://novox.internal:20000/api/packages/novox/npm/` (the forge setting's address). The lock holds `https://git.novox.be/…`, because the forge writes every tarball URL at its own public address however it is asked: on shanks, the packument fetched at `http://novox.internal:20000/…` gives `"tarball":"https://git.novox.be/…"`. So the two never match, and `replace-registry-host` cannot help: it rewrites to the default registry, not a scope's.
- Reproduced on g14 with `npx npm@12.2.0 ci` in mesh-tools main's node-tools: with `@novox:registry=https://git.novox.internal/…` the same EALLOWREMOTE; with `@novox:registry=https://git.novox.be/…` 108 packages are added.
The binding (package-registry.json) would not fix it: it gives the forge's mesh address (as the builder's `.npmrc` uses), which is again not the address in the tarballs. A token is not needed either: the registry answers reads anonymously.
## Fix
- `npmRegistry(forge)` in tools/runs.ts asks the registry, at the forge, for @novox/mesh-sdk's packument and names the registry by the address in its newest tarball URL (`https://git.novox.be/api/packages/novox/npm/` today). When the registry does not say (an error, a non-200, no tarball, a tarball not under the npm path), it falls back to the forge's own address and says why.
- `lab_run` writes that address into the run's `.npmrc` (`script`/`start` take it; without one the forge's address stands, as before), and answers with `registry` and any `problem`.
- `lab_check` names the problem when the registry does not say its address.
## Tests
- New in test/runs.test.ts: the registry is named by the address of its tarballs (and asked at the forge); each way a registry may not say leaves the forge's address with the reason; the script's `.npmrc` names the registry given. On main the file fails at import (`npmRegistry` does not exist); with the fix 21 of 21 pass.
- `merge-check-typescript.sh` with `MESH_CHECK_MODULES=lab` (toolchain from mesh-tools main's node-tools) type-checks and passes.
- Live: `npmRegistry("https://git.novox.internal")` from g14 answers `https://git.novox.be/api/packages/novox/npm/`.
The bed itself (genesis-keeps-its-bus) is to be rerun on shanks once this is delivered: lab_run uses the lab's installed tools bundle, so a ref cannot test it before.
mesh/merge-gate head bb60de6d616a merged into trunk a84d0094a0a3 — pass: builds lab → shanks; no bus step; every machine composes with the change as it did…
mesh/repo-check head bb60de6d616a merged into trunk a84d0094a0a3 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
npm 12 installs a locked tarball only from its configured registry; the forge
writes every tarball URL, and so every lock file, at its public address, and
the lab named the registry by its forge setting's address. Every run stopped
at mesh-tools' install with EALLOWREMOTE.
Deliverynovox/mesh-catalog@8ad121d5c369 — delivered since 2026-10-13T14:36:38Z
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 37s
lab on the rest running it: sent
Transitions
2026-10-13 14:27 (new) → proposed (announced): novox/mesh-catalog#275's head announced
2026-10-13 14:31 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 14:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 14:35 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 14:35 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-13 14:36 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@8ad121d5c369` — **delivered** since 2026-10-13T14:36:38Z
**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 37s
- lab on the rest running it: sent
**Transitions**
- 2026-10-13 14:27 (new) → proposed (announced): novox/mesh-catalog#275's head announced
- 2026-10-13 14:31 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 14:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 14:35 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 14:35 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-13 14:36 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`.
Merge check at bb60de6d
Judged: head bb60de6d616a merged into trunk a84d0094a0a3; read beside it: mesh-controller 6f1a05366c1d, mesh-controller-main 6f1a05366c1d, mesh-host 0e92ef3d1b21, 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-1791897985866650956 (builds --log build-1791897985866650956).
--- 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-13T13:23:41Z 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-13T13:23:41Z
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.002s
words: 12 retired words and 70 daemons' lines, none in the 46335 strings of 716 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.014s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
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: 66, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.248s
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)
testing modules/lab (TypeScript)
✔ a checkout with a lock file at its root is installed there (3.502195ms)
✔ a checkout whose package lives one directory down is installed there, as mesh-tools' node-tools (0.802871ms)
✔ a package.json with no lock file is named, never installed (0.484511ms)
✔ a run installs and builds mesh-tools in node-tools, where its lock file is (23.826096ms)
✔ a run installs a checkout with its lock file at the root there, and builds only when asked (4.646147ms)
✔ a run fails at its setup, naming the checkout, when nothing of it can be installed (10.933907ms)
✔ a run checks out mesh-tools-go and says where its checkouts are (0.678211ms)
✔ the forge credential is the bound account and its sealed secret, for the forge's own origin (0.640251ms)
✔ a run clones through git's credential store, and its script carries no secret (0.754341ms)
✔ git presents the stored credential to the forge, and only when one is given (39.28733ms)
✔ a stopped script removes the credential, whatever ends it (20.786842ms)
✔ the script removes the credential as soon as its clones are done (0.476951ms)
✔ credentials a crashed run left are removed, but not the running one's (1.187932ms)
✔ the lab asks the package registry for read only (0.681041ms)
✔ each check gets a fresh directory of its own (0.409051ms)
﹣ what earlier checks left is cleared, and what cannot be is named rather than tripped over (0.05292ms) # running as root, which no directory mode stops from removing anything
✔ leftover checks are cleared, whoever runs the check (0.727941ms)
✔ the lab's tools bundle names its bound credential and binding in its env (0.13452ms)
✔ a run names the package registry by the address the registry gives its tarballs (17.837077ms)
✔ a registry that does not say its address leaves the forge's, and the reason is said (0.910942ms)
✔ a run's npm configuration names the registry it was given, and the forge's own address only without one (0.945441ms)
ℹ tests 21
ℹ suites 0
ℹ pass 20
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 234.981718
**Merge check** at `bb60de6d`
Judged: head `bb60de6d616a` merged into trunk `a84d0094a0a3`; read beside it: mesh-controller `6f1a05366c1d`, mesh-controller-main `6f1a05366c1d`, mesh-host `0e92ef3d1b21`, 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-1791897985866650956` (`builds --log build-1791897985866650956`).
```
--- 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-13T13:23:41Z 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-13T13:23:41Z
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.002s
words: 12 retired words and 70 daemons' lines, none in the 46335 strings of 716 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.014s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
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: 66, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.248s
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)
testing modules/lab (TypeScript)
✔ a checkout with a lock file at its root is installed there (3.502195ms)
✔ a checkout whose package lives one directory down is installed there, as mesh-tools' node-tools (0.802871ms)
✔ a package.json with no lock file is named, never installed (0.484511ms)
✔ a run installs and builds mesh-tools in node-tools, where its lock file is (23.826096ms)
✔ a run installs a checkout with its lock file at the root there, and builds only when asked (4.646147ms)
✔ a run fails at its setup, naming the checkout, when nothing of it can be installed (10.933907ms)
✔ a run checks out mesh-tools-go and says where its checkouts are (0.678211ms)
✔ the forge credential is the bound account and its sealed secret, for the forge's own origin (0.640251ms)
✔ a run clones through git's credential store, and its script carries no secret (0.754341ms)
✔ git presents the stored credential to the forge, and only when one is given (39.28733ms)
✔ a stopped script removes the credential, whatever ends it (20.786842ms)
✔ the script removes the credential as soon as its clones are done (0.476951ms)
✔ credentials a crashed run left are removed, but not the running one's (1.187932ms)
✔ the lab asks the package registry for read only (0.681041ms)
✔ each check gets a fresh directory of its own (0.409051ms)
﹣ what earlier checks left is cleared, and what cannot be is named rather than tripped over (0.05292ms) # running as root, which no directory mode stops from removing anything
✔ leftover checks are cleared, whoever runs the check (0.727941ms)
✔ the lab's tools bundle names its bound credential and binding in its env (0.13452ms)
✔ a run names the package registry by the address the registry gives its tarballs (17.837077ms)
✔ a registry that does not say its address leaves the forge's, and the reason is said (0.910942ms)
✔ a run's npm configuration names the registry it was given, and the forge's own address only without one (0.945441ms)
ℹ tests 21
ℹ suites 0
ℹ pass 20
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 234.981718
```
mesh/merge-gate head 8ad121d5c369 merged into trunk 305c2ba24733 — pass: builds lab → shanks; no bus step; every machine composes with the change as it did…
mesh/repo-check head 8ad121d5c369 merged into trunk 305c2ba24733 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
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.
Head 8ad121d5: both blocking faults of the review fixed.
The tarball URL is parsed with new URL and taken only when: no whitespace or control character in the raw string; scheme https: or the forge's own; no user or password; no query or fragment; pathname.startsWith(NPM_PATH); hostname equal to the forge setting's own host. Otherwise the forge's address stands and the reason is said (lab_run's problem, lab_check's problems).
The registry is built as url.origin + NPM_PATH; the raw string never reaches .npmrc.
New fallback cases in the test: foreign host, the npm path in a query, a query, a fragment, the path behind a fragment, ftp:, file:///api/packages/novox/npm/, an embedded newline adding registry=/allow-remote=all, user:password. 21 of 21 pass; merge-check-typescript.sh for lab type-checks and passes.
Consequence for shanks (an operator setting, not code): the only trusted name is now the forge setting's own host. The lab's forge is http://novox.internal:20000, and the forge names its tarballs git.novox.be, so with this head runs still fall back and stop at EALLOWREMOTE, and lab_check says so. Live from g14: npmRegistry("https://git.novox.be") answers https://git.novox.be/api/packages/novox/npm/; npmRegistry("https://git.novox.internal") falls back naming the host mismatch. shanks reads https://git.novox.be/novox/mesh-lab.git (ls-remote, public) and the registry there. So runs pass once the lab's forge setting is https://git.novox.be; the clone credential then goes to that origin over https. I chose not to add a second trusted-name setting: a public name has no default (controller rule, ADR 0262), so it would stop the lab composing until set.
Head 8ad121d5: both blocking faults of the review fixed.
1. The tarball URL is parsed with `new URL` and taken only when: no whitespace or control character in the raw string; scheme https: or the forge's own; no user or password; no query or fragment; `pathname.startsWith(NPM_PATH)`; hostname equal to the forge setting's own host. Otherwise the forge's address stands and the reason is said (lab_run's `problem`, lab_check's problems).
2. The registry is built as `url.origin + NPM_PATH`; the raw string never reaches `.npmrc`.
New fallback cases in the test: foreign host, the npm path in a query, a query, a fragment, the path behind a fragment, ftp:, file:///api/packages/novox/npm/, an embedded newline adding registry=/allow-remote=all, user:password. 21 of 21 pass; merge-check-typescript.sh for lab type-checks and passes.
**Consequence for shanks (an operator setting, not code):** the only trusted name is now the forge setting's own host. The lab's forge is `http://novox.internal:20000`, and the forge names its tarballs `git.novox.be`, so with this head runs still fall back and stop at EALLOWREMOTE, and lab_check says so. Live from g14: `npmRegistry("https://git.novox.be")` answers `https://git.novox.be/api/packages/novox/npm/`; `npmRegistry("https://git.novox.internal")` falls back naming the host mismatch. shanks reads `https://git.novox.be/novox/mesh-lab.git` (ls-remote, public) and the registry there. So runs pass once the lab's forge setting is `https://git.novox.be`; the clone credential then goes to that origin over https. I chose not to add a second trusted-name setting: a public name has no default (controller rule, ADR 0262), so it would stop the lab composing until set.
Merge check at 8ad121d5
Judged: head 8ad121d5c369 merged into trunk 305c2ba24733; read beside it: mesh-controller 6f1a05366c1d, mesh-controller-main 6f1a05366c1d, mesh-host 0e92ef3d1b21, 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-1791901644511173237 (builds --log build-1791901644511173237).
--- 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-13T14:22:41Z 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-13T14:22:41Z
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 46586 strings of 717 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/secrets 0.012s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
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: 66, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.291s
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)
testing modules/lab (TypeScript)
✔ a checkout with a lock file at its root is installed there (3.602865ms)
✔ a checkout whose package lives one directory down is installed there, as mesh-tools' node-tools (1.086922ms)
✔ a package.json with no lock file is named, never installed (0.623141ms)
✔ a run installs and builds mesh-tools in node-tools, where its lock file is (8.369752ms)
✔ a run installs a checkout with its lock file at the root there, and builds only when asked (5.525968ms)
✔ a run fails at its setup, naming the checkout, when nothing of it can be installed (11.176146ms)
✔ a run checks out mesh-tools-go and says where its checkouts are (0.765381ms)
✔ the forge credential is the bound account and its sealed secret, for the forge's own origin (0.659521ms)
✔ a run clones through git's credential store, and its script carries no secret (0.766692ms)
✔ git presents the stored credential to the forge, and only when one is given (11.190386ms)
✔ a stopped script removes the credential, whatever ends it (24.455245ms)
✔ the script removes the credential as soon as its clones are done (0.347641ms)
✔ credentials a crashed run left are removed, but not the running one's (0.717051ms)
✔ the lab asks the package registry for read only (0.30905ms)
✔ each check gets a fresh directory of its own (0.519301ms)
﹣ what earlier checks left is cleared, and what cannot be is named rather than tripped over (0.07131ms) # running as root, which no directory mode stops from removing anything
✔ leftover checks are cleared, whoever runs the check (0.935762ms)
✔ the lab's tools bundle names its bound credential and binding in its env (0.18857ms)
✔ a run names the package registry by the address the registry gives its tarballs (17.202395ms)
✔ a registry that does not give an address the lab takes leaves the forge's, and the reason is said (5.245517ms)
✔ a run's npm configuration names the registry it was given, and the forge's own address only without one (0.310701ms)
ℹ tests 21
ℹ suites 0
ℹ pass 20
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 200.185088
**Merge check** at `8ad121d5`
Judged: head `8ad121d5c369` merged into trunk `305c2ba24733`; read beside it: mesh-controller `6f1a05366c1d`, mesh-controller-main `6f1a05366c1d`, mesh-host `0e92ef3d1b21`, 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-1791901644511173237` (`builds --log build-1791901644511173237`).
```
--- 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-13T14:22:41Z 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-13T14:22:41Z
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 46586 strings of 717 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/secrets 0.012s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
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: 66, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.291s
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)
testing modules/lab (TypeScript)
✔ a checkout with a lock file at its root is installed there (3.602865ms)
✔ a checkout whose package lives one directory down is installed there, as mesh-tools' node-tools (1.086922ms)
✔ a package.json with no lock file is named, never installed (0.623141ms)
✔ a run installs and builds mesh-tools in node-tools, where its lock file is (8.369752ms)
✔ a run installs a checkout with its lock file at the root there, and builds only when asked (5.525968ms)
✔ a run fails at its setup, naming the checkout, when nothing of it can be installed (11.176146ms)
✔ a run checks out mesh-tools-go and says where its checkouts are (0.765381ms)
✔ the forge credential is the bound account and its sealed secret, for the forge's own origin (0.659521ms)
✔ a run clones through git's credential store, and its script carries no secret (0.766692ms)
✔ git presents the stored credential to the forge, and only when one is given (11.190386ms)
✔ a stopped script removes the credential, whatever ends it (24.455245ms)
✔ the script removes the credential as soon as its clones are done (0.347641ms)
✔ credentials a crashed run left are removed, but not the running one's (0.717051ms)
✔ the lab asks the package registry for read only (0.30905ms)
✔ each check gets a fresh directory of its own (0.519301ms)
﹣ what earlier checks left is cleared, and what cannot be is named rather than tripped over (0.07131ms) # running as root, which no directory mode stops from removing anything
✔ leftover checks are cleared, whoever runs the check (0.935762ms)
✔ the lab's tools bundle names its bound credential and binding in its env (0.18857ms)
✔ a run names the package registry by the address the registry gives its tarballs (17.202395ms)
✔ a registry that does not give an address the lab takes leaves the forge's, and the reason is said (5.245517ms)
✔ a run's npm configuration names the registry it was given, and the forge's own address only without one (0.310701ms)
ℹ tests 21
ℹ suites 0
ℹ pass 20
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 200.185088
```
Host taken from the metadata (finding 1 of the first review): fixed. modules/lab/tools/runs.ts:96-121 parses the tarball with new URL, refuses whitespace and control characters, any scheme other than https or the forge's own, a user or password, a query or a fragment, and a path outside /api/packages/novox/npm/, and it requires the host to equal the forge setting's host. URL normalisation resolves .. and %2e%2e before the startsWith check, so a path cannot climb out of the npm path.
Newline injection into .npmrc (finding 2): fixed. The registry is built only from t.origin + NPM_PATH (runs.ts:121), so the raw string never reaches the run's .npmrc, and runs.ts:109 refuses whitespace and control characters before parsing.
Tests: the fallback table in test/runs.test.ts covers a foreign host, a query, a fragment, an address hidden in a fragment, ftp:, file:, a newline injection and user:password. I did not run them locally, because the clone was refused by this session's permission system. mesh/repo-check ran them and the type-check at this head: 20 of 21 tests pass, 1 is skipped because it runs as root, and none fail.
runs.ts:120 compares the hostname but not the port, so a tarball at the forge's host on another port is accepted. Low risk, since it is the forge's own host.
This merge alone does not fix issue 624
The lab's forge setting (the mesh-wide layer) is http://novox.internal:20000, and the forge writes tarballs at git.novox.be. So every run still falls back and still stops on EALLOWREMOTE, although lab_run and lab_check now say why. Do not resolve 624 on this merge.
Where the trusted public name should come from
Fixing it at the forge (ROOT_URL) is wrong. ROOT_URL is the public name for every link the forge writes (its own API answers at git.novox.be too) and for every lock file already made. Changing it breaks those links and lock files.
Repointing the lab's forge setting to https://git.novox.be works, but it sends the lab's git clones and the forge credential over the public address instead of the mesh path. It is also a change to a trusted setting (runtime-env), so it needs an operator-approved proposal.
I recommend a trusted public name that the mesh owns, so clones stay on the mesh address. The best source is the npm-package-registry provision's binding, which names the forge's public root next to its mesh address. The next best is a separate trusted lab setting. The check in npmRegistry then compares against that name instead of the forge setting's host, and the validation code in this PR stays as it is.
Verdict: approve at 8ad121d5c3697c3927bcc8e6b311aa4098ff2896
Independent re-review (the review of bb60de6 found two faults; both are fixed here).
What I checked
- Diff read in full at 8ad121d.
- Host taken from the metadata (finding 1 of the first review): fixed. modules/lab/tools/runs.ts:96-121 parses the tarball with new URL, refuses whitespace and control characters, any scheme other than https or the forge's own, a user or password, a query or a fragment, and a path outside /api/packages/novox/npm/, and it requires the host to equal the forge setting's host. URL normalisation resolves `..` and `%2e%2e` before the startsWith check, so a path cannot climb out of the npm path.
- Newline injection into .npmrc (finding 2): fixed. The registry is built only from `t.origin` + NPM_PATH (runs.ts:121), so the raw string never reaches the run's .npmrc, and runs.ts:109 refuses whitespace and control characters before parsing.
- Tests: the fallback table in test/runs.test.ts covers a foreign host, a query, a fragment, an address hidden in a fragment, ftp:, file:, a newline injection and user:password. I did not run them locally, because the clone was refused by this session's permission system. mesh/repo-check ran them and the type-check at this head: 20 of 21 tests pass, 1 is skipped because it runs as root, and none fail.
- Reachability from shanks: netcheck_dns gives git.novox.be as 142.132.152.141 (a public address, not the tunnel), and a GET from shanks to https://git.novox.be/api/packages/novox/npm/@novox%2fmesh-sdk answered 200 in 331 ms.
Minor (not blocking)
- runs.ts:120 compares the hostname but not the port, so a tarball at the forge's host on another port is accepted. Low risk, since it is the forge's own host.
- The PR body is stale: it says npmRegistry("https://git.novox.internal") answers https://git.novox.be/...; with the host check, that call now falls back.
This merge alone does not fix issue 624
The lab's forge setting (the mesh-wide layer) is http://novox.internal:20000, and the forge writes tarballs at git.novox.be. So every run still falls back and still stops on EALLOWREMOTE, although lab_run and lab_check now say why. Do not resolve 624 on this merge.
Where the trusted public name should come from
- Fixing it at the forge (ROOT_URL) is wrong. ROOT_URL is the public name for every link the forge writes (its own API answers at git.novox.be too) and for every lock file already made. Changing it breaks those links and lock files.
- Repointing the lab's forge setting to https://git.novox.be works, but it sends the lab's git clones and the forge credential over the public address instead of the mesh path. It is also a change to a trusted setting (runtime-env), so it needs an operator-approved proposal.
- I recommend a trusted public name that the mesh owns, so clones stay on the mesh address. The best source is the npm-package-registry provision's binding, which names the forge's public root next to its mesh address. The next best is a separate trusted lab setting. The check in npmRegistry then compares against that name instead of the forge setting's host, and the validation code in this PR stays as it is.
Correction to this PR's body (it describes head bb60de6d, not the merged head 8ad121d5):
"names the registry by the address in its newest tarball URL (https://git.novox.be/api/packages/novox/npm/ today)" is no longer true as merged. Since 8ad121d5 the tarball's address is taken only when its host is the forge setting's own host, so with the lab's forge http://novox.internal:20000 the lab falls back to that address, and runs on shanks still stop at EALLOWREMOTE; lab_check names the host mismatch.
"Live: npmRegistry(\"https://git.novox.internal\") from g14 answers https://git.novox.be/api/packages/novox/npm/" was true of bb60de6d only. With 8ad121d5 that call falls back and names the mismatch; only a forge set at https://git.novox.be yields that registry.
The host comparison ignores the port (t.hostname !== own.hostname); the follow-up will compare host and port against a trusted public root.
Issue 624 stays open: the trusted public name is still to come (see the issue's notes).
Correction to this PR's body (it describes head bb60de6d, not the merged head 8ad121d5):
- "names the registry by the address in its newest tarball URL (`https://git.novox.be/api/packages/novox/npm/` today)" is no longer true as merged. Since 8ad121d5 the tarball's address is taken only when its host is the forge setting's own host, so with the lab's forge `http://novox.internal:20000` the lab falls back to that address, and runs on shanks still stop at EALLOWREMOTE; lab_check names the host mismatch.
- "Live: `npmRegistry(\"https://git.novox.internal\")` from g14 answers `https://git.novox.be/api/packages/novox/npm/`" was true of bb60de6d only. With 8ad121d5 that call falls back and names the mismatch; only a forge set at `https://git.novox.be` yields that registry.
- The host comparison ignores the port (`t.hostname !== own.hostname`); the follow-up will compare host and port against a trusted public root.
Issue 624 stays open: the trusted public name is still to come (see the issue's notes).
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.
Fixes issue 624 (the lab module's lab_run fails at setup), its third setup failure.
What happened
Lab run run-2026-10-13T13-15-26-634Z on shanks (mesh-tools at the branch of #33, now merged) installed mesh-sdk, then stopped in mesh-tools' node-tools:
npm error code EALLOWREMOTE … Refusing to fetch "@novox/mesh-sdk@https://git.novox.be/api/packages/novox/npm/%40novox%2Fmesh-sdk/-/0.1.14/mesh-sdk-0.1.14.tgz"Cause (seen, not guessed)
npm 12.2.0-1, node 26.10.0), which the lab'snpmpackage declaration installs. No npmrc on shanks setsallow-remote: the debug log loads only npm's builtin npmrc (globalconfig=/etc/npmrc, which does not exist), the run's.npmrc, and a node-tools.npmrcthat does not exist. npm 12's own default forallow-remoteisnone(its config definitions: "As of npm 12 the default isnone. Tarballs that share a hostname with the configured registry … are still installed normally").resolvedorigin and path are the configured scope registry's (#isRegistryResolvedTarball); anything else is a "remote" tarball and refused..npmrcheld@novox:registry=http://novox.internal:20000/api/packages/novox/npm/(the forge setting's address). The lock holdshttps://git.novox.be/…, because the forge writes every tarball URL at its own public address however it is asked: on shanks, the packument fetched athttp://novox.internal:20000/…gives"tarball":"https://git.novox.be/…". So the two never match, andreplace-registry-hostcannot help: it rewrites to the default registry, not a scope's.npx npm@12.2.0 ciin mesh-tools main's node-tools: with@novox:registry=https://git.novox.internal/…the same EALLOWREMOTE; with@novox:registry=https://git.novox.be/…108 packages are added.The binding (package-registry.json) would not fix it: it gives the forge's mesh address (as the builder's
.npmrcuses), which is again not the address in the tarballs. A token is not needed either: the registry answers reads anonymously.Fix
npmRegistry(forge)in tools/runs.ts asks the registry, at the forge, for @novox/mesh-sdk's packument and names the registry by the address in its newest tarball URL (https://git.novox.be/api/packages/novox/npm/today). When the registry does not say (an error, a non-200, no tarball, a tarball not under the npm path), it falls back to the forge's own address and says why.lab_runwrites that address into the run's.npmrc(script/starttake it; without one the forge's address stands, as before), and answers withregistryand anyproblem.lab_checknames the problem when the registry does not say its address.Tests
.npmrcnames the registry given. On main the file fails at import (npmRegistrydoes not exist); with the fix 21 of 21 pass.merge-check-typescript.shwithMESH_CHECK_MODULES=lab(toolchain from mesh-tools main's node-tools) type-checks and passes.npmRegistry("https://git.novox.internal")from g14 answershttps://git.novox.be/api/packages/novox/npm/.The bed itself (genesis-keeps-its-bus) is to be rerun on shanks once this is delivered: lab_run uses the lab's installed tools bundle, so a ref cannot test it before.
Delivery
novox/mesh-catalog@8ad121d5c369— delivered since 2026-10-13T14:36:38ZDelivery 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.Merge check at
bb60de6dJudged: head
bb60de6d616amerged into trunka84d0094a0a3; read beside it: mesh-controller6f1a05366c1d, mesh-controller-main6f1a05366c1d, mesh-host0e92ef3d1b21, 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-1791897985866650956(builds --log build-1791897985866650956).Head
8ad121d5: both blocking faults of the review fixed.new URLand taken only when: no whitespace or control character in the raw string; scheme https: or the forge's own; no user or password; no query or fragment;pathname.startsWith(NPM_PATH); hostname equal to the forge setting's own host. Otherwise the forge's address stands and the reason is said (lab_run'sproblem, lab_check's problems).url.origin + NPM_PATH; the raw string never reaches.npmrc.New fallback cases in the test: foreign host, the npm path in a query, a query, a fragment, the path behind a fragment, ftp:, file:///api/packages/novox/npm/, an embedded newline adding registry=/allow-remote=all, user:password. 21 of 21 pass; merge-check-typescript.sh for lab type-checks and passes.
Consequence for shanks (an operator setting, not code): the only trusted name is now the forge setting's own host. The lab's forge is
http://novox.internal:20000, and the forge names its tarballsgit.novox.be, so with this head runs still fall back and stop at EALLOWREMOTE, and lab_check says so. Live from g14:npmRegistry("https://git.novox.be")answershttps://git.novox.be/api/packages/novox/npm/;npmRegistry("https://git.novox.internal")falls back naming the host mismatch. shanks readshttps://git.novox.be/novox/mesh-lab.git(ls-remote, public) and the registry there. So runs pass once the lab's forge setting ishttps://git.novox.be; the clone credential then goes to that origin over https. I chose not to add a second trusted-name setting: a public name has no default (controller rule, ADR 0262), so it would stop the lab composing until set.Merge check at
8ad121d5Judged: head
8ad121d5c369merged into trunk305c2ba24733; read beside it: mesh-controller6f1a05366c1d, mesh-controller-main6f1a05366c1d, mesh-host0e92ef3d1b21, 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-1791901644511173237(builds --log build-1791901644511173237).Verdict: approve at
8ad121d5c3Independent re-review (the review of
bb60de6found two faults; both are fixed here).What I checked
8ad121d...and%2e%2ebefore the startsWith check, so a path cannot climb out of the npm path.t.origin+ NPM_PATH (runs.ts:121), so the raw string never reaches the run's .npmrc, and runs.ts:109 refuses whitespace and control characters before parsing.Minor (not blocking)
This merge alone does not fix issue 624
The lab's forge setting (the mesh-wide layer) is http://novox.internal:20000, and the forge writes tarballs at git.novox.be. So every run still falls back and still stops on EALLOWREMOTE, although lab_run and lab_check now say why. Do not resolve 624 on this merge.
Where the trusted public name should come from
Correction to this PR's body (it describes head
bb60de6d, not the merged head8ad121d5):https://git.novox.be/api/packages/novox/npm/today)" is no longer true as merged. Since8ad121d5the tarball's address is taken only when its host is the forge setting's own host, so with the lab's forgehttp://novox.internal:20000the lab falls back to that address, and runs on shanks still stop at EALLOWREMOTE; lab_check names the host mismatch.npmRegistry(\"https://git.novox.internal\")from g14 answershttps://git.novox.be/api/packages/novox/npm/" was true ofbb60de6donly. With8ad121d5that call falls back and names the mismatch; only a forge set athttps://git.novox.beyields that registry.t.hostname !== own.hostname); the follow-up will compare host and port against a trusted public root.Issue 624 stays open: the trusted public name is still to come (see the issue's notes).