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
@@ -19,8 +19,8 @@ Assign it to every node, with the `go` and `nodejs` modules: it requires their p
 | git and jq | `git`, `jq` | package |

 All are in the distribution's official repositories, so the node-engine's package manager installs them on any
-node. The versions are the distribution's: the toolchain images that run `mesh/repo-check` stay the judge of a
-pull request, and a local run is the developer's early answer, not the verdict.
+node. The versions are the distribution's: the build modules' toolchains, which the checker runs a pull request's tests with, stay the
+judge of a pull request, and a local run is the developer's early answer, not the verdict.

 Nothing else is placed: no file, no service, no environment. A module's own dependencies come from its lock
-file (`go.mod`, `package-lock.json`), as in the toolchain images.
+file (`go.mod`, `package-lock.json`), as in the build modules.