@llblab/pi-telegram 0.9.0 → 0.9.1

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.9.1: Model Detail Hotfix
+
+- `[Model Menu]` Detail-mode activation now preserves scoped `thinkingLevel` by resolving the selected scoped entry before falling back to the unscoped model list. Impact: scoped model shortcuts opened through the detail submenu keep their reasoning/thinking level.
+- `[Model Menu]` Activating an already active model from the detail submenu now still runs the refresh path that applies scoped thinking changes while returning to the model list. Impact: tapping Active can still correct the thinking level instead of becoming a no-op.
+- `[Proactive Push]` Removed the unused proactive reply-target store and always sends proactive local-result pushes without `reply_to_message_id`. Impact: the runtime no longer carries dead state for a target-capture behavior that does not exist yet.
+- `[Queue Reactions]` Added `🔥` as a priority reaction and `🗑` as a queue-removal reaction. Impact: the intuitive fire/removal gestures now work alongside the existing reaction controls.
+- `[Docs]` Updated the status-bar example to match the compact active/queued display.
+- `[Package]` Bumped package metadata to `0.9.1` and kept the lockfile in sync.
+
 ## 0.9.0: Hidden Settings And Proactive Push
 
 - `[Settings Menu]` Added hidden Telegram `/settings` with a proactive push checkbox detail submenu plus `/telegram-settings` in the terminal. Impact: operators can see green/black binary flag state, use green/black/yellow On/Off checkbox controls from Telegram, and toggle the same proactive push flag locally without adding a visible bot-command entry.

package/README.md

@@ -110,8 +110,8 @@ Run these inside π, not Telegram:
 
 - If you send more Telegram messages while π is busy, they enter the default prompt queue and are processed in order.
 - Very long text messages that Telegram appears to split automatically are coalesced through a short conservative debounce and forwarded to π as one prompt when the first chunk is near Telegram's text limit, currently using a 3600-character threshold. Commands, bot messages, media groups, and normal short follow-ups are not coalesced.
-- `👍`, `⚡️`, `❤️`, and `🕊` move a waiting prompt into the priority prompt queue, behind control actions but ahead of default prompts. Removing the last priority reaction sends it back to its normal queue position, and adding a priority reaction again gives it a fresh priority position.
-- `👎`, `👻`, `💔`, and `💩` remove a waiting turn from the queue. Telegram Bot API does not expose ordinary DM message-deletion events through the polling path used here, so queue removal is bound to removal reactions.
+- `👍`, `⚡️`, `❤️`, `🕊`, and `🔥` move a waiting prompt into the priority prompt queue, behind control actions but ahead of default prompts. Removing the last priority reaction sends it back to its normal queue position, and adding a priority reaction again gives it a fresh priority position.
+- `👎`, `👻`, `💔`, `💩`, and `🗑` remove a waiting turn from the queue. Telegram Bot API does not expose ordinary DM message-deletion events through the polling path used here, so queue removal is bound to removal reactions.
 - Reactions apply to any waiting Telegram turn, including text, voice, files, images, and media groups. For media groups, a reaction on any message in the group applies to the whole queued turn.
 - If you edit a Telegram message while it is still waiting in the queue, the queued turn is updated instead of creating a duplicate prompt. Edits after a turn has already started may not affect the active run.
 - Telegram replies to earlier text or caption messages are forwarded as `[reply]` context for normal prompts, while slash commands still parse from the new message text only.
@@ -237,7 +237,7 @@ Rich previews are sent through editable messages because Telegram drafts are tex
 The π status bar shows the current bridge state plus queued Telegram turns as compact previews. Busy labels distinguish states such as `active`, `dispatching`, `queued`, `tool running`, `model`, and `compacting`. Telegram prompt guidance asks agents to keep tables, dense list items, and compact text blocks within about 37 visible cells when possible so mobile replies stay readable.
 
 ```text
-telegram queued +3: [⚡ write a shell script…, summarize this image…, 📎 2 attachments]
+telegram active +3
 ```
 
 ## Notes

package/docs/architecture.md

@@ -23,24 +23,24 @@ Naming rule: because the repository already scopes this codebase to Telegram, ex
 
 Current runtime areas use these ownership boundaries:
 
-| Domain                                    | Owns                                                                                                                                                              |
-| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `index.ts`                                | Single composition root for live π/Telegram ports, session state, API-bound transport adapters, and status updates                                                |
-| `api`                                     | Bot API transport shapes/helpers, retries, file download, temp-dir lifecycle, inbound limits, chat actions, lazy bot-token clients, runtime error recording       |
-| `config` / `setup`                        | Persisted bot/session pairing state, authorization, first-user pairing, token prompting, env fallback, validation, config persistence                             |
-| `locks` / `polling`                       | Singleton `locks.json` ownership, takeover/restart semantics, long-poll controller state, update offset persistence, poll-loop runtime wiring                     |
-| `updates` / `routing`                     | Update classification/execution planning, paired authorization, reactions, edits, callbacks, and inbound route composition                                        |
-| `media` / `text-groups` / `turns` / `inbound-handlers` | Text/media extraction, media-group debounce, long-text split coalescing, inbound downloads, inbound text/media handler execution, turn building/editing, image reads, legacy `attachmentHandlers` compatibility |
-| `queue`                                   | Queue item contracts, lane admission/order, stores, mutations, dispatch readiness/runtime, prompt/control enqueueing, session and agent/tool lifecycle sequencing |
-| `runtime`                                 | Session-local coordination primitives: counters, lifecycle flags, setup guard, abort handler, typing-loop timers, prompt-dispatch flags, agent-end reset binding  |
+| Domain                                                                                                          | Owns                                                                                                                                                                                                                                                |
+| --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `index.ts`                                                                                                      | Single composition root for live π/Telegram ports, session state, API-bound transport adapters, and status updates                                                                                                                                  |
+| `api`                                                                                                           | Bot API transport shapes/helpers, retries, file download, temp-dir lifecycle, inbound limits, chat actions, lazy bot-token clients, runtime error recording                                                                                         |
+| `config` / `setup`                                                                                              | Persisted bot/session pairing state, authorization, first-user pairing, token prompting, env fallback, validation, config persistence                                                                                                               |
+| `locks` / `polling`                                                                                             | Singleton `locks.json` ownership, takeover/restart semantics, long-poll controller state, update offset persistence, poll-loop runtime wiring                                                                                                       |
+| `updates` / `routing`                                                                                           | Update classification/execution planning, paired authorization, reactions, edits, callbacks, and inbound route composition                                                                                                                          |
+| `media` / `text-groups` / `turns` / `inbound-handlers`                                                          | Text/media extraction, media-group debounce, long-text split coalescing, inbound downloads, inbound text/media handler execution, turn building/editing, image reads, legacy `attachmentHandlers` compatibility                                     |
+| `queue`                                                                                                         | Queue item contracts, lane admission/order, stores, mutations, dispatch readiness/runtime, prompt/control enqueueing, session and agent/tool lifecycle sequencing                                                                                   |
+| `runtime`                                                                                                       | Session-local coordination primitives: counters, lifecycle flags, setup guard, abort handler, typing-loop timers, prompt-dispatch flags, agent-end reset binding                                                                                    |
 | `model` / `menu-model` / `menu-thinking` / `menu-status` / `menu` / `menu-queue` / `menu-settings` / `commands` | Model identity/thinking levels, scoped model resolution, in-flight switching, model-menu UI, thinking-menu UI, status-menu UI, inline application callback composition, queue-menu UI, hidden settings UI, slash commands, bot command registration |
-| `keyboard`                                | Shared Telegram inline-keyboard reply-markup structure; feature domains own callback semantics and button construction                                           |
-| `preview` / `replies` / `rendering`       | Preview lifecycle/transports, final reply delivery and reply parameters, Telegram HTML Markdown rendering, chunking, stable-preview snapshots                     |
-| `outbound-handlers`                       | Outbound text transformation, assistant-authored outbound comments, generated reply artifacts, inline-keyboard callbacks, and post-`agent_end` outbound action delivery |
-| `outbound-attachments`                    | `telegram_attach` registration, outbound attachment queueing, stat/limit checks, photo/document delivery classification                                           |
-| `status`                                  | Status-bar/status-message rendering, queue-lane status views, redacted runtime event ring, grouped π diagnostics                                                  |
-| `lifecycle` / `prompts` / `prompt-templates` / `pi` | π hook registration, Telegram-specific before-agent prompt injection, π prompt-template discovery/expansion, centralized direct pi SDK imports and context adapters |
-| `command-templates`                       | Portable shell-free command-template standard helpers, composition expansion, placeholder substitution, and executable resolution                                 |
+| `keyboard`                                                                                                      | Shared Telegram inline-keyboard reply-markup structure; feature domains own callback semantics and button construction                                                                                                                              |
+| `preview` / `replies` / `rendering`                                                                             | Preview lifecycle/transports, final reply delivery and reply parameters, Telegram HTML Markdown rendering, chunking, stable-preview snapshots                                                                                                       |
+| `outbound-handlers`                                                                                             | Outbound text transformation, assistant-authored outbound comments, generated reply artifacts, inline-keyboard callbacks, and post-`agent_end` outbound action delivery                                                                             |
+| `outbound-attachments`                                                                                          | `telegram_attach` registration, outbound attachment queueing, stat/limit checks, photo/document delivery classification                                                                                                                             |
+| `status`                                                                                                        | Status-bar/status-message rendering, queue-lane status views, redacted runtime event ring, grouped π diagnostics                                                                                                                                    |
+| `lifecycle` / `prompts` / `prompt-templates` / `pi`                                                             | π hook registration, Telegram-specific before-agent prompt injection, π prompt-template discovery/expansion, centralized direct pi SDK imports and context adapters                                                                                 |
+| `command-templates`                                                                                             | Portable shell-free command-template standard helpers, composition expansion, placeholder substitution, and executable resolution                                                                                                                   |
 
 Boundary invariants:
 
@@ -95,13 +95,13 @@ Queued items now use two explicit dimensions:
 
 Admission contract:
 
-| Admission             | Examples                                                     | Queue shape                                                          | Dispatch rank |
-| --------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------- | ------------- |
-| Immediate execution   | `/compact`, `/queue`, `/stop`, `/help`, `/start` | Does not enter the Telegram queue; `/help` opens the same menu as `/start`; `/stop` also clears queued items | N/A           |
-| Queued prompt command | `/continue`, `/template_name args` | `/continue` enqueues a Telegram-owned `continue` prompt; prompt-template commands expand the matching π template before entering the normal prompt queue | priority for `/continue`, otherwise default |
-| Control queue         | Model-switch continuation turns and future deferred controls | `queueLane: control`; accepts control items and continuation prompts | 0             |
-| Priority prompt queue | A waiting prompt promoted by `👍`, `⚡️`, `❤️`, or `🕊`      | `kind: prompt`, `queueLane: priority`                                | 1             |
-| Default prompt queue  | Normal Telegram text/media turns                             | `kind: prompt`, `queueLane: default`                                 | 2             |
+| Admission             | Examples                                                     | Queue shape                                                                                                                                              | Dispatch rank                               |
+| --------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
+| Immediate execution   | `/compact`, `/queue`, `/stop`, `/help`, `/start`             | Does not enter the Telegram queue; `/help` opens the same menu as `/start`; `/stop` also clears queued items                                             | N/A                                         |
+| Queued prompt command | `/continue`, `/template_name args`                           | `/continue` enqueues a Telegram-owned `continue` prompt; prompt-template commands expand the matching π template before entering the normal prompt queue | priority for `/continue`, otherwise default |
+| Control queue         | Model-switch continuation turns and future deferred controls | `queueLane: control`; accepts control items and continuation prompts                                                                                     | 0                                           |
+| Priority prompt queue | A waiting prompt promoted by `👍`, `⚡️`, `❤️`, `🕊`, or `🔥` | `kind: prompt`, `queueLane: priority`                                                                                                                    | 1                                           |
+| Default prompt queue  | Normal Telegram text/media turns                             | `kind: prompt`, `queueLane: default`                                                                                                                     | 2                                           |
 
 The command action itself carries its execution mode, and the queue domain exposes lane contracts for admission mode, dispatch rank, and allowed item kinds. Queue append and planning paths validate lane admission so a malformed control/default or other invalid lane pairing fails predictably instead of silently changing priority. This lets synthetic control actions and Telegram prompts share one stable ordering model while still rendering distinctly in status output. In the π status bar, busy labels distinguish `active`, `dispatching`, `queued`, `tool running`, `model`, and `compacting`; priority prompts and priority control items are marked with `⚡`. If a queue mutation removes the last waiting item while Telegram-owned work still has running tools, the status remains yellow `active` instead of degrading to green `connected`.
 
@@ -181,7 +181,7 @@ Current operator controls include:
 - `/stop` for aborting the active Telegram-owned run and clearing waiting Telegram queue items
 - `/telegram-status` for π-side diagnostics as grouped line-by-line sections separated by blank lines: connection, polling, execution, queue, and the recent redacted runtime/API event ring. These sections include polling state, last update id, active turn source ids, pending dispatch, compaction state, active tool count, pending model-switch state, total queue depth, and queue-lane counts. The event ring records transport/API, polling/update, prompt-dispatch, control-action, typing, compaction, setup, session-lifecycle, and attachment queue/delivery failures; benign unchanged edit responses and unsupported empty draft-clear attempts are filtered out so expected preview transport noise does not obscure real failures
 - `/telegram-settings` for π-side bridge settings; it currently exposes proactive push as a local toggle backed by the same `telegram.json` flag as the hidden Telegram `/settings` menu
-- Queue reactions apply to waiting text, voice, file, image, and media-group turns by matching the turn's source Telegram message ids: `👍`, `⚡️`, `❤️`, and `🕊` promote waiting prompts, while `👎`, `👻`, `💔`, and `💩` remove waiting turns because ordinary Telegram DM message deletions are not exposed through the Bot API polling path this bridge uses
+- Queue reactions apply to waiting text, voice, file, image, and media-group turns by matching the turn's source Telegram message ids: `👍`, `⚡️`, `❤️`, `🕊`, and `🔥` promote waiting prompts, while `👎`, `👻`, `💔`, `💩`, and `🗑` remove waiting turns because ordinary Telegram DM message deletions are not exposed through the Bot API polling path this bridge uses
 
 ## In-Flight Model Switching
 

package/index.ts

@@ -53,8 +53,6 @@ export default function (pi: Pi.ExtensionAPI) {
     Config.createTelegramProactivePushChecker(configStore);
   const setProactivePushEnabled =
     Config.createTelegramProactivePushSetter(configStore);
-  const proactivePromptTargetStore =
-    Config.createTelegramProactivePromptTargetStore();
   const lockRuntime = Locks.createTelegramLockRuntime<Pi.ExtensionContext>();
   const lockOwnershipGuard =
     Locks.createTelegramLockOwnershipGuard(lockRuntime);
@@ -496,7 +494,6 @@ export default function (pi: Pi.ExtensionAPI) {
     sendOutboundReplyArtifacts: outboundReplyArtifactSender,
     isCurrentOwner: lockOwnershipGuard.ownsContext,
     getDefaultChatId: proactivePushChatIdGetter,
-    consumeProactiveReplyToMessageId: proactivePromptTargetStore.consumeForChat,
     isProactivePushEnabled,
     recordRuntimeEvent,
     getActiveToolExecutions: lifecycle.getActiveToolExecutions,

package/lib/config.ts

@@ -148,31 +148,6 @@ export function createTelegramProactivePushChatIdGetter(deps: {
   return () => deps.getActiveTurnChatId() ?? deps.getAllowedUserId();
 }
 
-export interface TelegramProactivePromptTarget {
-  chatId: number;
-  messageId: number;
-}
-
-export interface TelegramProactivePromptTargetStore {
-  set: (target: TelegramProactivePromptTarget) => void;
-  consumeForChat: (chatId: number) => number | undefined;
-}
-
-export function createTelegramProactivePromptTargetStore(): TelegramProactivePromptTargetStore {
-  let target: TelegramProactivePromptTarget | undefined;
-  return {
-    set: (nextTarget) => {
-      target = nextTarget;
-    },
-    consumeForChat: (chatId) => {
-      if (!target || target.chatId !== chatId) return undefined;
-      const messageId = target.messageId;
-      target = undefined;
-      return messageId;
-    },
-  };
-}
-
 export type TelegramAuthorizationState =
   | { kind: "pair"; userId: number }
   | { kind: "allow" }

package/lib/menu-model.ts

@@ -620,6 +620,19 @@ export function applyTelegramModelDetailSelection(
 export function getTelegramSelectedDetailModel<
   TModel extends MenuModel = MenuModel,
 >(state: TelegramModelMenuState<TModel>): TelegramMenuSelectionResult<TModel> {
+  const indexedSelection = getTelegramModelSelection(
+    state,
+    state.selectedModelIndex?.toString(),
+  );
+  if (indexedSelection.kind === "selected") {
+    if (!state.selectedModelKey) return indexedSelection;
+    const indexedKey = getCanonicalModelId(
+      indexedSelection.selection.model,
+    ).toLowerCase();
+    if (indexedKey === state.selectedModelKey.toLowerCase()) {
+      return indexedSelection;
+    }
+  }
   if (state.selectedModelKey) {
     const lowerKey = state.selectedModelKey.toLowerCase();
     const selection = state.allModels.find(
@@ -627,7 +640,7 @@ export function getTelegramSelectedDetailModel<
     );
     if (selection) return { kind: "selected", selection };
   }
-  return getTelegramModelSelection(state, state.selectedModelIndex?.toString());
+  return indexedSelection;
 }
 
 export function isTelegramModelScoped(
@@ -817,7 +830,6 @@ export function buildTelegramModelCallbackPlan<
   if (modelsMatch(selection.model, params.activeModel)) {
     if (action.action === "pick-selected") {
       focusTelegramModelListPage(params.state, selection.model);
-      return { kind: "update-menu", text: `Model: ${selection.model.id}` };
     }
     return {
       kind: "refresh-status",

package/lib/queue.ts

@@ -794,7 +794,6 @@ export interface TelegramAgentEndRuntimeDeps<
     options?: { replyToPrompt?: boolean },
   ) => Promise<void>;
   getDefaultChatId?: () => number | undefined;
-  consumeProactiveReplyToMessageId?: (chatId: number) => number | undefined;
   isProactivePushEnabled?: () => boolean;
   recordRuntimeEvent?: (
     category: string,
@@ -839,7 +838,6 @@ export interface TelegramAgentEndHookRuntimeDeps<
   >["planOutboundReply"];
   sendOutboundReplyArtifacts?: TelegramAgentEndRuntimeDeps<TTurn>["sendOutboundReplyArtifacts"];
   getDefaultChatId?: TelegramAgentEndRuntimeDeps<TTurn>["getDefaultChatId"];
-  consumeProactiveReplyToMessageId?: TelegramAgentEndRuntimeDeps<TTurn>["consumeProactiveReplyToMessageId"];
   isProactivePushEnabled?: TelegramAgentEndRuntimeDeps<TTurn>["isProactivePushEnabled"];
   recordRuntimeEvent?: TelegramAgentEndRuntimeDeps<TTurn>["recordRuntimeEvent"];
 }
@@ -957,7 +955,6 @@ export function createTelegramAgentEndHook<
       planOutboundReply: deps.planOutboundReply,
       sendOutboundReplyArtifacts: deps.sendOutboundReplyArtifacts,
       getDefaultChatId: deps.getDefaultChatId,
-      consumeProactiveReplyToMessageId: deps.consumeProactiveReplyToMessageId,
       isProactivePushEnabled: deps.isProactivePushEnabled,
       recordRuntimeEvent: deps.recordRuntimeEvent,
     });
@@ -998,14 +995,8 @@ export async function handleTelegramAgentEndRuntime<
     ) {
       const defaultChatId = deps.getDefaultChatId?.();
       if (defaultChatId !== undefined) {
-        const replyToMessageId =
-          deps.consumeProactiveReplyToMessageId?.(defaultChatId);
         try {
-          await deps.sendMarkdownReply(
-            defaultChatId,
-            replyToMessageId,
-            finalText,
-          );
+          await deps.sendMarkdownReply(defaultChatId, undefined, finalText);
         } catch (error) {
           deps.recordRuntimeEvent?.("proactive-push", error, {
             chatId: defaultChatId,

package/lib/updates.ts

@@ -31,12 +31,14 @@ export const TELEGRAM_PRIORITY_REACTIONS = [
   { id: 11, name: "lightning", emoji: "⚡" },
   { id: 12, name: "heart", emoji: "❤" },
   { id: 13, name: "dove", emoji: "🕊" },
+  { id: 14, name: "fire", emoji: "🔥" },
 ] as const;
 export const TELEGRAM_REMOVAL_REACTIONS = [
   { id: 20, name: "dislike", emoji: "👎" },
   { id: 21, name: "ghost", emoji: "👻" },
   { id: 22, name: "broken-heart", emoji: "💔" },
   { id: 23, name: "poop", emoji: "💩" },
+  { id: 24, name: "wastebasket", emoji: "🗑" },
 ] as const;
 export const TELEGRAM_PRIORITY_REACTION_EMOJIS =
   TELEGRAM_PRIORITY_REACTIONS.map((reaction) => reaction.emoji);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-telegram",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "private": false,
   "description": "Better Telegram DM bridge extension for π",
   "type": "module",