The catalogue declares the event it emits on starting

Its runtime announces that it has just started and may have missed builds — the event the control
plane follows to replay them — and its manifest did not declare it. A module's authority on the bus
is derived from what it declares, so the publish was refused and the runtime died on start, in a
loop, with the mesh's graph never catching up.

modules/gitea/index.ts

@@ -107,6 +107,9 @@ async function pollMerged(client: GiteaClient): Promise<void> {
           clone_url: repo.clone_url,
           html_url: pull.html_url,
         });
+        // Said, because a trigger that fires silently is indistinguishable from one that did not
+        // fire (novox/hq 04-ISSUES/131) — this line is how an operator knows the mesh was told.
+        console.log(`[gitea] announced merge ${repo.full_name}#${pull.number} (${pull.merge_commit_sha.slice(0, 8)}) into ${pull.base}`);
       }
       announced.add(pull.merge_commit_sha);
       changed = true;

modules/mesh-catalog/module.json

@@ -34,7 +34,8 @@
   "emits": [
     "registered",
     "upgraded",
-    "rebuild-needed"
+    "rebuild-needed",
+    "catching-up"
   ],
   "resources": [
     {