@llblab/pi-telegram 0.27.8 → 0.27.10

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.27.10: Leader Thread Rebind Hotfix
+
+- `Live Leader Target`: Reclaiming or replacing the current leader thread now updates the process-local leader identity immediately after the durable binding commits. Impact: live thread-name resolution no longer returns the deleted previous leader target, so another instance can address the rebound leader without receiving `message thread not found`.
+- `Rebind Coverage`: The explicit new-slot reroute regression now requires the durable record, live leader target, slot, and thread name to converge before old-thread cleanup. Impact: future Thread reconciler changes cannot update persisted state while leaving agent-message routing on a stale target.
+
+## 0.27.9: Symmetric Agent-Turn Metadata Hotfix
+
+- `Agent-Turn Prompt Shape`: Cross-instance turns now fold trusted source-thread attribution into the canonical Telegram prefix as `[telegram|thread:<destination>|from-thread:<source>] <message>` instead of emitting a separate `[agent|from-thread:<source>]` block. Impact: inter-thread prompts match the existing compact metadata grammar without allowing ordinary Telegram text to impersonate transport attribution.
+- `Transport Preservation`: Source-thread metadata travels as an internal serialized message field so leader-to-follower bus forwarding preserves it across the local IPC boundary. Focused regressions prove synthetic construction and final prompt formatting.
+
 ## 0.27.8: Bidirectional Thread Routing Hotfix
 
 - `Directional Ownership`: Internal cross-instance turns now bypass only ownership of the already-sent Telegram message id while preserving ownership of the destination thread. Impact: follower-to-leader turns avoid bouncing back to their sender, while leader-to-follower and follower-to-follower turns still forward through the destination follower's live registration.

package/docs/multi-instance-bus.md

@@ -281,7 +281,7 @@ Follower instances receive normalized events, not raw Telegram transport interna
 
 Followers do not call Telegram Bot API directly for routed Telegram work. Instead, they call a leader-owned transport port:
 
-Explicit `telegram_message(..., thread)` delivery also uses the bus as an agent-message plane. The leader resolves the case-insensitive name or numeric id against live leader/follower registrations, rejects ambiguous, stale, same-instance, cross-chat, and replayed requests, then coordinates visible Bot API delivery with one source-attributed synthetic turn routed through the destination instance's ordinary queue. The destination sees `[agent|from-thread:<name>]`, not an impersonated user message. Generation fencing and request-ledger deduplication apply to both resolution and routing.
+Explicit `telegram_message(..., thread)` delivery also uses the bus as an agent-message plane. The leader resolves the case-insensitive name or numeric id against live leader/follower registrations, rejects ambiguous, stale, same-instance, cross-chat, and replayed requests, then coordinates visible Bot API delivery with one source-attributed synthetic turn routed through the destination instance's ordinary queue. The destination sees `[telegram|thread:<destination>|from-thread:<source>]`, not an impersonated user message. Generation fencing and request-ledger deduplication apply to both resolution and routing.
 
 ```text
 follower reply/preview/upload/chat-action/download/callback-answer -> leader IPC -> Telegram API

package/index.ts

@@ -729,6 +729,7 @@ export default function (pi: Pi.ExtensionAPI) {
     recordMessageOwnership: messageOwnershipRuntime.recordRouted,
     ...inboundBusProjectionRuntime,
     getCurrentLeaderEpoch,
+    setCurrentLeaderIdentity: telegramBusLeaderState.set,
     getThreadReconciliationMachineState: threadReconciliationRuntime.getState,
     recordThreadReconciliationPlan,
     handleTelegramTopicLifecycleUpdate: topicLifecycleSync,

package/lib/agent-messages.ts

@@ -109,7 +109,8 @@ export function createTelegramAgentMessageRuntime<TContext, TUpdate>(
         chat: { id: target.chatId, type: "private" as const },
         from: { id: allowedChatId, is_bot: false, first_name: "Pi Agent" },
         message_thread_id: target.threadId,
-        text: `[agent|from-thread:${sourceLabel}]\n\n${input.message.text}`,
+        pi_telegram_agent_source_thread: sourceLabel,
+        text: input.message.text,
       } as TelegramRoutedMessage;
       await deps.handleUpdate(
         { message, [TELEGRAM_INTERNAL_AGENT_MESSAGE]: true } as TUpdate,

package/lib/routing.ts

@@ -523,6 +523,11 @@ export interface TelegramInboundRouteRuntimeDeps<
     target: Queue.TelegramQueueTarget,
   ) => string | undefined;
   getCurrentLeaderEpoch?: () => number | string | undefined;
+  setCurrentLeaderIdentity?: (identity: {
+    target: Queue.TelegramQueueTarget;
+    slot?: string;
+    threadName?: string;
+  }) => void;
   getThreadReconciliationMachineState?: () =>
     ThreadReconciler.ThreadReconciliationMachineState | undefined;
   recordThreadReconciliationPlan?: (
@@ -1359,6 +1364,11 @@ export function createTelegramInboundRouteRuntime<
         rerouteConfirmedAtMs: nowMs,
       });
       await deps.threadStore.persist();
+      deps.setCurrentLeaderIdentity?.({
+        target: sourceTarget,
+        slot,
+        threadName,
+      });
       if (deps.callApi) {
         try {
           await deps.callApi("editForumTopic", {
@@ -2340,6 +2350,11 @@ export function createTelegramInboundRouteRuntime<
             slot,
           });
           await deps.threadStore.persist();
+          deps.setCurrentLeaderIdentity?.({
+            target: { chatId: target.chatId, threadId: target.threadId },
+            slot,
+            threadName,
+          });
           deps.recordRuntimeEvent?.(
             "bus",
             "Bus leader reclaimed unbound thread",
@@ -2449,6 +2464,11 @@ export function createTelegramInboundRouteRuntime<
               slot,
             });
             await deps.threadStore.persist();
+            deps.setCurrentLeaderIdentity?.({
+              target: { chatId: target.chatId, threadId: target.threadId },
+              slot,
+              threadName,
+            });
             deps.recordRuntimeEvent?.(
               "bus",
               "Bus leader reclaimed stale-current unbound thread",
@@ -2515,6 +2535,11 @@ export function createTelegramInboundRouteRuntime<
           slot,
         });
         await deps.threadStore.persist();
+        deps.setCurrentLeaderIdentity?.({
+          target: { chatId: target.chatId, threadId: target.threadId },
+          slot,
+          threadName,
+        });
         deps.recordRuntimeEvent?.(
           "bus",
           "Bus leader reclaimed unbound thread",

package/lib/turns.ts

@@ -54,6 +54,7 @@ export interface TelegramTurnTarget {
 export interface TelegramTurnMessage {
   message_id: number;
   message_thread_id?: number;
+  pi_telegram_agent_source_thread?: string;
   chat: { id: number; type?: string };
 }
 
@@ -552,7 +553,10 @@ export function createTelegramPromptTurnRuntimeBuilder<
     const threadLabel = firstMessage
       ? deps.getTelegramThreadLabel?.(firstMessage)
       : undefined;
-    const telegramPrefix = createTelegramTurnPrefix({ thread: threadLabel });
+    const telegramPrefix = createTelegramTurnPrefix({
+      thread: threadLabel,
+      "from-thread": firstMessage?.pi_telegram_agent_source_thread,
+    });
     return buildTelegramPromptTurnRuntime({
       telegramPrefix,
       messages,

package/lib/updates.ts

@@ -129,6 +129,7 @@ export interface TelegramUpdateMessage {
   from?: TelegramUser;
   message_id?: number;
   message_thread_id?: number;
+  pi_telegram_agent_source_thread?: string;
   forum_topic_created?: unknown;
   forum_topic_closed?: unknown;
   forum_topic_reopened?: unknown;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-telegram",
-  "version": "0.27.8",
+  "version": "0.27.10",
   "private": false,
   "publishConfig": {
     "access": "public"