@llblab/pi-telegram 0.10.2 → 0.10.4

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.10.4: Polling Status Resilience Hotfix
+
+- `[Polling]` Status-bar updates from the polling loop are now best-effort and no longer crash the extension when a captured session context becomes stale after session reload. Failures are recorded as structured polling runtime events with `phase: "status-update"`. Impact: polling cleanup and retry status updates stay resilient without changing the Telegram API, config, or operator workflow.
+- `[Tests]` Added stale-context polling regressions for startup, cleanup, and retry status updates. Impact: the external PR #43 fix is now covered by maintainer-side tests and kept aligned with local style.
+
+## 0.10.3: Dependency Audit Hotfix
+
+- `[Dependencies]` Refreshed the lockfile transitive dependency set to resolve current `protobufjs` / `@protobufjs/utf8` npm audit advisories inherited through development peer installs. Impact: `npm run validate` is green again without changing runtime API or bridge behavior.
+
 ## 0.10.2: Delete Message Port Hotfix
 
 - `[ctx.deleteMessage()]` Added `deleteMessage()` to `TelegramSectionContext` and `TelegramSectionCallbackContext`. Extensions can now delete the message that triggered a callback — useful for cleaning up confirmation dialogs after the user makes a choice.

package/README.md

@@ -236,6 +236,16 @@ Import from `@llblab/pi-telegram`, call `registerTelegramSection()`, and return
 - Replies to Telegram prompts are sent as Telegram replies to the source message when possible; if the source message is unavailable, delivery falls back to a normal message.
 - Temporary inbound Telegram files are cleaned up on later session starts.
 
+## Companion Extensions
+
+Third-party extensions that integrate with `pi-telegram`:
+
+- [`pi-telegram-tool-status`](https://github.com/Timur00Kh/pi-telegram-tool-status) — Live-updating service messages that list tools used by the agent. It keeps one message per Telegram prompt and edits it in place as tools execute.
+
+```bash
+pi install npm:pi-telegram-tool-status
+```
+
 ## License
 
 MIT

package/lib/polling.ts

@@ -91,7 +91,8 @@ export function createTelegramPollingActivityReader(
   return () => isTelegramPollingControllerActive(state);
 }
 
-export interface TelegramPollingRuntimeDeps<TContext> {
+export interface TelegramPollingRuntimeDeps<TContext>
+  extends TelegramRuntimeEventRecorderPort {
   hasBotToken: () => boolean;
   getPollingPromise: () => Promise<void> | undefined;
   setPollingPromise: (promise: Promise<void> | undefined) => void;
@@ -150,6 +151,7 @@ export function createTelegramPollingControllerRuntime<
     }),
     updateStatus: deps.updateStatus,
     createAbortController: deps.createAbortController,
+    recordRuntimeEvent: deps.recordRuntimeEvent,
   });
 }
 
@@ -191,6 +193,22 @@ export async function stopTelegramPollingRuntime<TContext>(
   deps.setPollingPromise(undefined);
 }
 
+function updateTelegramPollingStatusSafely<TContext>(
+  updateStatus: (ctx: TContext, message?: string) => void,
+  ctx: TContext,
+  options: {
+    message?: string;
+    recordRuntimeEvent?: TelegramRuntimeEventRecorderPort["recordRuntimeEvent"];
+  } = {},
+): void {
+  try {
+    updateStatus(ctx, options.message);
+  } catch (error) {
+    // The polling loop can outlive the session context it captured.
+    options.recordRuntimeEvent?.("polling", error, { phase: "status-update" });
+  }
+}
+
 export function startTelegramPollingRuntime<TContext>(
   ctx: TContext,
   deps: TelegramPollingRuntimeDeps<TContext>,
@@ -208,10 +226,14 @@ export function startTelegramPollingRuntime<TContext>(
   const promise = deps.runPollLoop(ctx, controller.signal).finally(() => {
     deps.setPollingPromise(undefined);
     deps.setPollingController(undefined);
-    deps.updateStatus(ctx);
+    updateTelegramPollingStatusSafely(deps.updateStatus, ctx, {
+      recordRuntimeEvent: deps.recordRuntimeEvent,
+    });
   });
   deps.setPollingPromise(promise);
-  deps.updateStatus(ctx);
+  updateTelegramPollingStatusSafely(deps.updateStatus, ctx, {
+    recordRuntimeEvent: deps.recordRuntimeEvent,
+  });
 }
 
 export interface TelegramRuntimeEventRecorderPort {
@@ -281,10 +303,15 @@ export function createTelegramPollLoopRunner<
       persistConfig: deps.persistConfig,
       handleUpdate: deps.handleUpdate,
       onErrorStatus: (message) => {
-        deps.updateStatus(ctx, message);
+        updateTelegramPollingStatusSafely(deps.updateStatus, ctx, {
+          message,
+          recordRuntimeEvent: deps.recordRuntimeEvent,
+        });
       },
       onStatusReset: () => {
-        deps.updateStatus(ctx);
+        updateTelegramPollingStatusSafely(deps.updateStatus, ctx, {
+          recordRuntimeEvent: deps.recordRuntimeEvent,
+        });
       },
       sleep,
       maxUpdateFailures: deps.maxUpdateFailures,

package/package.json

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