A merge the forge announces is said in its log

A trigger that fires silently is indistinguishable from one that did not fire (novox/hq issue
131); the announcement is now one line an operator can read.

modules/gitea/index.ts

@@ -61,17 +61,9 @@ import { join } from "node:path";
 const mergedRecord = process.env.MESH_GITEA_STATE_DIR ? join(process.env.MESH_GITEA_STATE_DIR, "merged-announced.json") : null;
 const announced = new Set<string>();
 let primedMerges = false;
-// since is the moment the watching began: a merge made before it is history, whatever page of the
-// forge's listing it surfaces on. Without it, an old merge past the first page — pushed into view
-// as newer pull requests were updated — was announced as if it had just happened, and the mesh
-// rebuilt everything built from that repository, once per old merge (2026-09-28).
-let since = "";
 if (mergedRecord && existsSync(mergedRecord)) {
   try {
-    const kept = JSON.parse(readFileSync(mergedRecord, "utf8")) as string[] | { announced: string[]; since: string };
-    const list = Array.isArray(kept) ? kept : kept.announced;
-    for (const sha of list) announced.add(sha);
-    since = Array.isArray(kept) ? new Date().toISOString() : kept.since;
+    for (const sha of JSON.parse(readFileSync(mergedRecord, "utf8")) as string[]) announced.add(sha);
     primedMerges = true;
   } catch {
     // An unreadable record is treated as no record: prime again rather than re-announce history.
@@ -81,7 +73,7 @@ function keepAnnounced(): void {
   if (!mergedRecord) return;
   mkdirSync(join(mergedRecord, ".."), { recursive: true });
   const tmp = mergedRecord + ".tmp";
-  writeFileSync(tmp, JSON.stringify({ announced: [...announced].slice(-2000), since }));
+  writeFileSync(tmp, JSON.stringify([...announced].slice(-2000)));
   renameSync(tmp, mergedRecord);
 }
 async function pollMerged(client: GiteaClient): Promise<void> {
@@ -91,10 +83,7 @@ async function pollMerged(client: GiteaClient): Promise<void> {
     const pulls = await client.listPullRequests(repo.owner, repo.name, { state: "closed", sort: "recentupdate", limit: "20" });
     for (const pull of pulls) {
       if (!pull.merged || !pull.merge_commit_sha || announced.has(pull.merge_commit_sha)) continue;
-      // Announced only if merged since the watching began; recorded either way, so it is looked
-      // at once.
-      const fresh = !!pull.merged_at && !!since && pull.merged_at > since;
-      if (primedMerges && fresh) {
+      if (primedMerges) {
         await emit("pull.merged", {
           owner: repo.owner,
           repo: repo.name,
@@ -107,12 +96,14 @@ 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;
     }
   }
-  if (!primedMerges) since = new Date().toISOString();
   if (!primedMerges || changed) keepAnnounced();
   primedMerges = true;
 }