pi-web-ui 0.94.1 → 0.96.0

package/dist/server/present-files-tool.js

@@ -19,7 +19,7 @@
  * resolvePathForDirCheck）；回传的 `path` 是线形绝对路径（"C:/…" / "/…"），
  * 前端拿它直接打 /api/file、file_reveal、file_open_default，不受会话 cwd 影响。
  *
- * 双语约定（issue #91）：definition 走 bilingual(en, zh) 内联双语；per-call
+ * 文案约定：工具 definition（description/promptSnippet/promptGuidelines）为纯英文；per-call
  * 结果文本走 pick(lang, zh, en, key, vars)，缺表回落英文内联。
  *
  * DSH 引擎无 customTool 注册面（工具来自 shipped preset），本工具只服务 pi 引擎。
@@ -28,7 +28,7 @@ import { open, stat } from "node:fs/promises";
 import { basename, extname, sep } from "node:path";
 import { defineTool } from "@earendil-works/pi-coding-agent";
 import { Type } from "typebox";
-import { bilingual, pick } from "./i18n.js";
+import { pick } from "./i18n.js";
 import { resolvePathForDirCheck } from "./read-tool.js";
 import { decodeText, isAudioFile, looksLikeText, previewKind } from "./text-sniff.js";
 import { PRESENT_FILES_TOOL_NAME } from "./tool-manager.js";
@@ -239,17 +239,14 @@ export function makePresentFilesTool(fallbackCwd, options = {}) {
     return defineTool({
         name: PRESENT_FILES_TOOL_NAME,
         label: "Show files to the user",
-        description: bilingual("Show files to the user as preview cards in the chat. Each item renders as a card: images/videos/audio are displayed inline, text/markdown/HTML can be opened in the preview dialog, and every card carries buttons to open the file locally, reveal it in the file manager, download it or copy its path. " +
-            "Use it whenever the user should LOOK at an artifact you produced or changed: a screenshot, chart, diagram, generated video/audio, report, log, build output. " +
-            "Give workspace-relative paths (or absolute ones); up to 12 items per call; `title` and `note` are shown above the cards, `caption` under the file name, and `focus: true` makes the client open that item in the preview dialog right away. " +
-            "Do not use it for files you merely read while reasoning, and do not repeat the file contents in your reply afterwards.", "把文件作为预览卡片展示给用户。每个条目渲染成一张卡片：图片/视频/音频直接在对话里显示，文本/markdown/HTML 可一键打开预览弹窗，每张卡片都带「本地打开 / 在文件管理器中显示 / 下载 / 复制路径」按钮。" +
-            "适合用户**应该看一眼**的产物：截图、图表、示意图、生成的视频音频、报告、日志、构建产物。" +
-            "路径写工作区相对路径（或绝对路径）；单次最多 12 条；`title`/`note` 显示在卡片上方，`caption` 显示在文件名旁，`focus: true` 让客户端立刻用预览弹窗打开该条目。" +
-            "只是自己读文件来推理时不要调用它，调用后也不要在回复里把文件内容再贴一遍。"),
-        promptSnippet: bilingual("show images/videos/text files to the user as preview cards", "把图片/视频/文本文件作为预览卡片展示给用户"),
+        description: "Show files to the user as preview cards in the chat: images/videos/audio inline, text/markdown/HTML in a preview dialog; each card can open locally, reveal in file manager, download, or copy path. " +
+            "Use whenever the user should LOOK at an artifact you produced or changed (screenshot, chart, diagram, video/audio, report, log, build output). " +
+            "Give workspace-relative paths (max 12 items); `title`/`note` show above the cards, `caption` next to the file name, `focus: true` opens that item in the preview dialog immediately. " +
+            "Do not use for files you merely read while reasoning, and do not repeat file contents in your reply.",
+        promptSnippet: "show images/videos/text files to the user as preview cards",
         promptGuidelines: [
-            bilingual("After producing something visual or user-facing (screenshot, chart, video, report, log, build output), call present_files so the user can actually see it instead of only printing the path", "产出可视化或面向用户的文件后（截图、图表、视频、报告、日志、构建产物），调 present_files 让用户真的看到，而不是只打印一行路径"),
-            bilingual("Do not call present_files for ordinary source edits the user did not ask to see, and never call it twice for the same file in one turn", "用户没要求看的普通源码改动不要用 present_files；同一轮里不要为同一个文件调两次"),
+            "After producing something visual or user-facing (screenshot, chart, video, report, log, build output), call present_files so the user can actually see it instead of only printing the path",
+            "Do not call present_files for ordinary source edits the user did not ask to see, and never call it twice for the same file in one turn",
         ],
         parameters: Type.Object({
             title: Type.Optional(Type.String({

package/dist/server/process-utils.js

@@ -86,16 +86,26 @@ export async function snapshotProcessParents() {
         return undefined;
     }
 }
-/** Kill a pid and its whole process tree (cross-platform). */
-export function killPidTree(pid) {
+/** Kill a pid and its whole process tree (cross-platform).
+ *
+ * The returned promise is only meaningful on Windows, where taskkill is itself
+ * asynchronous. Existing callers may continue to ignore it for best-effort
+ * background cleanup; callers that own a deadline can await completion. */
+export async function killPidTree(pid) {
+    // pid 下界防护：pid<=1（init / Windows System 级 pid）或自身 pid 绝不能杀 ——
+    // POSIX 的 -pid 是进程组语义，误传 0/1/自身 pid 会杀掉整组无辜进程甚至本进程。
+    if (!(pid > 1 && pid !== process.pid))
+        return;
     try {
         if (process.platform === "win32") {
-            void import("node:child_process").then(({ spawn }) => {
-                spawn("taskkill", ["/F", "/T", "/PID", String(pid)], {
+            const { spawn } = await import("node:child_process");
+            await new Promise((resolve) => {
+                const killer = spawn("taskkill", ["/F", "/T", "/PID", String(pid)], {
                     stdio: "ignore",
-                    detached: true,
                     windowsHide: true,
-                }).unref();
+                });
+                killer.once("error", () => resolve());
+                killer.once("close", () => resolve());
             });
         }
         else {

package/dist/server/prompt-composer.js

@@ -249,3 +249,12 @@ export function renderPromptTemplate(template, texts, overrides) {
 export function renderDefaultPrompt(texts) {
     return renderPromptTemplate(DEFAULT_PROMPT_TEMPLATE, texts, undefined);
 }
+const CJK_RE = /[\u3040-\u30ff\u3400-\u4dbf\u4e00-\u9fff\uf900-\ufaff\uac00-\ud7af]/gu;
+/** 粗略 token 估算（设置面板预览用，非精确分词，无 tokenizer 依赖）：
+ *  CJK 字符（汉字/假名/谚文）≈ 1 token/字，其余字符 ≈ 1 token / 4 字符。 */
+export function estimatePromptTokens(text) {
+    if (!text)
+        return 0;
+    const cjk = text.match(CJK_RE)?.length ?? 0;
+    return Math.ceil(cjk + (text.length - cjk) / 4);
+}

package/dist/server/protocol-version.js

@@ -8,4 +8,4 @@
  * its own copy in web/src/protocol-version.ts; scripts/check-protocol-sync.mjs
  * verifies the two never drift.
  */
-export const PROTOCOL_VERSION = 19;
+export const PROTOCOL_VERSION = 20;

package/dist/server/read-tool.js

@@ -12,11 +12,16 @@
  * 与 SDK ls 完全一致）；其余情况（文件、图片、路径不存在、读取报错）原样
  * 转发基底，行为与内置完全一致。
  *
+ * 基底也可能是**第三方扩展注册的 read**：`customTools` 恒胜、会把它顶掉（见
+ * tool-overrides.ts），所以那种情况下改走 `withReadDirSupport()` —— 把扩展的实现
+ * 整个当基底叠目录能力，它的 schema/描述/prompt 指引/渲染原样保留（扩展独有的参数
+ * 照旧可用），只有目录分支归 pi-web-ui。
+ *
  * 开关：`readDirEnabled`（设置面板「工具」页，默认开）。**行为开关**不是
  * ActiveSet 开关（read 本体不可关，关了 agent 就残了），因此不进
  * tool-manager 的 AGENT_TOOL_CATALOG；每次调用实时读设置，改动即时生效。
  *
- * 双语约定（issue #91）：definition 走 bilingual(en, zh) 内联双语；per-call
+ * 文案约定：工具 definition（description/promptSnippet/promptGuidelines）为纯英文；per-call
  * 返回文本（目录头）按 lang 取 pick(lang, zh, en, key)，缺表回落英文内联。
  *
  * DSH 引擎无 customTool 注册面（工具来自 shipped preset），本覆盖只服务 pi 引擎。
@@ -26,7 +31,7 @@ import { homedir } from "node:os";
 import { isAbsolute, join, resolve as nodeResolve } from "node:path";
 import { DEFAULT_MAX_BYTES, DEFAULT_MAX_LINES, createLsToolDefinition, createReadToolDefinition, defineTool, } from "@earendil-works/pi-coding-agent";
 import { Type } from "typebox";
-import { bilingual, pick } from "./i18n.js";
+import { pick } from "./i18n.js";
 const UNICODE_SPACES = /[\u00A0\u2000-\u200A\u202F\u205F\u3000]/g;
 /**
  * 目录判定用的路径归一：~ / @ 前缀、Unicode 空格、相对 → 绝对（对齐 SDK
@@ -56,16 +61,16 @@ export async function isDirectoryPath(absolutePath) {
 /** 覆盖定义的参数 schema：内置的 path/offset/limit + file_path 别名。 */
 const readDirSchema = Type.Object({
     path: Type.String({
-        description: bilingual("Path to the file (or directory) to read (relative or absolute)", "要读取的文件（或目录）路径（相对或绝对）"),
+        description: "Path to the file (or directory) to read (relative or absolute)",
     }),
     file_path: Type.Optional(Type.String({
-        description: bilingual("Alias of `path` — some clients/models emit file_path; if both are given, `path` wins", "`path` 的别名 —— 部分客户端/模型习惯发 file_path；两者都给时以 `path` 为准"),
+        description: "Alias of `path` — some clients/models emit file_path; if both are given, `path` wins",
     })),
     offset: Type.Optional(Type.Number({
-        description: bilingual("Line number to start reading from (1-indexed)", "从第几行开始读（从 1 起算）"),
+        description: "Line number to start reading from (1-indexed)",
     })),
     limit: Type.Optional(Type.Number({
-        description: bilingual("Maximum number of lines to read (for a directory path: maximum number of entries)", "最多读多少行（路径是目录时 = 最多列多少条目）"),
+        description: "Maximum number of lines to read (for a directory path: maximum number of entries)",
     })),
 }, {});
 /**
@@ -81,9 +86,59 @@ export function prepareReadArguments(raw) {
     // 两者都没给时这里仍缺 path（静态类型是谎，运行时交给 schema 校验报错）。
     return args;
 }
+/** Directory support note appended to any read definition (definitions are English-only). */
+const DIR_DESCRIPTION_NOTE = "Also accepts a directory path: its entries are then listed instead of file contents (one entry per line, directories suffixed with '/'); in that case `limit` caps the number of entries and `offset` is ignored.";
+const DIR_GUIDELINE = "Use read on a directory to list its entries — no need to shell out to `ls`";
+/**
+ * 两条路（内置基底 / 扩展基底）共用的执行体：先判「路径是不是目录」—— 是就复用 SDK 的
+ * ls 列条目（排序/`/` 后缀/截断提示口径一致），否则把请求转发给基底实现。
+ *
+ * `normalizePath`：只给了 `file_path` 别名时补出 `path` 再转发（SDK 内置实现需要）；
+ * 扩展基底传 false —— 它自带 `prepareArguments`，参数原样交给它，免得我们这边把扩展
+ * 独有的字段（如 better-edit 的 `windows`）吃掉。
+ */
+async function dirAwareExecute(base, ls, fallbackCwd, dirEnabled, getLang, normalizePath, toolCallId, params, signal, onUpdate, ctx) {
+    const input = (params ?? {});
+    // 兜底（不依赖 prepareArguments 一定跑过）：path 缺省/空时用 file_path。
+    const rawPath = typeof input.path === "string" && input.path.trim() ? input.path : input.file_path;
+    const path = typeof rawPath === "string" ? rawPath : "";
+    if (path && dirEnabled()) {
+        const cwd = typeof ctx?.cwd === "string" ? ctx.cwd : fallbackCwd;
+        if (await isDirectoryPath(resolvePathForDirCheck(path, cwd))) {
+            const limit = typeof input.limit === "number" && input.limit > 0 ? Math.floor(input.limit) : undefined;
+            // 列目录本体完全复用 SDK 的 ls。
+            const listed = (await ls.execute(toolCallId, { path, ...(limit !== undefined ? { limit } : {}) }, signal, onUpdate, ctx));
+            const header = pick(getLang(), `[目录：${path}]`, `[Directory: ${path}]`, "read.dir.header", { path });
+            // 只取列出来的正文：截断/条目上限提示已在正文末尾，read 卡片的
+            // details 不需要 ls 的字段。
+            const content = listed.content.map((part, index) => index === 0 && part.type === "text" ? { ...part, text: `${header}\n${part.text}` } : part);
+            return { content, details: undefined };
+        }
+    }
+    return base.execute(toolCallId, (normalizePath ? { ...input, path } : params), signal, onUpdate, ctx);
+}
+/**
+ * 在**任意** read 实现（SDK 内置，或第三方扩展 `registerTool` 注册的同名工具）之上叠加
+ * 「路径是目录时列出条目」。基底的 name/label/描述/参数 schema/prepareArguments/render*
+ * 全部原样保留，只补一句目录说明与一条目录指引 —— 于是扩展的锚协议、独有参数、渲染都不丢。
+ */
+export function withReadDirSupport(base, fallbackCwd, options = {}) {
+    const dirEnabled = options.dirEnabled ?? (() => true);
+    const getLang = options.getLang ?? (() => "en");
+    const ls = createLsToolDefinition(fallbackCwd);
+    return defineTool({
+        ...base,
+        description: `${base.description} ${DIR_DESCRIPTION_NOTE}`,
+        promptGuidelines: [...(base.promptGuidelines ?? []), DIR_GUIDELINE],
+        async execute(toolCallId, params, signal, onUpdate, ctx) {
+            return dirAwareExecute(base, ls, fallbackCwd, dirEnabled, getLang, false, toolCallId, params, signal, onUpdate, ctx);
+        },
+    });
+}
 /**
- * 生成「read 读目录」覆盖定义。cwd 仅供创建时固定；执行时优先 ctx.cwd
- * （会话工作区）。
+ * 生成「read 读目录」覆盖定义（**没有**扩展同名工具时的完整实现：内置基底 + 英文描述 +
+ * `file_path` 别名）。cwd 仅供创建时固定；执行时优先 ctx.cwd（会话工作区）。
+ * 有扩展同名工具时改用 `withReadDirSupport` 组合它的实现（见 tool-overrides.ts）。
  */
 export function makeReadDirTool(fallbackCwd, options = {}) {
     const base = createReadToolDefinition(fallbackCwd);
@@ -92,34 +147,18 @@ export function makeReadDirTool(fallbackCwd, options = {}) {
     const getLang = options.getLang ?? (() => "en");
     return defineTool({
         ...base,
-        description: bilingual(`${base.description} Also accepts \`file_path\` as an alias of \`path\`. If the path is a directory, its entries are listed instead of file contents (one entry per line, directories suffixed with '/'); in that case \`limit\` caps the number of entries and \`offset\` is ignored.`, `读取文件内容。支持文本文件与图片（jpg, png, gif, webp, bmp），图片作为附件发出。文本输出截断到 ${DEFAULT_MAX_LINES} 行或 ${DEFAULT_MAX_BYTES / 1024}KB（先到者为准），大文件用 offset/limit 续读。路径也可用 \`file_path\` 传（path 的别名，两者都给时以 path 为准）。路径是目录时改为列出目录条目（一行一项，目录带 '/' 后缀；此时 limit 是条目上限，offset 忽略）。`),
-        promptSnippet: bilingual("Read file contents (a directory path lists its entries)", "读取文件内容（传目录则列出其条目）"),
+        description: `${base.description} Also accepts \`file_path\` as an alias of \`path\`. ` +
+            "If the path is a directory, its entries are listed instead (one per line, directories suffixed with '/'); `limit` caps the entries and `offset` is ignored.",
+        promptSnippet: "Read file contents (a directory path lists its entries)",
         promptGuidelines: [
             ...(base.promptGuidelines ?? []),
-            bilingual("Use read on a directory to list its entries — no need to shell out to `ls`", "要看目录内容直接把目录路径交给 read，不必再走 bash 的 ls"),
+            "Use read on a directory to list its entries — no need to shell out to `ls`",
         ],
         parameters: readDirSchema,
         prepareArguments: prepareReadArguments,
         async execute(toolCallId, params, signal, onUpdate, ctx) {
-            const input = (params ?? {});
-            // 兜底（不依赖 prepareArguments 一定跑过）：path 缺省/空时用 file_path。
-            const rawPath = typeof input.path === "string" && input.path.trim() ? input.path : input.file_path;
-            const path = typeof rawPath === "string" ? rawPath : "";
-            if (path && dirEnabled()) {
-                const cwd = typeof ctx?.cwd === "string" ? ctx.cwd : fallbackCwd;
-                if (await isDirectoryPath(resolvePathForDirCheck(path, cwd))) {
-                    const limit = typeof input.limit === "number" && input.limit > 0 ? Math.floor(input.limit) : undefined;
-                    // 列目录本体完全复用 SDK 的 ls（排序/`/` 后缀/截断提示口径一致）。
-                    const listed = await ls.execute(toolCallId, { path, ...(limit !== undefined ? { limit } : {}) }, signal, onUpdate, ctx);
-                    const header = pick(getLang(), `[目录：${path}]`, `[Directory: ${path}]`, "read.dir.header", { path });
-                    // 只取列出来的正文：截断/条目上限提示已在正文末尾，read 卡片的
-                    // details 不需要 ls 的字段。
-                    const content = listed.content.map((part, index) => index === 0 && part.type === "text" ? { ...part, text: `${header}\n${part.text}` } : part);
-                    return { content, details: undefined };
-                }
-            }
-            // 转发内置实现时带上归一后的 path（模型可能只给了 file_path）。
-            return base.execute(toolCallId, { ...input, path }, signal, onUpdate, ctx);
+            // 目录分支与转发都在共用执行体里（normalizePath=true：只给了 file_path 时补出 path）。
+            return dirAwareExecute(base, ls, fallbackCwd, dirEnabled, getLang, true, toolCallId, params, signal, onUpdate, ctx);
         },
     });
 }

package/dist/server/resolve-global-sdk.js

@@ -1,22 +1,25 @@
 /**
- * resolve-global-sdk — 可选的「优先用全局/祖先那份 pi SDK」解析钩子（issue #260）。
+ * resolve-global-sdk — pi SDK 副本选择钩子（issue #260；#321 起默认启用）。
  *
  * 背景：pi-web-ui 依赖 `@earendil-works/pi-coding-agent`，而 npm 全局安装会把依赖
  * **嵌在** `<npm root -g>/pi-web-ui/node_modules/`（不 hoist，实测），Node 又「嵌套优先于
  * 祖先」—— 于是用户 `npm i -g @earendil-works/pi-coding-agent@latest` 改的是全局那份，
  * 服务加载的仍是自带那份，表现为「升了 0.86.1，横幅和 /api/health 还显示 0.85.1」。
+ * 这个割裂在 #321 里反复咬人（界面此前完全看不见），所以解析顺序默认反转：
  *
- * 本模块把解析顺序反过来，但**只在显式开启时**：
+ *   缺省 / global / auto   → 机器上有**更新**的 pi 副本（祖先链，如全局 pi CLI）就用它，
+ *                              多份取版本最高的；没有或都更旧 → 自带副本兜底。
+ *   bundled / 0 / off /
+ *   false / no             → 强制自带副本（可复现、CI 覆盖的那份；报 bug 请用它复现）。
  *
- *   PI_WEB_SDK=global   → 祖先链上存在一份版本**更新**的 SDK 时，把裸标识符重定向到它；
- *                         否则原样不动（同版本也不折腾 —— 没意义）。
- *   （缺省 / 其它值）    → 什么都不做，用自带副本。
+ * 为什么「绝不降级」：祖先副本必须严格比自带的新才采用（同版本继续用自带那份，
+ * 少一次重定向）；绝不为了「用全局」而跑更旧的版本。
  *
- * 为什么默认关：服务运行的 SDK 版本会变成「用户机器上装了什么」，同一个 pi-web-ui 版本在
- * 不同机器上跑不同 SDK，报 bug 时无法复现；自带副本可复现、且是 CI 覆盖的那一份。
- *
- * 为什么只做「必须更新」这一道门：仓库没有 semver 依赖，手写完整范围解析容易出错，
- * 「祖先那份比自带那份新」是保守且够用的判据（旧的 / 同版本的都不采用）。
+ * 为什么默认跟随（#321）：用户升级全局 pi 后界面「显示没更新」，每个版本都有人踩，
+ * 每次都要人肉排查。可复现性的代价用两条路补回来：界面更新面板与 /api/health 的
+ * `piSdkCopies` 都如实报出实际加载的那份；`PI_WEB_SDK=bundled` 随时显式换回自带。
+ * 「全局 SDK 比宿主新」的兼容风险是被接受的：pi 与 pi-web-ui 同步演进，跟随全局
+ * 正是用户升级 pi 的本意。
  *
  * 安全约定：整个注册流程包在 try/catch 里，任何异常都退回默认解析 —— 这个模块**绝不允许**
  * 让服务起不来。它必须在任何 SDK 静态 import **之前**被加载（`--import <本文件>`，
@@ -26,18 +29,28 @@ import { registerHooks } from "node:module";
 import { pathToFileURL } from "node:url";
 import { compareVersions, sdkCopies } from "./sdk-origin.js";
 const PKG = "@earendil-works/pi-coding-agent";
+/** 显式强制自带副本的取值（旧默认；可复现、CI 覆盖的那份）。 */
+const BUNDLED_MODES = new Set(["bundled", "0", "off", "false", "no"]);
 /**
  * 该用哪一份对外解析（纯函数，便于单测）。
- * `copies` 按 Node 的解析顺序（[0] = 自带的、实际会被用到的），返回 null = 保持默认。
+ * `copies` 按 Node 的解析顺序（[0] = 自带的、无钩子时实际会被用到的），
+ * 返回 null = 保持默认（用自带副本兜底）。
  */
 export function pickGlobalSdk(copies, mode) {
-    if ((mode ?? "bundled").trim().toLowerCase() !== "global")
+    if (BUNDLED_MODES.has((mode ?? "global").trim().toLowerCase()))
         return null;
     const bundled = copies[0];
-    // 只考虑祖先链上的副本，且必须是**更新**的（旧的或同版本都不折腾）。
-    return copies.slice(1).find((c) => !bundled || compareVersions(c.version, bundled.version) > 0) ?? null;
+    // 只考虑祖先链上**严格更新**的副本，多份取版本最高的（旧的/同版本的都不折腾）。
+    let best = null;
+    for (const copy of copies.slice(1)) {
+        if ((!bundled || compareVersions(copy.version, bundled.version) > 0) &&
+            (!best || compareVersions(copy.version, best.version) > 0)) {
+            best = copy;
+        }
+    }
+    return best;
 }
-/** 注册钩子；返回实际选中的副本（null = 没启用 / 没找到可用的）。 */
+/** 注册钩子；返回实际选中的副本（null = 用自带副本）。 */
 export function registerGlobalSdkPreference(mode = process.env.PI_WEB_SDK, fromFile = import.meta.url) {
     try {
         const copies = sdkCopies(fromFile);
@@ -68,5 +81,6 @@ export function registerGlobalSdkPreference(mode = process.env.PI_WEB_SDK, fromF
 // ---- 副作用：被 `--import` 加载时立刻生效 --------------------------------
 const used = registerGlobalSdkPreference();
 if (used) {
-    console.log(`[pi-web-ui] PI_WEB_SDK=global → using the pi SDK at ${used.path} (v${used.version})`);
+    console.log(`[pi-web-ui] following a newer pi SDK on this machine: ${used.path} (v${used.version}; ` +
+        "set PI_WEB_SDK=bundled to pin the bundled copy)");
 }

package/dist/server/schedule-agent-tool.js

@@ -13,12 +13,12 @@
 // 到期执行走 index.ts 的 executor：目标对话还在 → steer 语义唤醒它（不切用户
 // 当前对话）；不在了（关闭/重启）→ 回落原有无头执行；单次任务触发后自动删除。
 //
-// 双语约定（issue #91）：definition 走 bilingual(en, zh) 内联双语；per-call
+// 文案约定：工具 definition（description/promptSnippet/promptGuidelines）为纯英文；per-call
 // 返回文本按 lang 取 pick(lang, zh, en, key, vars)，缺表回落英文内联。
 // ---------------------------------------------------------------------------
 import { defineTool } from "@earendil-works/pi-coding-agent";
 import { Type } from "typebox";
-import { bilingual, pick } from "./i18n.js";
+import { pick } from "./i18n.js";
 import { SCHEDULE_CANCEL_TOOL_NAME, SCHEDULE_LIST_TOOL_NAME, SCHEDULE_TASK_TOOL_NAME } from "./tool-manager.js";
 import { computeNextFire, describeIntervalMs, SCHEDULER_MIN_INTERVAL_MS, } from "./scheduler-tasks.js";
 import { parseCronSpec } from "./plugin-schedule.js";
@@ -107,17 +107,11 @@ export function makeScheduleTools(host, ownerConversationId, lang) {
     const taskTool = defineTool({
         name: SCHEDULE_TASK_TOOL_NAME,
         label: "Schedule a wake-up in this conversation",
-        description: bilingual("Create a scheduled wake-up in the CURRENT conversation: at the given cron time or after the given delay, the scheduler automatically delivers your prompt back into this conversation so you continue the work and report to the user. " +
-            "Use it when the user asks for periodic checks, delayed reminders, or scheduled summaries — do NOT fake it with sleep loops (a sleeping script can never push a message back). " +
-            'Schedule accepts a 5-field cron ("0 * * * *" = hourly) or a relative delay ("in 30m", "in 1h", "30m"); minimum interval is 60s. ' +
-            "One-shot by default (recurring=false auto-deletes the task after it fires); pass recurring=true for repeats. " +
-            "The wake-up binds the originating conversation AND its persisted session file: after context compaction or a restart the scheduler re-binds to the same session automatically; if the original conversation is gone it first falls back to the project's active conversation (and visibly reports the move), and only runs headless (report in panel history) when no live conversation exists for the project. " +
-            "Manage with schedule_list / schedule_cancel; the user can also cancel from the background-tasks panel.", "在**当前对话**里创建一个定时唤醒：到指定 cron 时间或延迟后，调度器自动把你的 prompt 投回本对话，你继续执行并向用户汇报。" +
-            "用户要求定时巡检、延时提醒、定时汇总时用它 —— 不要用 sleep 死循环假装答应（休眠的脚本推不回任何消息）。" +
-            "时间写法收 5 字段 cron（“0 * * * *”=每小时）或相对延迟（“in 30m”“in 1h”“30m”）；最短间隔 60s。" +
-            "默认单次（recurring=false 触发后自动删除）；传 recurring=true 做周期任务。" +
-            "唤醒绑定发起对话与其落盘会话文件：上下文压缩或重启后自动重绑到同一会话；原对话不在时先回落到同项目的活跃对话（并明确提示迁移），同项目无存活对话才无头执行，报告留在调度面板历史里。" +
-            "用 schedule_list / schedule_cancel 管理；用户也可从后台任务面板取消。"),
+        description: "Create a scheduled wake-up in the CURRENT conversation: at the cron time or after the delay, your prompt is delivered back into this conversation so you continue and report. " +
+            "Use for periodic checks, delayed reminders, scheduled summaries — never sleep loops (they cannot push messages back). " +
+            'schedule: 5-field cron ("0 * * * *" hourly) or delay ("in 30m"); minimum 60s. One-shot by default; recurring=true repeats. ' +
+            "Re-binds to the same session after compaction/restart; if the conversation is gone it falls back to the project's active conversation (visibly reported), headless only when none exists. " +
+            "Manage with schedule_list / schedule_cancel.",
         promptSnippet: "schedule a wake-up in this conversation (cron or delay), auto-report on fire",
         parameters: Type.Object({
             schedule: Type.String({
@@ -210,7 +204,9 @@ export function makeScheduleTools(host, ownerConversationId, lang) {
     const listTool = defineTool({
         name: SCHEDULE_LIST_TOOL_NAME,
         label: "List scheduled tasks",
-        description: bilingual("List all built-in scheduled tasks (all projects): id, name, cron/interval, on/paused, one-shot, target conversation, next fire, last run. Use it to inspect before cancelling, or to answer the user about what is scheduled.", "列出全部内置定时任务（跨项目）：id、名称、cron/间隔、启用/暂停、单次、目标对话、下次触发、上次结果。取消前先看，或回答用户“排了什么”时用。"),
+        description: "List all built-in scheduled tasks (all projects): " +
+            "id, name, cron/interval, on/paused, one-shot, target conversation, next fire, last run. " +
+            "Use it to inspect before cancelling, or to answer the user about what is scheduled.",
         promptSnippet: "list scheduled wake-up tasks",
         parameters: Type.Object({}),
         execute: async () => {
@@ -235,7 +231,8 @@ export function makeScheduleTools(host, ownerConversationId, lang) {
     const cancelTool = defineTool({
         name: SCHEDULE_CANCEL_TOOL_NAME,
         label: "Cancel a scheduled task",
-        description: bilingual("Delete a scheduled task by id (see schedule_list). Deleting stops all future fires; use it when the user says the schedule is no longer needed.", "按 id 删除定时任务（id 见 schedule_list）。删除后不再触发；用户说不用排了时用它。"),
+        description: "Delete a scheduled task by id (see schedule_list). " +
+            "Deleting stops all future fires; use it when the user says the schedule is no longer needed.",
         promptSnippet: "cancel a scheduled task by id",
         parameters: Type.Object({
             id: Type.String({ description: "Task id from schedule_list." }),

package/dist/server/scheduler-tasks.js

@@ -347,6 +347,12 @@ export class SchedulerStore {
         if (ok) {
             this.save();
             this.changed();
+            try {
+                this.opts.onTaskRemoved?.(id);
+            }
+            catch {
+                /* 回调失败不影响删除 */
+            }
         }
         return ok;
     }

package/dist/server/sdk-origin.js

@@ -52,13 +52,29 @@ export function compareVersions(a, b) {
     return 0;
 }
 /**
- * 启动横幅要打印的一行（不含前缀），以及是否需要提示「你升的不是服务在用的那份」。
+ * 本进程实际加载的是否为**随包自带**的那份（未被钩子重定向到祖先链副本）。
+ * 判据：自带副本是解析顺序上的第一份，且钩子只在祖先副本**严格更新**时才重定向
+ * （同版本继续用自带），所以 running == copies[0] ⟺ 自带在用。copies 为空
+ * （如部分桌面/容器布局）时按自带算 —— 那本来就是唯一能加载的份。
+ * UI 用它决定是否亮「安装全局引擎并切换」入口（issue #321）。
+ */
+export function isBundledInUse(copies, effectiveVersion) {
+    return copies.length === 0 || effectiveVersion === copies[0].version;
+}
+/**
+ * 启动横幅要打印的一行（不含前缀），以及是否需要提示「本进程在用的不是最新的那份」。
  * `effective` 为空时（没找到副本）返回空串，调用方照旧只打印版本号。
+ *
+ * #321 起默认会自动跟随更新的那份（resolve-global-sdk），所以这条提示出现即意味着：
+ * 进程启动时没跟上（升级发生在启动后 / 旧构建没注入钩子），或用户显式
+ * PI_WEB_SDK=bundled 钉死了自带副本 —— 文案把两种出路都写明。
  */
 export function sdkOriginNote(copies, effectiveVersion) {
     const shadowed = copies.slice(1);
     const newer = shadowed.filter((c) => compareVersions(c.version, effectiveVersion) > 0);
     if (newer.length === 0)
         return null;
-    return `a newer pi SDK is installed elsewhere (${newer.map((c) => `v${c.version}`).join(", ")}) but pi-web-ui runs its own bundled copy (v${effectiveVersion}).`;
+    return (`a newer pi SDK is installed on this machine (${newer.map((c) => `v${c.version}`).join(", ")}) ` +
+        `but this process runs v${effectiveVersion} — restart to follow it (default), ` +
+        `or set PI_WEB_SDK=bundled to pin the bundled copy.`);
 }