@agfpd/iapeer 0.2.92 → 0.2.93

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agfpd/iapeer",
-  "version": "0.2.92",
+  "version": "0.2.93",
   "description": "Foundation core for the iapeer multi-agent ecosystem: identity, registry, storage, codec.",
   "license": "Apache-2.0",
   "author": "agfpd",

package/src/daemon/main.ts

@@ -237,6 +237,24 @@ export function makeComposerQueueRouteDeps(cfg: LifecycleConfig, env: NodeJS.Pro
         return
       }
       const sender = resolveCallerIdentity({ personality: 'iapeer', runtime: self.runtime }, index)
+      // SELF-NOTIFY GUARD: the failure outlet sends FROM the foundation peer (iapeer). When the QUEUED
+      // sender IS the foundation peer on the same runtime (e.g. iapeer itself queued a cross-runtime send to
+      // its codex twin and that queue later failed), this notify would be iapeer→iapeer — a genuine
+      // self-send the address-based router correctly refuses with 'cannot send to self', logging ok=false
+      // and tripping monitoring alarms. The notification is moot anyway (the sender IS the one being
+      // notified about its own send). Skip it and log a benign skip instead of attempting a self-send.
+      if (`${job.caller.runtime}-${job.caller.personality}` === sender.address) {
+        appendDeliveryEvent(cfg.eventLogDir, {
+          ev: 'composer-queue-failed-notify',
+          caller: sender.address,
+          to: job.caller.personality,
+          rt: job.caller.runtime,
+          ok: 'true',
+          err: 'skipped self-notify (queued sender is the foundation peer itself)',
+          topic: job.topic ?? 'delivery-failed',
+        })
+        return
+      }
       const result = await routeSend(
         sender,
         {