M1 check-needs: a package outside every Go artifact's from takes the manifest's own check-needs

The forge module's internal/seatgit whole test needs the Node build seat, and no Go artifact's from holds it, so
nothing named its need and the Go build seat ran it on a node without the Node toolchain. The manifest now says the
need at its top level, read by the Go build module for such packages; gitea declares node-build-node
(review round 1, mesh-catalog, finding on §800; H-A-453 (2)).

Builds: design 47 H2 §800, H-A-453 (2)
This commit is contained in:
2026-11-22 02:27:36 +01:00
parent 30a3e665e0
commit 98da0e0b68
4 changed files with 52 additions and 7 deletions
+3
View File
@@ -3,6 +3,9 @@
"version": "0.1",
"class": "core",
"moved": true,
"check-needs": [
"node-build-node"
],
"requires": [
"postgres-database",
"route",