From 8c37328ba375c72b4912d020f9b3d9671aef90e9 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 21 Sep 2026 15:18:46 +0200 Subject: [PATCH] The catalogue is recognised by the registry's manifest, not the control plane's The control plane's manifest is leaving the catalogue (ADR 0069, issue 072); a marker that named it would make every catalogue-reading bed skip the day it goes. --- test/integration/harness.ts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test/integration/harness.ts b/test/integration/harness.ts index ac09d5e..360cd50 100644 --- a/test/integration/harness.ts +++ b/test/integration/harness.ts @@ -255,7 +255,9 @@ export function catalogueDir(): string { ? [resolve(named, "modules"), resolve(named)] : [resolve(process.cwd(), "..", "mesh-catalog", "modules")]; for (const dir of candidates) { - if (existsSync(resolve(dir, "mesh-controller", "module.json"))) return dir; + // Known by the registry's manifest, which genesis reads from the catalogue and always will — + // not the control plane's, which lives in the control plane's own repository (ADR 0069). + if (existsSync(resolve(dir, "distribution", "module.json"))) return dir; } throw new Error( `no catalogue: MESH_LAB_CATALOG=${named ?? "(unset)"} and nothing at ${candidates.join(", ")}`);