pi-naming 0.2.1 → 0.4.0

package/README.md

@@ -42,7 +42,7 @@ File: `<pi-agent-dir>/extensions/pi-naming/config.json`; respects `PI_CODING_AGE
 }
 ```
 
-`automaticNaming` and `manualNaming` independently control the automatic input hook and `/rename`. `targets` controls session, workspace and tab separately; all default to enabled. Disable both terminal targets for session-only naming without loading the terminal module.
+`automaticNaming` and `manualNaming` independently control the automatic input hook and `/rename`. `targets` directly controls session, workspace and tab separately; all targets default to enabled. Disable both terminal targets for session-only naming without loading the terminal module.
 
 | Title field | Default | Meaning |
 | --- | --- | --- |
@@ -64,9 +64,9 @@ For longer English titles use `maxLength: 60`, `preferredLength: 40`, `language:
 - tmux/WezTerm/Otty/Orca splits do not prove exclusive window/tab ownership. Unverified targets are skipped with an explanation rather than expanding the operation's scope.
 - With `pi-interactive-subagents`, explicitly include this package's entrypoint in `subagentExtensions`. Installing it in the parent does not bypass child extension isolation.
 
-Ordinary sessions use the configured terminal-mux defaults. The following terminal-mux variables remain only as compatibility inputs for older launchers: `PI_SUBAGENT_RENAME_TMUX_WINDOW=1`, `PI_SUBAGENT_RENAME_TMUX_SESSION=1`, `PI_SUBAGENT_RENAME_HERDR_WORKSPACE=1`. Missing target IDs never fall back to current focus or the first tab. Actual targets can be panes, tabs, windows, workspaces or sessions and are reported in results.
+Ordinary sessions request every enabled target with an explicit ID, including supported tmux and Herdr targets. This target-resolution path deliberately ignores the legacy `PI_SUBAGENT_RENAME_TMUX_WINDOW`, `PI_SUBAGENT_RENAME_TMUX_SESSION` and `PI_SUBAGENT_RENAME_HERDR_WORKSPACE` switches; those variables remain only for terminal-mux's older public rename APIs. A disabled `targets` entry does not run even if an environment variable is set. Missing IDs never fall back to current focus or the first tab.
 
-Before publication, align the terminal-mux dependency minimum with a published version providing the target ownership API.
+`pi-naming` requires a published `pi-terminal-mux` version that exports `resolveTerminalRenameTargets` and `renameTerminalTarget`. Release-please updates workspace dependency ranges in release PRs. When one release publishes both packages, CI publishes terminal-mux first and publishes naming only after that npm publication succeeds; a naming-only release uses the already published compatible mux. Do not manually publish or preemptively raise the range to an unpublished version.
 
 ## Validation
 

package/README.zh-CN.md

@@ -42,7 +42,7 @@ pi install npm:pi-naming
 }
 ```
 
-`automaticNaming` 和 `manualNaming` 独立控制自动入口和 `/rename` 命令。`targets` 分别控制 session、workspace、tab；全部默认开启。仅需 session 命名时关闭两个终端目标，此时不加载终端模块。
+`automaticNaming` 和 `manualNaming` 独立控制自动入口和 `/rename` 命令。`targets` 直接分别控制 session、workspace、tab，三个目标默认开启。仅需 session 命名时关闭两个终端目标，此时不加载终端模块。
 
 | 标题字段 | 默认值 | 含义 |
 | --- | --- | --- |
@@ -64,9 +64,9 @@ pi install npm:pi-naming
 - tmux/WezTerm/Otty/Orca 分屏不代表独占 window/tab，归属无法确认时跳过并说明原因，不扩大操作范围。
 - 使用 `pi-interactive-subagents` 时，需在它的 `subagentExtensions` 中显式加载本包入口；仅在主会话安装本包不会绕过子代理的扩展隔离设置。
 
-普通会话使用配置文件中的 mux 默认值。以下终端变量仅作为旧版启动器的兼容输入保留：`PI_SUBAGENT_RENAME_TMUX_WINDOW=1`、`PI_SUBAGENT_RENAME_TMUX_SESSION=1`、`PI_SUBAGENT_RENAME_HERDR_WORKSPACE=1`。终端目标缺少 ID 时不会使用当前焦点或第一个 tab 代替。实际目标可能是 pane、tab、window、workspace 或 session，结果中会说明。
+普通会话会请求每个启用且具备明确 ID 的目标，包括受支持的 tmux 和 Herdr 目标。此目标解析路径刻意忽略旧变量 `PI_SUBAGENT_RENAME_TMUX_WINDOW`、`PI_SUBAGENT_RENAME_TMUX_SESSION`、`PI_SUBAGENT_RENAME_HERDR_WORKSPACE`；它们仅保留给 terminal-mux 的旧公开改名接口。即使环境变量为 `1`，关闭的 `targets` 也绝不执行。终端目标缺少 ID 时不会使用当前焦点或第一个 tab 代替。实际目标可能是 pane、tab、window、workspace 或 session，结果中会说明。
 
-发布前，terminal-mux 依赖下限必须对齐实际提供目标归属 API 的已发布版本。
+`pi-naming` 依赖已发布且导出 `resolveTerminalRenameTargets`、`renameTerminalTarget` 的 `pi-terminal-mux` 版本。release-please 会在 Release PR 中更新 workspace 依赖范围；同一次发布同时包含两包时，CI 先发布 terminal-mux，只有其 npm 发布成功后才发布 naming；仅发布 naming 时使用已发布的兼容 mux。不手动发布，也不预先把范围改成未发布版本。
 
 ## 验证
 

package/SKILL.md

@@ -9,9 +9,9 @@ description: 配置 Pi 统一 /rename、首条消息命名和终端目标归属
 
 Use `/config:naming` to open the normal TUI settings menu; use `reset` for defaults and reload after saving.
 
-- `automaticNaming` / `manualNaming` 控制自动输入和 `/rename [名称]`，`targets` 分别控制 session/workspace/tab。Control automatic input and `/rename [name]`; `targets` selects session/workspace/tab.
+- `automaticNaming` / `manualNaming` 控制自动输入和 `/rename [名称]`，`targets` 直接分别控制 session/workspace/tab。Control automatic input and `/rename [name]`; `targets` directly selects session/workspace/tab.
 - `title` 控制长度、语言、补充提示和超时；模型鉴权复用 Pi。Controls length, language, instructions and timeout; model authentication comes from Pi.
-- 无终端也可命名 session；终端失败与跳过必须报告。Session naming works without a terminal; report terminal failures and skips.
+- 无终端也可命名 session；终端失败与跳过必须报告。普通会话明确目标路径不受旧 `PI_SUBAGENT_RENAME_*` 变量影响；关闭 target 即使变量为 `1` 也不执行。Session naming works without a terminal; report terminal failures and skips. The ordinary-session explicit-target path ignores legacy `PI_SUBAGENT_RENAME_*` variables; a disabled target never runs even when a variable is `1`.
 - 子进程归属由启动方通过 mux 协议提供，不把 pane 扩大为共享 tab，不修改父 workspace。Launchers grant child targets through the mux protocol; never expand a pane to a shared tab or rename the parent workspace.
 - 子代理需要显式配置 `subagentExtensions` 加载 naming。Child extension isolation requires explicitly loading naming in `subagentExtensions`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-naming",
-  "version": "0.2.1",
+  "version": "0.4.0",
   "description": "Configurable Pi session naming and manual terminal workspace/tab renaming",
   "type": "module",
   "main": "./index.ts",
@@ -57,19 +57,19 @@
     "workspace"
   ],
   "dependencies": {
-    "pi-extensions-i18n": "^0.4.0",
-    "pi-terminal-mux": "^0.5.1"
+    "pi-extensions-i18n": "^0.5.0",
+    "pi-terminal-mux": "^0.6.2"
   },
   "peerDependencies": {
-    "@earendil-works/pi-coding-agent": ">=0.80.0 <0.81.0",
-    "@earendil-works/pi-ai": ">=0.80.0 <0.81.0"
+    "@earendil-works/pi-coding-agent": ">=0.80.0",
+    "@earendil-works/pi-ai": ">=0.80.0"
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "0.80.10",
+    "@earendil-works/pi-coding-agent": "0.85.1",
     "@types/node": "24.12.4",
-    "pi-terminal-mux": "^0.5.1",
+    "pi-terminal-mux": "^0.6.2",
     "tsx": "4.23.1",
     "typescript": "5.9.3",
-    "@earendil-works/pi-ai": "0.80.10"
+    "@earendil-works/pi-ai": "0.85.1"
   }
 }

package/src/index.ts

@@ -2,6 +2,14 @@ import type { ExtensionAPI, ExtensionCommandContext, ExtensionContext } from "@e
 import type { TerminalRenameOutcome, TerminalRenameTarget, ResolveRenameOptions } from "pi-terminal-mux";
 import { configPath, loadConfig, parseConfig, saveConfig, type NamingConfig } from "./config.ts";
 import { i18n } from "./i18n.ts";
+import { notifyWithSource, type NoticeColor, type NoticeSource } from "pi-extensions-i18n";
+
+/** 本扩展的提示标签；短且唯一，便于在会话里定位来源。 */
+const NOTICE_TAG = "naming";
+/** 提示标签颜色；与其它扩展错开，避免看起来像同一条消息。 */
+const NOTICE_COLOR: NoticeColor = "toolTitle";
+/** 本扩展的提示来源。 */
+const NOTICE_SOURCE: NoticeSource = { tag: NOTICE_TAG, color: NOTICE_COLOR };
 import { getCurrentSessionUserMessages, requestSessionNameWithTimeout, type SessionNameRequester } from "./session-name.ts";
 
 const RENAME_COMMAND = "rename";
@@ -44,12 +52,21 @@ function errorMessage(error: unknown): string {
 /** 无交互 UI 时仍通过 Pi 消息报告结果，不静默吞错。 */
 function report(pi: ExtensionAPI, ctx: ExtensionContext, notice: { message: string; level: "info" | "warning" | "error" }): void {
   const { message, level } = notice;
-  if (ctx.hasUI) ctx.ui.notify(message, level);
+  if (ctx.hasUI) notifyWithSource({ ctx, source: NOTICE_SOURCE, level, message });
   else pi.sendMessage({ customType: MESSAGE_TYPE, content: message, display: true }, { triggerTurn: false });
 }
 
+export interface NamingConfigStore {
+  load(): NamingConfig;
+  save(config: NamingConfig): void;
+  path(): string;
+}
+
 /** 注册配置命令，通过 TUI 菜单和输入框修改命名配置。 */
-function registerNamingConfigCommand(pi: ExtensionAPI): void {
+export function registerNamingConfigCommand(
+  pi: ExtensionAPI,
+  store: NamingConfigStore = { load: loadConfig, save: saveConfig, path: configPath },
+): void {
   const command = {
     description: i18n.t("configCommandDescription"),
     getArgumentCompletions: () => [{ value: CONFIG_RESET_COMMAND, label: CONFIG_RESET_COMMAND }],
@@ -61,9 +78,9 @@ function registerNamingConfigCommand(pi: ExtensionAPI): void {
       }
       if (argument === CONFIG_RESET_COMMAND) {
         try {
-          saveConfig(parseConfig({}));
+          store.save(parseConfig({}));
           report(pi, ctx, {
-            message: i18n.t("configCommandSaved", { path: configPath() }),
+            message: i18n.t("configCommandSaved", { path: store.path() }),
             level: "info",
           });
         } catch (error) {
@@ -78,7 +95,7 @@ function registerNamingConfigCommand(pi: ExtensionAPI): void {
 
       let config: NamingConfig;
       try {
-        config = loadConfig();
+        config = store.load();
       } catch (error) {
         report(pi, ctx, { message: i18n.t("configCommandInvalid", { error: errorMessage(error) }), level: "error" });
         return;
@@ -87,9 +104,9 @@ function registerNamingConfigCommand(pi: ExtensionAPI): void {
       /** Saves one validated menu change and reports its result. */
       const save = (next: NamingConfig): boolean => {
         try {
-          saveConfig(next);
+          store.save(next);
           config = next;
-          report(pi, ctx, { message: i18n.t("configCommandSaved", { path: configPath() }), level: "info" });
+          report(pi, ctx, { message: i18n.t("configCommandSaved", { path: store.path() }), level: "info" });
           return true;
         } catch (error) {
           report(pi, ctx, { message: i18n.t("configCommandInvalid", { error: errorMessage(error) }), level: "error" });