instar 1.3.164 → 1.3.166

package/dist/messaging/installAgentMessageHook.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"installAgentMessageHook.d.ts","sourceRoot":"","sources":["../../src/messaging/installAgentMessageHook.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EAEL,KAAK,eAAe,EAEpB,KAAK,UAAU,EAChB,MAAM,yBAAyB,CAAC;AACjC,OAAO,KAAK,EAAE,mBAAmB,EAAmB,MAAM,0BAA0B,CAAC;AACrF,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAC9D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AAE7D;oFACoF;AACpF,MAAM,MAAM,WAAW,GAAG,CAAC,GAAG,EAAE,UAAU,EAAE,GAAG,EAAE;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,WAAW,CAAC,EAAE,MAAM,CAAA;CAAE,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;AAE7G,MAAM,WAAW,2BAA2B;IAC1C,MAAM,EAAE,eAAe,CAAC;IACxB,MAAM,EAAE,mBAAmB,CAAC;IAC5B,YAAY,EAAE,gBAAgB,CAAC;IAC/B;;sDAEkD;IAClD,YAAY,EAAE,GAAG,CAAC,MAAM,EAAE,WAAW,CAAC,CAAC;CACxC;AAED;;;;;GAKG;AACH,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,2BAA2B,GAAG,gBAAgB,CAuFzF"}
+{"version":3,"file":"installAgentMessageHook.d.ts","sourceRoot":"","sources":["../../src/messaging/installAgentMessageHook.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EAEL,KAAK,eAAe,EAEpB,KAAK,UAAU,EAChB,MAAM,yBAAyB,CAAC;AACjC,OAAO,KAAK,EAAE,mBAAmB,EAAmB,MAAM,0BAA0B,CAAC;AACrF,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAC9D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AAE7D;oFACoF;AACpF,MAAM,MAAM,WAAW,GAAG,CAAC,GAAG,EAAE,UAAU,EAAE,GAAG,EAAE;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,WAAW,CAAC,EAAE,MAAM,CAAA;CAAE,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;AAE7G,MAAM,WAAW,2BAA2B;IAC1C,MAAM,EAAE,eAAe,CAAC;IACxB,MAAM,EAAE,mBAAmB,CAAC;IAC5B,YAAY,EAAE,gBAAgB,CAAC;IAC/B;;sDAEkD;IAClD,YAAY,EAAE,GAAG,CAAC,MAAM,EAAE,WAAW,CAAC,CAAC;CACxC;AAED;;;;;GAKG;AACH,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,2BAA2B,GAAG,gBAAgB,CAkGzF"}

package/dist/messaging/installAgentMessageHook.js

@@ -83,16 +83,26 @@ export function buildAgentMessageHook(deps) {
             telegramSenderChatId: input.senderChatId,
             topicId: input.topicId,
         });
-        try {
-            await handler(msg, { topicId: input.topicId, senderBotId: input.senderBotId });
-        }
-        catch (err) {
-            // A role-handler failure is recorded but doesn't un-mark the id (we still treat
-            // the message as processed; retrying would just re-fail). Stage-B forensics can see
-            // the routed row + the absence of a downstream effect.
+        // Accept-boundary (the #581 / #3 class — this is the THIRD a2a path): a role
+        // handler (e.g. the mentee mentor-message handler) SPAWNS a session and
+        // bounded-waits for the reply — that can take MINUTES — and delivers its
+        // reply OUT via a separate a2a message, not this HTTP response. AWAITING it
+        // here meant the caller's /a2a/inbox POST waited the full handler, so the
+        // sender's ~10s `AbortSignal.timeout` fired and logged a FALSE "local-inbox
+        // delivery attempt failed" (the message was in fact accepted — its id is
+        // marked processed above — and the reply will arrive on its own channel).
+        // Respond ACCEPTED immediately and run the handler in the background. The
+        // idempotency mark above still dedups any retry; a handler failure is caught
+        // + logged async (it can't reject a response that already returned).
+        void Promise.resolve()
+            .then(() => handler(msg, { topicId: input.topicId, senderBotId: input.senderBotId }))
+            .catch((err) => {
+            // A role-handler failure is recorded but doesn't un-mark the id (we still
+            // treat the message as processed; retrying would just re-fail). Stage-B
+            // forensics can see the routed row + the absence of a downstream effect.
             // eslint-disable-next-line no-console
             console.error(`[a2a] role-handler "${msg.role}" failed:`, err instanceof Error ? err.message : String(err));
-        }
+        });
         return { handled: true };
     };
 }

package/dist/messaging/installAgentMessageHook.js.map

@@ -1 +1 @@
-{"version":3,"file":"installAgentMessageHook.js","sourceRoot":"","sources":["../../src/messaging/installAgentMessageHook.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EACL,WAAW,GAIZ,MAAM,yBAAyB,CAAC;AAmBjC;;;;;GAKG;AACH,MAAM,UAAU,qBAAqB,CAAC,IAAiC;IACrE,MAAM,KAAK,GAAG,CAAC,EAAU,EAAE,EAAE,CAAC,IAAI,IAAI,CAAC,EAAE,CAAC,CAAC,WAAW,EAAE,CAAC;IAEzD,OAAO,KAAK,EAAE,KAAK,EAAE,EAAE;QACrB,MAAM,GAAG,GAAoB;YAC3B,GAAG,EAAE,KAAK,CAAC,IAAI;YACf,WAAW,EAAE,KAAK,CAAC,WAAW;YAC9B,YAAY,EAAE,KAAK,CAAC,YAAY;YAChC,WAAW,EAAE,KAAK,CAAC,WAAW;YAC9B,GAAG,EAAE,KAAK,CAAC,GAAG;SACf,CAAC;QACF,MAAM,QAAQ,GAAG,WAAW,CAC1B,GAAG,EACH,IAAI,CAAC,MAAM,EACX;YACE,WAAW,EAAE,CAAC,EAAE,EAAE,EAAE,CAAC,IAAI,CAAC,YAAY,CAAC,YAAY,CAAC,EAAE,CAAC;YACvD,SAAS,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,CAAC,CAAC;SAC3C,CACF,CAAC;QAEF,IAAI,QAAQ,CAAC,MAAM,KAAK,cAAc,EAAE,CAAC;YACvC,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;QAC5B,CAAC;QAED,IAAI,QAAQ,CAAC,MAAM,KAAK,MAAM,EAAE,CAAC;YAC/B,MAAM,GAAG,GAAoB;gBAC3B,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC;gBACzB,SAAS,EAAE,UAAU;gBACrB,QAAQ,EAAE,SAAS;gBACnB,UAAU,EAAE,QAAQ,CAAC,MAAM;gBAC3B,SAAS,EAAE,QAAQ,CAAC,GAAG,EAAE,IAAI;gBAC7B,OAAO,EAAE,QAAQ,CAAC,GAAG,EAAE,EAAE;gBACzB,IAAI,EAAE,QAAQ,CAAC,GAAG,EAAE,IAAI;gBACxB,EAAE,EAAE,QAAQ,CAAC,GAAG,EAAE,EAAE;gBACpB,IAAI,EAAE,QAAQ,CAAC,GAAG,EAAE,IAAI;gBACxB,EAAE,EAAE,QAAQ,CAAC,GAAG,EAAE,EAAE;gBACpB,iBAAiB,EAAE,KAAK,CAAC,WAAW;gBACpC,oBAAoB,EAAE,KAAK,CAAC,YAAY;gBACxC,OAAO,EAAE,KAAK,CAAC,OAAO;gBACtB,SAAS,EAAE,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,EAAE,GAAG,CAAC;aACpC,CAAC;YACF,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC,GAAG,CAAC,CAAC;YAChC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;QAC3B,CAAC;QAED,qBAAqB;QACrB,MAAM,GAAG,GAAG,QAAQ,CAAC,GAAG,CAAC;QACzB,MAAM,OAAO,GAAG,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAChD,IAAI,CAAC,OAAO,EAAE,CAAC;YACb,mFAAmF;YACnF,iEAAiE;YACjE,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC;gBACzB,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC;gBACzB,SAAS,EAAE,UAAU;gBACrB,QAAQ,EAAE,SAAS;gBACnB,UAAU,EAAE,2BAA2B;gBACvC,SAAS,EAAE,GAAG,CAAC,IAAI,EAAE,OAAO,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE;gBAC5F,iBAAiB,EAAE,KAAK,CAAC,WAAW;gBACpC,oBAAoB,EAAE,KAAK,CAAC,YAAY;gBACxC,OAAO,EAAE,KAAK,CAAC,OAAO;aACvB,CAAC,CAAC;YACH,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;QAC3B,CAAC;QAED,qFAAqF;QACrF,gFAAgF;QAChF,IAAI,CAAC,YAAY,CAAC,aAAa,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QACxC,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC;YACzB,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC;YACzB,SAAS,EAAE,UAAU;YACrB,QAAQ,EAAE,QAAQ;YAClB,SAAS,EAAE,GAAG,CAAC,IAAI,EAAE,OAAO,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE;YAC5F,iBAAiB,EAAE,KAAK,CAAC,WAAW;YACpC,oBAAoB,EAAE,KAAK,CAAC,YAAY;YACxC,OAAO,EAAE,KAAK,CAAC,OAAO;SACvB,CAAC,CAAC;QACH,IAAI,CAAC;YACH,MAAM,OAAO,CAAC,GAAG,EAAE,EAAE,OAAO,EAAE,KAAK,CAAC,OAAO,EAAE,WAAW,EAAE,KAAK,CAAC,WAAW,EAAE,CAAC,CAAC;QACjF,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,gFAAgF;YAChF,oFAAoF;YACpF,uDAAuD;YACvD,sCAAsC;YACtC,OAAO,CAAC,KAAK,CAAC,uBAAuB,GAAG,CAAC,IAAI,WAAW,EAAE,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC;QAC9G,CAAC;QACD,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;IAC3B,CAAC,CAAC;AACJ,CAAC"}
+{"version":3,"file":"installAgentMessageHook.js","sourceRoot":"","sources":["../../src/messaging/installAgentMessageHook.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EACL,WAAW,GAIZ,MAAM,yBAAyB,CAAC;AAmBjC;;;;;GAKG;AACH,MAAM,UAAU,qBAAqB,CAAC,IAAiC;IACrE,MAAM,KAAK,GAAG,CAAC,EAAU,EAAE,EAAE,CAAC,IAAI,IAAI,CAAC,EAAE,CAAC,CAAC,WAAW,EAAE,CAAC;IAEzD,OAAO,KAAK,EAAE,KAAK,EAAE,EAAE;QACrB,MAAM,GAAG,GAAoB;YAC3B,GAAG,EAAE,KAAK,CAAC,IAAI;YACf,WAAW,EAAE,KAAK,CAAC,WAAW;YAC9B,YAAY,EAAE,KAAK,CAAC,YAAY;YAChC,WAAW,EAAE,KAAK,CAAC,WAAW;YAC9B,GAAG,EAAE,KAAK,CAAC,GAAG;SACf,CAAC;QACF,MAAM,QAAQ,GAAG,WAAW,CAC1B,GAAG,EACH,IAAI,CAAC,MAAM,EACX;YACE,WAAW,EAAE,CAAC,EAAE,EAAE,EAAE,CAAC,IAAI,CAAC,YAAY,CAAC,YAAY,CAAC,EAAE,CAAC;YACvD,SAAS,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,CAAC,CAAC;SAC3C,CACF,CAAC;QAEF,IAAI,QAAQ,CAAC,MAAM,KAAK,cAAc,EAAE,CAAC;YACvC,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;QAC5B,CAAC;QAED,IAAI,QAAQ,CAAC,MAAM,KAAK,MAAM,EAAE,CAAC;YAC/B,MAAM,GAAG,GAAoB;gBAC3B,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC;gBACzB,SAAS,EAAE,UAAU;gBACrB,QAAQ,EAAE,SAAS;gBACnB,UAAU,EAAE,QAAQ,CAAC,MAAM;gBAC3B,SAAS,EAAE,QAAQ,CAAC,GAAG,EAAE,IAAI;gBAC7B,OAAO,EAAE,QAAQ,CAAC,GAAG,EAAE,EAAE;gBACzB,IAAI,EAAE,QAAQ,CAAC,GAAG,EAAE,IAAI;gBACxB,EAAE,EAAE,QAAQ,CAAC,GAAG,EAAE,EAAE;gBACpB,IAAI,EAAE,QAAQ,CAAC,GAAG,EAAE,IAAI;gBACxB,EAAE,EAAE,QAAQ,CAAC,GAAG,EAAE,EAAE;gBACpB,iBAAiB,EAAE,KAAK,CAAC,WAAW;gBACpC,oBAAoB,EAAE,KAAK,CAAC,YAAY;gBACxC,OAAO,EAAE,KAAK,CAAC,OAAO;gBACtB,SAAS,EAAE,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,EAAE,GAAG,CAAC;aACpC,CAAC;YACF,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC,GAAG,CAAC,CAAC;YAChC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;QAC3B,CAAC;QAED,qBAAqB;QACrB,MAAM,GAAG,GAAG,QAAQ,CAAC,GAAG,CAAC;QACzB,MAAM,OAAO,GAAG,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAChD,IAAI,CAAC,OAAO,EAAE,CAAC;YACb,mFAAmF;YACnF,iEAAiE;YACjE,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC;gBACzB,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC;gBACzB,SAAS,EAAE,UAAU;gBACrB,QAAQ,EAAE,SAAS;gBACnB,UAAU,EAAE,2BAA2B;gBACvC,SAAS,EAAE,GAAG,CAAC,IAAI,EAAE,OAAO,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE;gBAC5F,iBAAiB,EAAE,KAAK,CAAC,WAAW;gBACpC,oBAAoB,EAAE,KAAK,CAAC,YAAY;gBACxC,OAAO,EAAE,KAAK,CAAC,OAAO;aACvB,CAAC,CAAC;YACH,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;QAC3B,CAAC;QAED,qFAAqF;QACrF,gFAAgF;QAChF,IAAI,CAAC,YAAY,CAAC,aAAa,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QACxC,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC;YACzB,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC;YACzB,SAAS,EAAE,UAAU;YACrB,QAAQ,EAAE,QAAQ;YAClB,SAAS,EAAE,GAAG,CAAC,IAAI,EAAE,OAAO,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,GAAG,CAAC,EAAE;YAC5F,iBAAiB,EAAE,KAAK,CAAC,WAAW;YACpC,oBAAoB,EAAE,KAAK,CAAC,YAAY;YACxC,OAAO,EAAE,KAAK,CAAC,OAAO;SACvB,CAAC,CAAC;QACH,6EAA6E;QAC7E,wEAAwE;QACxE,yEAAyE;QACzE,4EAA4E;QAC5E,0EAA0E;QAC1E,4EAA4E;QAC5E,yEAAyE;QACzE,0EAA0E;QAC1E,0EAA0E;QAC1E,6EAA6E;QAC7E,qEAAqE;QACrE,KAAK,OAAO,CAAC,OAAO,EAAE;aACnB,IAAI,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,GAAG,EAAE,EAAE,OAAO,EAAE,KAAK,CAAC,OAAO,EAAE,WAAW,EAAE,KAAK,CAAC,WAAW,EAAE,CAAC,CAAC;aACpF,KAAK,CAAC,CAAC,GAAG,EAAE,EAAE;YACb,0EAA0E;YAC1E,wEAAwE;YACxE,yEAAyE;YACzE,sCAAsC;YACtC,OAAO,CAAC,KAAK,CAAC,uBAAuB,GAAG,CAAC,IAAI,WAAW,EAAE,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC;QAC9G,CAAC,CAAC,CAAC;QACL,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;IAC3B,CAAC,CAAC;AACJ,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "1.3.164",
+  "version": "1.3.166",
   "description": "Coherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.",
   "type": "module",
   "main": "dist/index.js",

package/src/data/builtin-manifest.json

@@ -1,8 +1,8 @@
 {
   "$schema": "./builtin-manifest.schema.json",
   "schemaVersion": 1,
-  "generatedAt": "2026-05-31T11:18:35.637Z",
-  "instarVersion": "1.3.164",
+  "generatedAt": "2026-05-31T12:02:03.497Z",
+  "instarVersion": "1.3.166",
   "entryCount": 193,
   "entries": {
     "hook:session-start": {

package/upgrades/1.3.165.md

@@ -0,0 +1,47 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What to Tell Your User
+
+If you run your agent across more than one machine and move a conversation to another
+one, that conversation can now reply to you — its replies are relayed through the
+machine that owns your messaging bot, so you hear back without any risk of the two
+machines clashing over the bot. Only relevant when the multi-machine session pool is
+on; single-machine agents are unaffected. Nothing to configure.
+
+## Summary of New Capabilities
+
+- `TelegramAdapter` gains an `outboundRelay` hook. When the adapter has no bot token,
+  `sendToTopic` routes the send through it (the server wires it to POST the
+  Telegram-owning lease holder's `/telegram/reply`), instead of failing silently. A
+  token-holding adapter sends directly as before; a relay that can't deliver throws
+  rather than dropping the message.
+
+## Evidence
+
+- Found live: the backup machine's Telegram adapter had no bot token, so a moved
+  session's reply was sent with no token and silently vanished.
+- Unit, `tests/unit/TelegramAdapter.test.ts`: a tokenless adapter routes the send
+  through the relay (the Telegram API is not hit, the relayed id is returned); a
+  token-holding adapter sends directly and never consults the relay; a relay that
+  returns nothing throws instead of silently dropping the reply.
+- 19 TelegramAdapter tests pass; tsc --noEmit clean.
+- Spec, `docs/specs/standby-telegram-outbound-relay.md` plus the .eli16.md sibling.
+- Side-effects, `upgrades/side-effects/standby-telegram-outbound-relay.md`.
+
+## What Changed — a conversation moved to your other machine can now reply to you
+
+The final piece of the multi-machine "move this conversation to my other machine"
+feature. Telegram only allows one program to use a given bot at a time, so in a
+two-machine setup only the main machine holds the bot, and the backup deliberately
+holds none (to avoid two programs fighting over the same bot — a real failure we fixed
+earlier). That meant a conversation moved to the backup machine could run there but
+couldn't actually send a reply — it came out silent.
+
+This release adds a relay: when the backup machine wants to reply but has no bot, it
+hands the message to the machine that does hold the bot, which sends it normally. So
+your reply comes through, and there's still only ever one program using the bot — no
+fighting, no duplicate messages. A machine that holds its own bot is completely
+unaffected.

package/upgrades/1.3.166.md

@@ -0,0 +1,24 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What to Tell Your User
+
+If you run multiple agents that talk to each other, you'll stop seeing spurious "delivery failed" timeouts in the logs for messages that actually went through fine. The receiving agent now confirms it got the message right away and does the work in the background, and the reply still comes back as normal.
+
+## Summary of New Capabilities
+
+- The agent-to-agent inbox hook (the third and last of the agent-to-agent transports) now responds at the accept boundary: it acknowledges immediately after validating the message and runs the (potentially minutes-long) handler in the background, instead of making the sender wait through it. Completes the same fix already shipped for the co-located relay and the cross-machine threadline paths.
+
+## Evidence
+
+- Found in the agent's own server log: recurring "[a2a] local-inbox delivery attempt failed (to=instar-codey): aborted due to timeout".
+- Root traced through the call chain: the /a2a/inbox response awaited the role handler, which spawns a session and waits minutes; the sender's ~10s timeout fired first. The reply flows back on a separate channel, so awaiting was unnecessary.
+- Unit tests: a held (slow) handler no longer blocks the response (it would have hung if still awaited); a background handler error still yields a clean acknowledgement. Idempotency, validation, and spoof-defense cases unchanged. Independent adversarial review.
+
+## What Changed — Agent-to-agent task delivery no longer logs false "delivery failed" timeouts
+
+When one of your agents hands a task to another agent on the same machine (for example a mentor agent assigning work to a mentee), the receiver was only acknowledging the message AFTER it had finished the whole task — which means spinning up a work session and waiting minutes for it to think and reply. But the sender only waits about 10 seconds for an acknowledgement, so it gave up and logged a "delivery failed" every time — even though the message was actually received fine and the reply was on its way back on a separate channel.
+
+Now the receiver acknowledges the moment it accepts the message and does the work in the background. The sender gets its acknowledgement right away, stops logging false failures, and stops holding a connection open for ten seconds each time. The actual reply still comes back exactly as before.

package/upgrades/side-effects/a2a-inbox-accept-boundary.md

@@ -0,0 +1,40 @@
+# Side-effects — /a2a/inbox accept-boundary
+
+## 1. What files/state does this touch at runtime?
+`installAgentMessageHook.ts` — the role-handler invocation in the agent-message hook. No new files,
+config, schema, or state. The role handler still runs (now in the background); the idempotency mark
+and ledger row are unchanged.
+
+## 2. Does it change any functional behavior?
+The `/a2a/inbox` HTTP response now returns `{handled:true}` immediately after the message is validated
++ marked processed, instead of after the (minutes-long) role handler completes. The handler runs in
+the background and delivers its reply on its own a2a channel exactly as before. Net: the sender no
+longer times out (its ~10s `AbortSignal.timeout`) and no longer logs a false "delivery failed".
+
+## 3. What happens on failure / weird config?
+A background handler rejection is caught and logged (`console.error`), exactly as the old `try/catch`
+did — just on a later microtask. The id stays marked processed (unchanged). Validation failures
+(unknown role, spoof, already-processed) still short-circuit BEFORE the handler, unchanged.
+
+## 4. Migration parity — do existing agents get it?
+Yes, via the normal release — code-only, compiled into `dist`. No agent-installed file / config /
+template change → no `PostUpdateMigrator` pass.
+
+## 5. Could it spam / flood / burn resources?
+No — it REDUCES resource use (no 10s held connection per mentor a2a message). Same single handler
+run, no new timers/IO/network. The idempotency mark still bounds duplicate processing.
+
+## 6. Rollback / off-switch?
+Revert the one block (re-`await` the handler). No data, no migration, no flag. Mirrors #581/#3
+rollback.
+
+## 7. Concurrency / ordering?
+The handler now runs after the response returns instead of before. The idempotency `markProcessed`
+still happens BEFORE the response (so retries dedup). The reply-out is unchanged (a separate a2a
+send). A background handler error cannot affect the already-sent response.
+
+## Blast radius
+Small + additive: one block in `installAgentMessageHook.ts` swapped from await-then-respond to
+respond-then-background. Exactly mirrors the proven #581 (`/messages/relay-agent`) and #3
+(`/threadline/messages/receive`) accept-boundaries. Only the a2a role-handler dispatch timing
+changes; validation, idempotency, ledger, and the reply path are untouched.

package/upgrades/side-effects/standby-telegram-outbound-relay.md

@@ -0,0 +1,100 @@
+# Side-Effects Review — Tokenless standby Telegram outbound relay (bug #7)
+
+**Version / slug:** `standby-telegram-outbound-relay`
+**Date:** `2026-05-31`
+**Author:** `echo`
+**Second-pass reviewer:** `not required`
+
+## Summary of the change
+
+`TelegramAdapter` gains a settable `outboundRelay` callback. In `sendToTopic`, when
+the adapter has NO bot token AND a relay is wired, the send routes through the relay
+instead of the Telegram API (the relayed id feeds the same log/stall/promise
+bookkeeping); a relay returning null throws. `server.ts` wires the relay to POST the
+lease holder's `/telegram/reply/:topicId` (Bearer authToken + the holder's peer URL),
+refusing to relay to self/unknown. Closes bug #7 (a session moved to a tokenless
+standby was mute).
+
+## Decision-point inventory
+
+- **sendToTopic branch** — `!this.config.token && this.outboundRelay` → relay; else →
+  the unchanged API path. Both covered by tests.
+- **relay closure** — `holder` is self or unknown, or no URL → return null (no
+  relay); else POST and return the id (or null on non-ok / throw). Self-relay guard
+  + null-on-failure tested via the adapter-level null case.
+
+## 1. Over-block
+
+**What legitimate inputs does this reject?** Nothing for a token-holding machine — its
+send path is byte-identical (the relay branch is skipped). For a tokenless standby, a
+send that previously failed silently (no token) now either relays successfully or
+throws a clear error (better than the silent mute). No legitimate send is dropped.
+
+## 2. Under-block
+
+**What does this still miss?** It does not sync conversation CONTEXT to the moved
+session (audit #2 — the reply may lack prior history). It relays to the current lease
+holder only (correct for the single-Telegram-owner model); if the holder is
+unreachable it returns null → `sendToTopic` throws (surfaced, not silent). It does not
+retry/queue a failed relay (the caller/​session sees the throw); a durable relay queue
+is possible later but out of scope.
+
+## 3. Level-of-abstraction fit
+
+**Right layer?** Yes. The send decision lives in `TelegramAdapter.sendToTopic` (the
+one outbound chokepoint), expressed as an injected callback (same pattern as the
+adapter's other `on*` hooks). The cross-machine resolution (holder → URL → POST) lives
+in `server.ts` where the mesh/coordinator/authToken are already in scope. The relay
+reuses the existing `/telegram/reply` route rather than a new mesh command.
+
+## 4. Signal vs authority compliance
+
+**Required reference:** [docs/signal-vs-authority.md](../../docs/signal-vs-authority.md)
+
+No new blocking authority. It changes HOW a tokenless adapter sends (relay vs direct),
+not WHETHER. It preserves the single-Telegram-owner safety invariant (the standby
+never sends on the bot directly), which is the 409-conflict guard — strengthening, not
+weakening, a safety property.
+
+## 5. Interactions
+
+The relay POSTs the holder's `/telegram/reply` — the same route used for normal
+replies — so the message goes out the one bot the holder owns; no second poller/sender
+(no 409). Pairs with the lease coordinator (`getSyncStatus().leaseHolder` picks the
+target) and peer presence (`peerUrl`). On a token-holding router the callback is wired
+but never invoked. Idempotent per call; a failed relay throws (the session's reply
+attempt errors rather than silently vanishing).
+
+## 6. External surfaces
+
+One cross-machine HTTP POST from a tokenless standby to the holder's existing
+`/telegram/reply` (Bearer-authed). No new route, config, or notification. The visible
+effect: a moved session's replies reach the user (via the holder's bot).
+
+## 7. Rollback cost
+
+Low. Remove the `outboundRelay` callback + the `sendToTopic` branch + the wiring; a
+tokenless standby's sends revert to silent failure (bug #7). No schema, no state, no
+migration (the callback is in-memory, default null).
+
+## Conclusion
+
+Minimal, injected-callback change scoped to the tokenless-send path, reusing the
+existing reply route, preserving the single-owner 409-guard, both branches + the
+null-failure case unit-tested, no change for token-holding machines, cheap revert.
+The completion gate for the live transfer — a moved session can now reply.
+
+## Second-pass review (if required)
+
+Not required — scoped to the no-token send path, reuses a battle-tested route,
+strengthens (not weakens) the single-owner invariant, both branches + failure tested,
+reversible. The live two-machine re-test (a reply landing) is the Tier-3 gate.
+
+## Evidence pointers
+
+- `tests/unit/TelegramAdapter.test.ts` — tokenless adapter relays (API not hit, relayed
+  id returned); token-holding adapter sends directly (relay not consulted); relay→null
+  throws (no silent mute).
+- 19 TelegramAdapter tests green; `tsc --noEmit` clean.
+- Found live: mini telegram adapter `botToken=MISSING` → a moved session's reply muted.
+- Spec: `docs/specs/standby-telegram-outbound-relay.md` (+ `.eli16.md`).