@chbo297/infoflow 2026.5.7-beta.3 → 2026.5.8

package/README.md

@@ -43,22 +43,30 @@ BAIDU_NPM_REGISTRY=http://registry.npm.baidu-int.com bash scripts/deploy.sh
 
 方式 A：通过独立 tools 包安装并部署（推荐，支持 `update` 子命令）
 
+<!-- sync:infoflow-plugin-version -->
 ```bash
 # 正式版（latest）
-npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.6 --registry https://registry.npmjs.org
+npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.8 --registry https://registry.npmjs.org
+```
+<!-- /sync:infoflow-plugin-version -->
 
-# Beta 版（示例）
-npx -y @chbo297/infoflow-openclaw-tools@beta update --version 2026.5.7-beta.2 --registry https://registry.npmjs.org
+```bash
+# Beta 版（示例，版本号请按实际预发包替换）
+npx -y @chbo297/infoflow-openclaw-tools@beta update --version 2026.5.8-beta.1 --registry https://registry.npmjs.org
 ```
 
 方式 B：通过 OpenClaw 插件命令安装
 
+<!-- sync:infoflow-plugin-version -->
 ```bash
 # 正式版
-openclaw plugins install @chbo297/infoflow@2026.5.6
+openclaw plugins install @chbo297/infoflow@2026.5.8
+```
+<!-- /sync:infoflow-plugin-version -->
 
-# Beta 版（示例）
-openclaw plugins install @chbo297/infoflow@2026.5.7-beta.2
+```bash
+# Beta 版（示例，版本号请按实际预发包替换）
+openclaw plugins install @chbo297/infoflow@2026.5.8-beta.1
 ```
 
 安装后建议检查插件状态：
@@ -72,9 +80,11 @@ openclaw plugins inspect infoflow
 
 发布到 npm 后，可直接通过独立 tools 包执行安装/升级：
 
+<!-- sync:infoflow-plugin-version -->
 ```bash
-npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.6 --registry https://registry.npmjs.org
+npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.8 --registry https://registry.npmjs.org
 ```
+<!-- /sync:infoflow-plugin-version -->
 
 常用参数：
 
@@ -97,28 +107,34 @@ npx -y @chbo297/infoflow-openclaw-tools update --version 2026.5.6 --registry htt
 
 ### 版本升级、打 tag、推送与 npm 发布流程
 
-每次发布新版本（例如 `2026.5.6`）建议按以下顺序执行：
+每次发布新版本时，先将 `package.json` 的 `version` 设为待发版本号，再按下述顺序执行。上文「首次安装 / npx 更新」与下文发版流程中，各 bash 代码块外侧有一对用于自动替换的 HTML 注释标记；发版前请执行 **`npm run sync-readme-install-version`**，脚本会按当前 `package.json` 的 `version` 更新这些块内的版本号，以免 README 与 npm 不一致。
 
+<!-- sync:infoflow-plugin-version -->
 ```bash
 # 1) 修改版本号（会同步 package-lock.json）
-npm version 2026.5.6 --no-git-tag-version
+npm version 2026.5.8 --no-git-tag-version
 
-# 2) 发布前校验
+# 2) 同步 README 中标记块内的推荐安装命令与下文中的 tag / commit 示例版本号
+npm run sync-readme-install-version
+
+# 3) 发布前校验
 npm run typecheck
 npm run test
 npm run build
 
-# 3) 提交版本变更
-git add package.json package-lock.json README.md scripts src
-git commit -m "2026.5.6"
+# 4) 提交版本变更（含 README、CHANGELOG 等）
+git add package.json package-lock.json README.md CHANGELOG.md scripts src
+git commit -m "2026.5.8"
 
-# 4) 打 tag 并推送代码与 tag
-git tag 2026.5.6
+# 5) 打 tag 并推送代码与 tag
+git tag 2026.5.8
 git push origin main
-git push origin 2026.5.6
+git push origin 2026.5.8
 
-# 5) 发布 npm（可按需指定 registry）
+# 6) 发布 npm（可按需指定 registry）
 npm publish
 # 或
 # npm publish --registry https://registry.npmjs.org
-```
+```
+<!-- /sync:infoflow-plugin-version -->
+

package/dist/src/bot.js

@@ -211,12 +211,10 @@ function checkReplyToBot(bodyItems, accountId) {
     }
     return false;
 }
-// ---------------------------------------------------------------------------
-// Shared reply judgment rules (reused across prompt builders)
-// ---------------------------------------------------------------------------
 /** Shared judgment rules and reply format requirements for all conditional-reply prompts */
-function buildReplyJudgmentRules() {
-    return [
+function buildReplyJudgmentRules(options) {
+    const variant = options?.variant ?? "default";
+    const lines = [
         "# Rules for Group Message Response",
         "",
         "## When to Reply",
@@ -231,19 +229,12 @@ function buildReplyJudgmentRules() {
         "Do NOT reply if ANY of the following is true:",
         "- The message is casual chatter, banter, emoji-only, or has no actionable question/request",
         "- The user explicitly indicates they don't want your response",
-        "- The message is directed at another person, not at you",
-        "- You lack the context or knowledge to give a useful answer (e.g., private/internal info you don't have access to)",
-        "- The message intent is ambiguous and a wrong guess would be more disruptive than silence",
-        "",
-        "## Response Format",
-        "",
-        "- If you can answer: respond directly and concisely. Do not explain why you chose to answer. Do not add filler or pleasantries.",
-        "- If you cannot answer: output exactly `NO_REPLY` — nothing else, no explanation, no apology.",
-        "",
-        "## Guiding Principle",
-        "",
-        "When in doubt, prefer silence (`NO_REPLY`). A missing reply is far less disruptive than an irrelevant or incorrect one in a group chat.",
-    ].join("\n");
+    ];
+    if (variant === "default") {
+        lines.push("- The message is directed at another person, not at you");
+    }
+    lines.push("- You lack the context or knowledge to give a useful answer (e.g., private/internal info you don't have access to)", "- The message intent is ambiguous and a wrong guess would be more disruptive than silence", "", "## Response Format", "", "- If you can answer: respond directly and concisely. Do not explain why you chose to answer. Do not add filler or pleasantries.", "- If you cannot answer: output exactly `NO_REPLY` — nothing else, no explanation, no apology.", "", "## Guiding Principle", "", "When in doubt, prefer silence (`NO_REPLY`). A missing reply is far less disruptive than an irrelevant or incorrect one in a group chat.");
+    return lines.join("\n");
 }
 /**
  * Build a GroupSystemPrompt for watch-mention triggered messages.
@@ -251,10 +242,11 @@ function buildReplyJudgmentRules() {
  */
 function buildWatchMentionPrompt(mentionedId) {
     return [
-        `Someone in the group @mentioned ${mentionedId}. As ${mentionedId}'s assistant, you observed this message.`,
-        "Decide whether you can answer on their behalf or provide help.",
+        `Someone in the group @mentioned ${mentionedId}. You are ${mentionedId}'s assistant and you see this message.`,
+        "Before you write your reply, use the visible thread context, quoted/reply context if any, and your knowledge and tools to decide whether you can add value (a direct answer, a concrete next step, or a useful pointer). Prefer making a genuine attempt to help when context makes it reasonable; do not send exploratory or partial messages to the group—produce a single final message.",
+        "If you can provide worthwhile help or leads, reply with that information clearly and concisely. If, after that effort, you still have nothing useful to add, output exactly NO_REPLY and nothing else.",
         "",
-        buildReplyJudgmentRules(),
+        buildReplyJudgmentRules({ variant: "watchAssistant" }),
         "",
         "# Examples",
         "",
@@ -283,7 +275,7 @@ function buildWatchRegexPrompt(patterns) {
         `The message content matched one of the configured watch patterns ${label}.`,
         "As the group assistant, you observed this message. Decide whether you can provide help or a valuable reply.",
         "",
-        buildReplyJudgmentRules(),
+        buildReplyJudgmentRules({ variant: "watchAssistant" }),
     ].join("\n");
 }
 /**
@@ -317,6 +309,21 @@ function buildProactivePrompt() {
         buildReplyJudgmentRules(),
     ].join("\n");
 }
+/**
+ * Appended last to every group-chat GroupSystemPrompt. Keeps the visible group reply
+ * conclusion-oriented: no raw tool transcripts or retrieval dumps; multi-step work
+ * stays in subagent (or equivalent) with only a synthesized answer to the group.
+ */
+function buildGroupOutputHygienePrompt() {
+    return [
+        "# Group chat output (hard constraint)",
+        "",
+        "- Reply to the group with **only the final user-facing answer** in one concise message (or a few short messages if the channel requires splitting).",
+        "- **Do not** include tool-call traces, raw intermediate search/retrieval payloads, or long scratchpad-style reasoning in the group-visible text.",
+        "- If the task needs exploration across multiple steps, do that work in a **subagent** (or equivalent isolated context) and return **only** the merged conclusion to the group.",
+        "- If the user explicitly asks for your reasoning or steps, satisfy that with a **brief** numbered or bulleted summary **inside the same** conclusion-style reply — still **not** raw tool logs or full intermediate dumps.",
+    ].join("\n");
+}
 // ---------------------------------------------------------------------------
 // Group reply tracking (in-memory) for follow-up window
 // ---------------------------------------------------------------------------
@@ -930,6 +937,12 @@ export async function handleInfoflowMessage(params) {
                 ? `${existing}\n\n---\n\n${groupCfg.systemPrompt}`
                 : groupCfg.systemPrompt;
         }
+        // Default output hygiene for every dispatched group message (always last)
+        const hygiene = buildGroupOutputHygienePrompt();
+        const beforeHygiene = ctxPayload.GroupSystemPrompt ?? "";
+        ctxPayload.GroupSystemPrompt = beforeHygiene
+            ? `${beforeHygiene}\n\n---\n\n${hygiene}`
+            : hygiene;
     }
     // Build unified target: "group:<id>" for group chat, username for private chat
     const to = isGroup && groupId !== undefined ? `group:${groupId}` : fromuser;
@@ -1008,3 +1021,5 @@ export const _extractMentionIds = extractMentionIds;
 export const _checkWatchRegex = checkWatchRegex;
 /** @internal — Check if message is a reply to one of the bot's own messages. Only exported for tests. */
 export const _checkReplyToBot = checkReplyToBot;
+/** @internal — Group output hygiene fragment appended to GroupSystemPrompt. Only exported for tests. */
+export const _buildGroupOutputHygienePrompt = buildGroupOutputHygienePrompt;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chbo297/infoflow",
-  "version": "2026.5.7-beta.3",
+  "version": "2026.5.8",
   "description": "OpenClaw Infoflow (如流) channel plugin for Baidu enterprise messaging",
   "type": "module",
   "main": "dist/index.js",
@@ -47,7 +47,8 @@
   "scripts": {
     "build": "rm -rf dist && tsc -p tsconfig.build.json",
     "typecheck": "tsc --noEmit",
-    "test": "vitest run"
+    "test": "vitest run",
+    "sync-readme-install-version": "node scripts/sync-readme-install-version.mjs"
   },
   "devDependencies": {
     "typescript": "^6.0.3",