Take the build agent and the toolchain images out of the catalogue's prose, and refuse the word where it comes back outside the one module still naming it (issue 1295, E6)

2026-10-23 15:34:11 +02:00
parent c4fc565180
commit 6bfdbc5758
12 changed files with 114 additions and 47 deletions
@@ -166,7 +166,7 @@ export async function npmRegistry(forge: string, get: typeof fetch = fetch, publ
 * The forge credential a run's clones may present, as a git credential-store line —
 * scheme://user:password@host[:port] — for the forge's own origin, or undefined when the lab holds none.
 *
- * **The mesh's credential for the forge, the way the build agent holds it** (novox/hq issue 624): the lab
+ * **The mesh's credential for the forge, the way the build modules hold it** (novox/hq issue 624): the lab
 * requires the package registry, the forge's provisioner binds it an account (`as`) and seals that
 * account's password, and the forge that answers npm is the forge that hosts the repositories. Private
 * repositories (mesh-tools-go) are cloned with it; public ones clone as before. Written to a file git reads