@chbo297/infoflow 2026.5.9-beta.1 → 2026.5.9-beta.2

package/README.md

@@ -39,35 +39,49 @@ BAIDU_NPM_REGISTRY=http://registry.npm.baidu-int.com bash scripts/deploy.sh
 
 ### 首次安装（推荐命令）
 
-首次在机器上安装时，推荐使用以下两种方式。
+下面的安装命令块由 `npm run sync-readme-install-version` 自动维护，版本号始终与 npm 上当前的 `latest` / `beta` dist-tag 保持一致，请直接复制使用。
 
-方式 A：通过独立 tools 包安装并部署（推荐，支持 `update` 子命令）
+#### 方式 A：通过独立 tools 包安装并部署（推荐，支持 `update` 子命令）
 
-<!-- sync:infoflow-plugin-version -->
+正式版（`latest` dist-tag）：
+
+<!-- sync:infoflow-plugin-version:latest -->
 ```bash
-# 正式版（latest）
-npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.9-beta.1 --registry https://registry.npmjs.org
+npm cache clean --force
+npx -y --prefer-online @chbo297/infoflow-openclaw-tools update \
+  --version 2026.5.8 --registry https://registry.npmjs.org
 ```
-<!-- /sync:infoflow-plugin-version -->
+<!-- /sync:infoflow-plugin-version:latest -->
+
+Beta 版（`beta` dist-tag，按需）：
 
+<!-- sync:infoflow-plugin-version:beta -->
 ```bash
-# Beta 版（示例，版本号请按实际预发包替换）
-npx -y @chbo297/infoflow-openclaw-tools@beta update --version 2026.5.8-beta.1 --registry https://registry.npmjs.org
+npm cache clean --force
+npx -y --prefer-online @chbo297/infoflow-openclaw-tools@beta update \
+  --version 2026.5.9-beta.1 --registry https://registry.npmjs.org
 ```
+<!-- /sync:infoflow-plugin-version:beta -->
 
-方式 B：通过 OpenClaw 插件命令安装
+> 加上 `npm cache clean --force` 和 `--prefer-online`，可避免本机 npm metadata 缓存尚未刷新而看不到刚发布版本（典型表现为 `ETARGET: No matching version found`）。
 
-<!-- sync:infoflow-plugin-version -->
+#### 方式 B：通过 OpenClaw 插件命令安装
+
+正式版：
+
+<!-- sync:infoflow-plugin-version:latest -->
 ```bash
-# 正式版
-openclaw plugins install @chbo297/infoflow@2026.5.9-beta.1
+openclaw plugins install @chbo297/infoflow@2026.5.8
 ```
-<!-- /sync:infoflow-plugin-version -->
+<!-- /sync:infoflow-plugin-version:latest -->
+
+Beta 版：
 
+<!-- sync:infoflow-plugin-version:beta -->
 ```bash
-# Beta 版（示例，版本号请按实际预发包替换）
-openclaw plugins install @chbo297/infoflow@2026.5.8-beta.1
+openclaw plugins install @chbo297/infoflow@2026.5.9-beta.1
 ```
+<!-- /sync:infoflow-plugin-version:beta -->
 
 安装后建议检查插件状态：
 
@@ -76,17 +90,32 @@ openclaw plugins list
 openclaw plugins inspect infoflow
 ```
 
-### 通过 npx 一键更新安装
+#### 如遇 `ETARGET: No matching version found`
 
-发布到 npm 后，可直接通过独立 tools 包执行安装/升级：
+刚发布的版本可能在本机 npm metadata 缓存里看不到，按下面顺序排查：
 
-<!-- sync:infoflow-plugin-version -->
 ```bash
-npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.9-beta.1 --registry https://registry.npmjs.org
+# 1) 强制清缓存 + 在线拉取最新元数据
+npm cache clean --force
+npx -y --prefer-online @chbo297/infoflow-openclaw-tools@beta update \
+  --version <要装的版本> --registry https://registry.npmjs.org
+
+# 2) 直接查 registry，确认版本确实可见
+npm view @chbo297/infoflow versions --registry https://registry.npmjs.org
+
+# 3) 确认默认 registry 未被改到镜像源（有些内网会重写到 cnpm/baidu 镜像，那里同步可能滞后）
+npm config get registry            # 期望: https://registry.npmjs.org/
+# 临时强制覆盖（不改全局配置）：
+npm_config_registry=https://registry.npmjs.org \
+  npx -y --prefer-online @chbo297/infoflow-openclaw-tools@beta update \
+  --version <要装的版本> --registry https://registry.npmjs.org
+
+# 4) 直接 curl 验证那台机器能否拿到 manifest
+curl -sI https://registry.npmjs.org/@chbo297/infoflow | head -5
+curl -s https://registry.npmjs.org/@chbo297/infoflow/<要装的版本> | head -50
 ```
-<!-- /sync:infoflow-plugin-version -->
 
-常用参数：
+### tools 包的常用参数
 
 - `--version <version>`: 指定安装版本（默认 `latest`）
 - `--registry <url>`: 插件包下载源（默认 `https://registry.npmjs.org`）
@@ -107,34 +136,102 @@ npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.9-beta.1 --regis
 
 ### 版本升级、打 tag、推送与 npm 发布流程
 
-每次发布新版本时，先将 `package.json` 的 `version` 设为待发版本号，再按下述顺序执行。上文「首次安装 / npx 更新」与下文发版流程中，各 bash 代码块外侧有一对用于自动替换的 HTML 注释标记；发版前请执行 **`npm run sync-readme-install-version`**，脚本会按当前 `package.json` 的 `version` 更新这些块内的版本号，以免 README 与 npm 不一致。
+正式版与 Beta 预发各自有完整流程，区别只在 **`npm version` 用的版本号** 和 **`npm publish` 是否带 `--tag beta`** 两处。请按需选择对应小节，从头到尾执行。
+
+执行 `npm run sync-readme-install-version` 时脚本会：
+
+- 把"发版流程"代码块内 `--version` / `npm version` / `git tag` / `git commit -m "<version>"` 等示例同步到当前 `package.json.version`（"current" stream）；
+- 同时把上文"首次安装"段落里 `:latest` / `:beta` 两个 marker 区按 npm 上的 dist-tag 刷新——发 stable 时 `:latest` 区会写成新版本号；发 prerelease 时 `:beta` 区会写成新版本号；另一条 stream 通过 npm registry 接口拉取真实 dist-tag。
+
+#### A. 正式版（stable）发布流程
+
+发布一个不带预发后缀的版本（例如 `2026.5.10`），会同时占用 npm 的 `latest` dist-tag，是 `npx` 默认拉取的版本。
+
+将下方所有 `<X.Y.Z>` 替换为目标正式版本号（不带 `-beta.N`）：
 
-<!-- sync:infoflow-plugin-version -->
 ```bash
 # 1) 修改版本号（会同步 package-lock.json）
-npm version 2026.5.9-beta.1 --no-git-tag-version
+npm version <X.Y.Z> --no-git-tag-version
 
-# 2) 同步 README 中标记块内的推荐安装命令与下文中的 tag / commit 示例版本号
+# 2) 同步 README：current 区写入 <X.Y.Z>；:latest 区也写入 <X.Y.Z>（因为本次发的就是新 latest）；
+#                 :beta 区从 npm 拉取当前 beta dist-tag 保持不变
 npm run sync-readme-install-version
 
-# 3) 发布前校验
+# 3) 编辑 CHANGELOG.md 顶部，添加本版本章节
+
+# 4) 发布前校验
 npm run typecheck
 npm run test
 npm run build
 
-# 4) 提交版本变更（含 README、CHANGELOG 等）
+# 5) 提交版本变更
 git add package.json package-lock.json README.md CHANGELOG.md scripts src
-git commit -m "2026.5.9-beta.1"
+git commit -m "<X.Y.Z>"
 
-# 5) 打 tag 并推送代码与 tag
-git tag 2026.5.9-beta.1
+# 6) 打 tag 并推送代码与 tag
+git tag <X.Y.Z>
 git push origin main
-git push origin 2026.5.9-beta.1
+git push origin <X.Y.Z>
+
+# 7) 发布到 npm（占用 latest dist-tag）
+npm publish --registry https://registry.npmjs.org
+
+# 8) 发布成功后再跑一次 sync，把 :latest 区刷新成 npm registry 真实状态（通常已经一致，
+#    但若另一条 stream 在期间也有新发布，这一步会顺带更新），并补一个 docs 提交
+npm run sync-readme-install-version
+git add README.md && git diff --cached --quiet || git commit -m "docs: refresh README install commands"
+git push origin main
+```
+
+#### B. Beta 预发布流程
 
-# 6) 发布 npm（可按需指定 registry）
-npm publish
-# 或
-# npm publish --registry https://registry.npmjs.org
+发布一个带预发后缀的版本（例如 `2026.5.10-beta.1`），通过 `--tag beta` 占用 `beta` dist-tag，**不会**改写 `latest`，默认 `npx` 装到的仍是正式版。
+
+将下方所有 `<X.Y.Z-beta.N>` 替换为目标预发版本号：
+
+```bash
+# 1) 修改版本号（会同步 package-lock.json）
+npm version <X.Y.Z-beta.N> --no-git-tag-version
+
+# 2) 同步 README：current 区写入 <X.Y.Z-beta.N>；:beta 区也写入 <X.Y.Z-beta.N>（因为本次发的就是新 beta）；
+#                 :latest 区从 npm 拉取当前 latest dist-tag 保持不变
+npm run sync-readme-install-version
+
+# 3) 编辑 CHANGELOG.md 顶部，添加本版本章节
+
+# 4) 发布前校验
+npm run typecheck
+npm run test
+npm run build
+
+# 5) 提交版本变更
+git add package.json package-lock.json README.md CHANGELOG.md scripts src
+git commit -m "<X.Y.Z-beta.N>"
+
+# 6) 打 tag 并推送代码与 tag
+git tag <X.Y.Z-beta.N>
+git push origin main
+git push origin <X.Y.Z-beta.N>
+
+# 7) 发布到 npm（占用 beta dist-tag；不影响 latest）
+npm publish --tag beta --registry https://registry.npmjs.org
+
+# 8) 发布成功后再跑一次 sync 并补一个 docs 提交（同 A.8）
+npm run sync-readme-install-version
+git add README.md && git diff --cached --quiet || git commit -m "docs: refresh README install commands"
+git push origin main
+```
+
+#### 当前 `package.json` 的版本号示例
+
+以下示例由 `sync` 脚本自动维护，反映**仓库当前 `package.json.version`**（可作为复制 A / B 流程时的版本号参考）：
+
+<!-- sync:infoflow-plugin-version -->
+```bash
+npm version 2026.5.9-beta.1 --no-git-tag-version
+git commit -m "2026.5.9-beta.1"
+git tag 2026.5.9-beta.1
+git push origin 2026.5.9-beta.1
 ```
 <!-- /sync:infoflow-plugin-version -->
 

package/dist/src/actions.js

@@ -6,6 +6,7 @@
 import { jsonResult, readStringParam } from "openclaw/plugin-sdk/core";
 import { extractToolSend } from "openclaw/plugin-sdk/tool-send";
 import { resolveInfoflowAccount } from "./accounts.js";
+import { looksLikeRecallLatest } from "./recall-intent.js";
 import { lookupInboundContext } from "./inbound-context.js";
 import { logVerbose } from "./logging.js";
 import { prepareInfoflowImageBase64, sendInfoflowImageMessage } from "./media.js";
@@ -34,7 +35,44 @@ function resolveInboundReplyToMessageId(params) {
         return undefined;
     if (ctx.target !== params.target)
         return undefined;
-    return ctx.replyToMessageId;
+}
+/**
+ * Aggressive guard: when LLM passes messageId === inbound currentMessageId (a known
+ * confusion pattern), auto-correct based on context instead of failing.
+ *
+ * Priorities:
+ * 1) Use replyToMessageId — user quote-replied to a bot message (highest confidence).
+ * 2) Drop to count=1 mode — when no replyTo AND text indicates "recall latest one".
+ * 3) Defer to existing fallback chain — ambiguous intent (e.g., "recall the one about X").
+ *
+ * Returns the corrected messageId (or undefined to signal count=1 mode).
+ */
+function applyAggressiveGuardForInboundMessageId(params) {
+    const inboundMsgId = params.currentMessageId != null ? String(params.currentMessageId) : undefined;
+    // Guard only triggers when LLM passes the inbound message id as delete target
+    if (!inboundMsgId || params.messageId !== inboundMsgId) {
+        return params.messageId;
+    }
+    const ctxRec = lookupInboundContext(inboundMsgId);
+    const scopeOk = ctxRec && ctxRec.accountId === params.accountId && ctxRec.target === params.target;
+    if (!scopeOk) {
+        // No inbound context to guide correction — defer to existing fallback chain
+        return params.messageId;
+    }
+    // Priority 1: replyToMessageId (user quote-replied to a bot message)
+    const replyToId = ctxRec.replyToMessageId;
+    if (replyToId && findSentMessage(params.accountId, replyToId)) {
+        logVerbose(`[infoflow:delete] aggressive: messageId==inboundMsgId(${params.messageId}); using replyTo=${replyToId}`);
+        return replyToId;
+    }
+    // Priority 2: text indicates "recall latest one" — safe to auto-correct to count=1
+    if (looksLikeRecallLatest(ctxRec.inboundBody ?? "")) {
+        logVerbose(`[infoflow:delete] aggressive: messageId==inboundMsgId(${params.messageId}); recall-latest intent → drop to count=1`);
+        return undefined; // undefined → count=1 mode
+    }
+    // Priority 3: ambiguous intent — defer to existing fallback chain
+    logVerbose(`[infoflow:delete] aggressive: messageId==inboundMsgId(${params.messageId}); ambiguous intent → defer to candidate-error path`);
+    return params.messageId;
 }
 /** Format up to N recent sent messages for an error-path hint to the LLM. */
 function formatRecentCandidatesForError(records, limit = 5) {
@@ -76,7 +114,7 @@ export const infoflowMessageActions = {
             if (!account.config.appKey || !account.config.appSecret) {
                 throw new Error("Infoflow appKey/appSecret not configured.");
             }
-            const messageId = readStringParam(params, "messageId");
+            let messageId = readStringParam(params, "messageId");
             // Default to count=1 (recall latest message) when neither messageId nor count is provided
             const countStr = readStringParam(params, "count") ?? (messageId ? undefined : "1");
             const groupMatch = target.match(/^group:(\d+)/i);
@@ -85,6 +123,16 @@ export const infoflowMessageActions = {
                 // 群消息撤回
                 // -----------------------------------------------------------------
                 const groupId = Number(groupMatch[1]);
+                const targetForStore = `group:${groupId}`;
+                // Apply aggressive guard when messageId equals inbound currentMessageId (LLM confusion pattern)
+                if (messageId) {
+                    messageId = applyAggressiveGuardForInboundMessageId({
+                        messageId,
+                        currentMessageId: toolContext?.currentMessageId,
+                        accountId: account.accountId,
+                        target: targetForStore,
+                    });
+                }
                 // Mode A: single message recall by messageId
                 if (messageId) {
                     // Resolve msgseqid (group recall requires it). If the LLM-passed messageId
@@ -97,7 +145,7 @@ export const infoflowMessageActions = {
                     if (!stored && !msgseqid) {
                         const fallbackId = resolveInboundReplyToMessageId({
                             accountId: account.accountId,
-                            target: `group:${groupId}`,
+                            target: targetForStore,
                             currentMessageId: toolContext?.currentMessageId,
                         });
                         if (fallbackId && fallbackId !== effectiveMessageId) {
@@ -151,7 +199,7 @@ export const infoflowMessageActions = {
                         throw new Error("count must be a positive integer.");
                     }
                     const records = querySentMessages(account.accountId, {
-                        target: `group:${groupId}`,
+                        target: targetForStore,
                         count,
                     });
                     // Filter to records that have msgseqid (required for group recall)
@@ -221,6 +269,15 @@ export const infoflowMessageActions = {
                     throw new Error("Infoflow private message recall requires appAgentId configuration. " +
                         "Set channels.infoflow.appAgentId to your application ID (如流企业后台的应用ID).");
                 }
+                // Apply aggressive guard when messageId equals inbound currentMessageId (LLM confusion pattern)
+                if (messageId) {
+                    messageId = applyAggressiveGuardForInboundMessageId({
+                        messageId,
+                        currentMessageId: toolContext?.currentMessageId,
+                        accountId: account.accountId,
+                        target,
+                    });
+                }
                 // Mode A: single message recall by messageId (msgkey)
                 if (messageId) {
                     // Attempt the inbound-context fallback when the LLM-passed messageId is

package/dist/src/bot.js

@@ -4,6 +4,7 @@ import { resolveInfoflowAccount } from "./accounts.js";
 import { registerInboundContext } from "./inbound-context.js";
 import { getInfoflowBotLog, formatInfoflowError, logVerbose } from "./logging.js";
 import { createInfoflowReplyDispatcher } from "./reply-dispatcher.js";
+import { looksLikeRecallIntent, looksLikeRecallLatest } from "./recall-intent.js";
 import { getInfoflowRuntime } from "./runtime.js";
 import { findSentMessage, querySentMessages } from "./sent-message-store.js";
 /**
@@ -226,13 +227,7 @@ function resolveReplyTargets(bodyItems, accountId) {
 // in the target group" bug. sent-messages.db tracks all bot-sent messages
 // keyed by target, so a single push surfaces messages sent from any session.
 // ---------------------------------------------------------------------------
-/** Detect inbound text that semantically asks the bot to recall/delete messages. */
-const RECALL_INTENT_REGEX = /(撤回|收回|删[掉了除]|取消|清除|recall|unsend|undo\s*send|delete\s+(?:that|those|the\s+(?:last|previous(?:\s+\d+)?)))/i;
-function looksLikeRecallIntent(text) {
-    if (!text)
-        return false;
-    return RECALL_INTENT_REGEX.test(text);
-}
+// Recall-intent detection lives in ./recall-intent.js — shared with actions.ts.
 const RECENT_BOT_AMBIENT_WINDOW_MS = 24 * 60 * 60 * 1000;
 const RECENT_BOT_AMBIENT_COUNT = 5;
 const RECENT_BOT_DETAIL_COUNT = 10;
@@ -886,10 +881,11 @@ export async function handleInfoflowMessage(params) {
         }
     }
     // Register inbound context so the delete action handler can fall back to the
-    // bot-message id the inbound is quote-replying to (when present) — only used
-    // when the LLM otherwise passes an unknown id. We intentionally only pick a
-    // bot-sent reply target: falling back to a non-bot reply id would never help
-    // (it can't be in sent-messages.db) and only adds noise.
+    // bot-message id the inbound is quote-replying to (when present), or detect
+    // the "messageId===inboundMessageId" LLM confusion pattern with the body
+    // text to decide whether it's safe to auto-correct to count=1. We only pick
+    // a bot-sent reply target: falling back to a non-bot reply id would never
+    // help (it can't be in sent-messages.db) and only adds noise.
     if (event.messageId) {
         registerInboundContext({
             accountId,
@@ -897,6 +893,7 @@ export async function handleInfoflowMessage(params) {
             inboundMessageId: event.messageId,
             replyToMessageId: event.replyTargets?.find((t) => t.isBotMessage)?.messageid,
             replyTargets: event.replyTargets,
+            inboundBody: bodyForAgent || mes || event.replyContext?.join(" "),
             registeredAt: Date.now(),
         });
     }
@@ -1163,6 +1160,8 @@ export function _checkReplyToBot(bodyItems, accountId) {
 export const _buildGroupOutputHygienePrompt = buildGroupOutputHygienePrompt;
 /** @internal — Recall intent regex. Only exported for tests. */
 export const _looksLikeRecallIntent = looksLikeRecallIntent;
+/** @internal — Stricter recall-latest detector. Only exported for tests. */
+export const _looksLikeRecallLatest = looksLikeRecallLatest;
 /** @internal — Sent-messages section builder. Only exported for tests. */
 export const _buildBotRecentMessagesSection = buildBotRecentMessagesSection;
 /** @internal — Quoted-reply targets section builder. Only exported for tests. */

package/dist/src/recall-intent.js

@@ -0,0 +1,26 @@
+/**
+ * Lightweight recall-intent detection used by both the prompt-injection path
+ * (bot.ts) and the delete action's aggressive guard (actions.ts).
+ *
+ * Two helpers:
+ *  - looksLikeRecallIntent: matches any "撤回/删除/recall/unsend/..." verb.
+ *  - looksLikeRecallLatest: requires both a recall verb AND an explicit
+ *    "the latest one" qualifier (上一条 / 最后一条 / 刚才那条 / 最近一条 /
+ *    last / previous / most recent / ...). Used to decide whether it's safe
+ *    to auto-correct `messageId=inbound_user_msg_id` to count=1 (recall most
+ *    recent). Standalone "撤回那条" without a temporal qualifier is rejected:
+ *    it could refer to a specific quoted message and we'd rather surface
+ *    candidates to the LLM than risk recalling the wrong one.
+ */
+const RECALL_INTENT_REGEX = /(撤回|收回|删[掉了除]|取消|清除|recall|unsend|undo\s*send|delete\s+(?:that|those|the\s+(?:last|previous(?:\s+\d+)?)))/i;
+const RECALL_LATEST_HINT_REGEX = /(上一?条|最后一?条|刚才那?条|最近一?条|last(?:\s+(?:one|message|two|few|reply))?|previous|most\s*recent)/iu;
+export function looksLikeRecallIntent(text) {
+    if (!text)
+        return false;
+    return RECALL_INTENT_REGEX.test(text);
+}
+export function looksLikeRecallLatest(text) {
+    if (!text)
+        return false;
+    return RECALL_INTENT_REGEX.test(text) && RECALL_LATEST_HINT_REGEX.test(text);
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chbo297/infoflow",
-  "version": "2026.5.9-beta.1",
+  "version": "2026.5.9-beta.2",
   "description": "OpenClaw Infoflow (如流) channel plugin for Baidu enterprise messaging",
   "type": "module",
   "main": "dist/index.js",