Make dev-tools, lab and the build modules need the go and nodejs modules instead of declaring the toolchain packages, step B of issue 1573 (ADR 0477 §4)

+212 -73

6 Commits

Author	SHA1	Message	Date
mesh-tools	36259f3406	Update the build modules' manifest tests for the toolchain provisions (issue 1573) mesh/merge-gate head 36259f3406f7 merged into trunk f0c8958dd217 — pass: builds dev-tools, lab, mesh-build-go, mesh-build-node → ace, g14, novox, shanks; n… Details mesh/repo-check head 36259f3406f7 merged into trunk f0c8958dd217 — pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the ch… Details mesh/delivery covered: a later merge that contains it was delivered: novox/mesh-catalog@e023f69989ab (merged as b5dbfbb7 into main, walk plan-17925769516… Details	2026-10-21 09:53:48 +00:00
mesh-tools	d8d153295a	Say in the go and nodejs READMEs that they are now the only declarers (issue 1573)	2026-10-21 09:51:22 +00:00
mesh-tools	bda75011a1	Say in the build modules' READMEs where the packages come from (issue 1573)	2026-10-21 09:50:55 +00:00
mesh-tools	9d1f152603	Wire the toolchains check into the merge check (issue 1573)	2026-10-21 09:50:46 +00:00
mesh-tools	c4cd7a1b16	Check that only the go and nodejs modules declare the toolchain packages (issue 1573)	2026-10-21 09:50:14 +00:00
mesh-tools	7753c27042	Make dev-tools, lab and the two build modules require the toolchain provisions instead of declaring the packages (issue 1573)	2026-10-21 09:49:50 +00:00

Make dev-tools, lab and the build modules need the go and nodejs modules instead of declaring the toolchain packages, step B of issue 1573 (ADR 0477 §4) #409