Mark the build modules moved, so a machine assigned them composes before the forge serves their entry (issue 1537)

modules/mesh-build-go/cmd/mesh-build-go/forge_test.go

@@ -23,6 +23,7 @@ const (
 )
 
 type forgeManifest struct {
+	Moved     bool             `json:"moved"`
 	Requires  []any            `json:"requires"`
 	State     []any            `json:"state"`
 	Resources []map[string]any `json:"resources"`
@@ -44,6 +45,16 @@ func readForgeManifest(t *testing.T) forgeManifest {
 	return m
 }
 
+// The forge files are filled on the node by the provisioner's client, never by the controller (ADR 0466 §4, ADR 0400
+// §5, issue 1537): the forge serves a module's entry only after the module has run and reported its key (ADR 0400
+// §2), so a controller filling them would refuse the machine until then, and the module could never run.
+func TestTheForgeFilesAreFilledOnTheNodeSoTheModuleCanRunBeforeItsEntry(t *testing.T) {
+	if !readForgeManifest(t).Moved {
+		t.Errorf("%s's manifest does not say \"moved\": true, so the controller fills its forge files and refuses "+
+			"every machine it is assigned to until the forge serves an entry it makes only after the module ran", forgeModule)
+	}
+}
+
 func forgeTemplate(t *testing.T, r map[string]any) string {
 	t.Helper()
 	name, _ := r["template"].(string)