Merge pull request 'Add the go and nodejs modules that own the toolchain packages on a node, step A of issue 1573 (ADR 0477 §4)' (#406) from fix/1573a-toolchain-owners into main

modules/go/README.md

@@ -0,0 +1,14 @@
+# go
+
+The Go toolchain as a module (novox/hq ADR 0477 §4, issue 1573).
+
+- **Declares the package `go`.** Today dev-tools, lab and mesh-build-go declare it too, which the resolver allows
+  (ADR 0303); once they require `go-toolchain` instead (issue 1573's second step), this is the only module that
+  declares it, and `checks/toolchains` refuses another.
+- **Provides `go-toolchain` with the machine's reach**: a module that requires it composes only on a machine where
+  this module is assigned. It is never pulled in for whatever asked, so `go` is assigned to a node on purpose.
+  Nothing requires it yet; dev-tools, lab and mesh-build-go will, in the second step.
+- Holds no long-running resource, so it adds nothing to `health-undeclared`.
+
+The node-engine never uninstalls a package, so when the users stop declaring `go`, nothing leaves a node that has
+this module.

modules/go/module.json

@@ -0,0 +1,20 @@
+{
+  "module": "go",
+  "version": "1",
+  "capabilities": [
+    "package-manager"
+  ],
+  "provides": [
+    {
+      "name": "go-toolchain",
+      "reach": "machine"
+    }
+  ],
+  "resources": [
+    {
+      "id": "go",
+      "type": "package",
+      "package": "go"
+    }
+  ]
+}

modules/nodejs/README.md

@@ -0,0 +1,14 @@
+# nodejs
+
+Node.js and npm as a module (novox/hq ADR 0477 §4, issue 1573).
+
+- **Declares the packages `nodejs` and `npm`.** Today dev-tools, lab and mesh-build-node declare some of them too,
+  which the resolver allows (ADR 0303); once they require `node-toolchain` instead (issue 1573's second step), this
+  is the only module that declares them, and `checks/toolchains` refuses another.
+- **Provides `node-toolchain` with the machine's reach**: a module that requires it composes only on a machine where
+  this module is assigned. It is never pulled in for whatever asked, so `nodejs` is assigned to a node on purpose.
+  Nothing requires it yet; dev-tools, lab and mesh-build-node will, in the second step.
+- Holds no long-running resource, so it adds nothing to `health-undeclared`.
+
+The node-engine never uninstalls a package, so when the users stop declaring `nodejs` and `npm`, nothing leaves a
+node that has this module.

modules/nodejs/module.json

@@ -0,0 +1,25 @@
+{
+  "module": "nodejs",
+  "version": "1",
+  "capabilities": [
+    "package-manager"
+  ],
+  "provides": [
+    {
+      "name": "node-toolchain",
+      "reach": "machine"
+    }
+  ],
+  "resources": [
+    {
+      "id": "nodejs",
+      "type": "package",
+      "package": "nodejs"
+    },
+    {
+      "id": "npm",
+      "type": "package",
+      "package": "npm"
+    }
+  ]
+}