@wrongstack/telegram 1.0.3 → 1.0.5

package/dist/index.js

@@ -799,7 +799,7 @@ function truncateForTelegram(text, maxLen = 4e3) {
   const effectiveMaxLen = Math.min(maxLen, MAX_TELEGRAM_MESSAGE_LENGTH);
   if (text.length <= effectiveMaxLen) return text;
   const cutoff = effectiveMaxLen - 30;
-  if (cutoff <= 0) return `${text.slice(0, effectiveMaxLen - 1)}\u2026`;
+  if (cutoff <= 0) return `${text.slice(0, Math.max(0, effectiveMaxLen - 1))}\u2026`;
   const paraSearchEnd = effectiveMaxLen - 3;
   const paraIdx = text.lastIndexOf("\n\n", paraSearchEnd);
   if (paraIdx > cutoff) {
@@ -1628,7 +1628,7 @@ function makeTelegramApproveTool(opts) {
       },
       required: ["prompt"]
     },
-    permission: "auto",
+    permission: "confirm",
     mutating: true,
     riskTier: "standard",
     capabilities: [TELEGRAM_APPROVAL_CAPABILITY],

package/dist/tools/telegram-approve.d.ts

@@ -27,15 +27,14 @@ interface TelegramApproveOutput {
  * auto-denies). Useful when the agent wants explicit approval before
  * continuing and the user is on their phone rather than the TUI.
  *
- * The agent calls this tool directly. It does not replace the host-level
- * `permission: 'confirm'` flow — for that, see the future B4 work.
+ * The Telegram button is the remote authorization for the proposed action;
+ * it does not authorize sending the outbound approval request itself.
  *
- * Permission: `auto` (NOT `confirm`). This is intentional — the tool's
- * purpose IS to obtain user approval; gating it behind another host-level
- * confirm dialog would be circular and would block the agent in
- * headless mode. The user-side approval (Telegram button press) is
- * the only confirm gate. The 600 s tool `timeoutMs` ceiling is the
- * safety net for the case where the user never responds.
+ * Permission: `confirm`. Sending a persistent approval request to a remote
+ * user is a high-impact external side effect, so the host must confirm it
+ * before dispatch. After that confirmation, the Telegram button remains the
+ * only remote authorization for the proposed action. The 600 s tool
+ * `timeoutMs` ceiling auto-denies when the user never responds.
  */
 export declare function makeTelegramApproveTool(opts: {
     bot: TelegramBot;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrongstack/telegram",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "license": "MIT",
   "description": "WrongStack plugin — Telegram bridge: send messages, receive prompts, get notified.",
   "repository": {
@@ -26,11 +26,11 @@
     "!dist/**/*.map"
   ],
   "peerDependencies": {
-    "@wrongstack/core": "1.0.3"
+    "@wrongstack/core": "1.0.5"
   },
   "devDependencies": {
     "@types/node": "^26.2.0",
-    "@wrongstack/core": "1.0.3",
+    "@wrongstack/core": "1.0.5",
     "typescript": "^7.0.2"
   },
   "publishConfig": {