@s0nderlabs/anima-plugin-telegram 0.19.17 → 0.19.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@s0nderlabs/anima-plugin-telegram",
-  "version": "0.19.17",
+  "version": "0.19.18",
   "type": "module",
   "description": "Telegram gateway plugin for anima — long-poll bot, debounced dispatch, reactions, allowlist",
   "license": "MIT",
@@ -28,7 +28,7 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@s0nderlabs/anima-core": "0.19.17",
+    "@s0nderlabs/anima-core": "0.19.18",
     "grammy": "^1.42.0",
     "zod": "^3.23.8"
   }

package/src/index.ts

@@ -27,7 +27,7 @@ export type {
   TelegramToolEvent,
 } from './types'
 export { ProgressTracker, PROGRESS_EDIT_INTERVAL } from './progress'
-export { TelegramListener, capForTelegram } from './listener'
+export { TelegramListener, TELEGRAM_ALLOWED_UPDATES, capForTelegram } from './listener'
 export { buildSessionKey, sanitizeAgentName } from './session-key'
 export { formatTelegramChannel, formatInboundPreview } from './format'
 export { RateLimiter } from './limits'

package/src/listener-allowed-updates.test.ts

@@ -0,0 +1,25 @@
+import { describe, expect, it } from 'bun:test'
+import { TELEGRAM_ALLOWED_UPDATES } from './listener'
+
+/**
+ * Regression test for v0.19.18 callback_query polling fix.
+ *
+ * v0.18.0 introduced inline-keyboard approvals but only subscribed to
+ * `'message'` updates in `bot.start({ allowed_updates })`. v0.19.10 fixed
+ * the handler-registration path but left the polling spec narrow, so every
+ * keyboard tap was silently filtered out by Telegram before grammY ever
+ * saw it. Operators saw the modal "do nothing" — the harness saw zero
+ * resolution events. This test pins both kinds in the polling spec so a
+ * future refactor cannot quietly drop the second one again.
+ */
+describe('TELEGRAM_ALLOWED_UPDATES', () => {
+  it('subscribes to both message and callback_query updates', () => {
+    expect(TELEGRAM_ALLOWED_UPDATES).toContain('message')
+    expect(TELEGRAM_ALLOWED_UPDATES).toContain('callback_query')
+  })
+
+  it('does not over-subscribe to update kinds we have no handler for', () => {
+    // Keep the wire payload minimal. Add new kinds only when a handler exists.
+    expect([...TELEGRAM_ALLOWED_UPDATES].sort()).toEqual(['callback_query', 'message'])
+  })
+})

package/src/listener.ts

@@ -38,6 +38,23 @@ import { startTypingLoop } from './typing'
 const RETRY_INTERVAL_MS = 30_000
 const MAX_LOCK_RETRY_ATTEMPTS = 12
 
+/**
+ * Update kinds we ask Telegram to deliver via long-poll.
+ *
+ * `'message'` covers inbound DMs we dispatch to the brain. `'callback_query'`
+ * covers inline-keyboard taps (the [Allow Once / Session / Always / Deny]
+ * buttons rendered for tool approvals). Without `'callback_query'` here,
+ * Telegram silently filters the click events out of `getUpdates`, the
+ * `bot.on('callback_query:data', ...)` handler never fires, and operator
+ * taps register on the device but never reach the harness — the modal
+ * appears stuck and the brain's tool call hangs until timeout.
+ *
+ * Latent bug from v0.18.0 (the introduction of inline-keyboard approvals);
+ * v0.19.10 fixed handler registration but not the polling spec, which is
+ * why no live drive caught it before v0.19.18.
+ */
+export const TELEGRAM_ALLOWED_UPDATES = ['message', 'callback_query'] as const
+
 export interface TelegramListenerOpts extends TelegramRuntimeContext {
   /** Optional override of the Telegram Bot API root. Used by the mock-bot test. */
   apiRoot?: string
@@ -182,7 +199,7 @@ export class TelegramListener {
       .start({
         onStart: info => console.log(`[telegram] listener active @${info.username}`),
         drop_pending_updates: true,
-        allowed_updates: ['message'],
+        allowed_updates: [...TELEGRAM_ALLOWED_UPDATES],
       })
       .catch(err => {
         const verdict = classifyStartFailure(err)