@xmoon76/dsh-pi-tui 0.4.1 → 0.4.5

package/README.en.md

@@ -19,21 +19,32 @@ Stable releases are recommended for ordinary users. Install DSH first, then add
 the TUI to the `pi-tui` profile:
 
 ```sh
-npm install -g @deepseek-ai/dsh@0.1.2-rc.1
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@latest
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
 
-### Preview / next
+### Next / npm line (validation)
 
-Preview releases contain unreleased changes. Use this channel only when you need
-to try or validate a prerelease:
+Preview installation uses the DSH `alpha` channel and the TUI `next` channel.
+The DSH native install scripts must be explicitly allowed:
 
 ```sh
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@alpha
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
 dsh --profile pi-tui
 ```
 
+Use the isolated npm driver (it installs the exact DSH version declared by this
+checkout and exercises the full build/test/package path):
+
+```sh
+pnpm compat:dsh:npm
+```
+
+See the [compatibility guide](docs/dsh-compatibility.md) for the stable minimum,
+next compatibility range, and fallback paths.
+
 ### Requirements
 
 * DeepSeek Harness
@@ -41,38 +52,25 @@ dsh --profile pi-tui
 
 ### DSH/TUI version pairing (important)
 
-| TUI package line | Matching DSH line | Notes |
+| TUI package line | Official DSH tags for the pairing | Notes |
 |---|---|---|
-| `0.4.1` (`@latest`) | `>=0.1.2-rc.1` | Current stable; validated against the rc.1 family |
-| `0.4.x-alpha` (`@next`) | `>=0.1.2-rc.1` | Subsequent prerelease; each release validates its concrete DSH family |
-| `0.4.0-alpha.2` (published) | `>=0.1.2-alpha.4` | Previous 0.4 prerelease; its releases validated the alpha.4/alpha.5 family |
-| `0.4.0-alpha.1` (published) | `>=0.1.2-alpha.2` | Earlier 0.4 prerelease; accepts the alpha.2/alpha.3 runtime |
-| `0.3.x` (`@0.3`) | `0.1.1-rc.2` | Legacy runtime line |
-
-Do not mix the lines: DSH 0.1.1 is outside the 0.4 peer window and the
-normal incompatible-runtime boundary will fail. The startup row prints upgrade
-and rollback guidance when concurrent Loader ordering allows it, but that
-friendly notice is best-effort rather than a startup-order guarantee. If you
-keep DSH 0.1.1, use the 0.3 TUI line; if you keep the alpha.2/alpha.3
-baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`; if you keep the
-alpha.4/alpha.5 baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.2`. The stable
-installation path is documented above under “Install into a DSH profile”; if
-you need to keep the legacy DSH runtime, use this compatibility recovery path:
-
-```sh
-npm install -g @deepseek-ai/dsh@0.1.1-rc.2
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
-dsh --profile pi-tui
-```
+| `0.4.5` (published `@latest`) | `dsh-v0.1.5-rc.1`, `dsh-v0.1.5-rc.2` | Current stable line; rc.1 minimum, rc.2 compatible |
+| Current `next` npm line (this checkout; version `0.4.5`) | `dsh-v0.1.5-rc.1`, `dsh-v0.1.5-rc.2` | Current next line |
 
-The current 0.4 line declares `>=0.1.2-rc.1`; each release validates
-its concrete DSH family. `npm install -g` is only for installing DSH itself; to
-install dsh-pi-tui into a DSH profile, you must use the `dsh plugin` command.
+Do not mix the stable and `next` lines. The current `next` checkout declares
+the published `0.1.5-rc.1` npm floor; older runtimes fail at the normal
+incompatible-runtime boundary. The startup notice is best-effort rather than a
+Loader startup-order guarantee. See the [full historical compatibility matrix](docs/dsh-compatibility.md)
+for official-tag pairings and fallback commands, and see the [latest `next`
+README](https://github.com/XMoon/dsh-pi-tui/blob/next/README.md) for the current
+integration status.
 
 New agent sessions use the official roster's selected preset id. A custom DSH
 preset literally named `code` is valid and remains `code` when it exists in the
-current roster. Old persisted `code` defaults/session values fall back to `ptc`
-only after the roster proves that no custom `code` preset exists.
+current roster. DSH V3 migration owns historical session `code -> ptc`
+conversion, while the current projection preserves a legal custom `code`. Only
+an omitted legacy settings default `code` falls back to `ptc` after the roster
+proves that no custom `code` preset exists.
 
 ### Profile management
 
@@ -136,7 +134,8 @@ Supports persisted DSH Sessions, including:
 * Forking
 * Rewind
 * Session lineage
-* Transcript export
+* `/export` — full Session archive (descendants + attachments) saved to a Client-local directory
+* `/transcript` — readable Markdown transcript saved to a Client-local directory
 
 Use:
 
@@ -144,6 +143,8 @@ Use:
 /sessions
 /fork
 /rewind
+/export
+/transcript
 ```
 
 When the Agent is idle and the editor is empty, pressing `Esc` twice quickly also opens Rewind.
@@ -234,7 +235,7 @@ Typing `@` opens workspace file search and completion:
 @"path with spaces/file.ts"
 ```
 
-`/image <path>` also completes files and directories; paths with spaces, quotes, or Windows separators preserve the input dialect, and directories can be expanded further.
+`/attach <path>` is the unified Client-local image/file intake; `/image <path>` keeps its image-only compatibility semantics. Both complete files and directories; paths with spaces, quotes, or Windows separators preserve the input dialect, and directories can be expanded further.
 
 Resolvable relative paths are canonicalized before submission.
 
@@ -294,7 +295,7 @@ For the full `/footer` workflow, Custom Text / Command items, YAML reference, se
 | Key           | Action                                              |
 | ------------- | --------------------------------------------------- |
 | `Enter`       | Submit input                                        |
-| `Ctrl+Enter`  | Queue the draft while the agent is busy (the opposite of Enter while busy) |
+| `Ctrl+Enter`  | Submit with the OPPOSITE busy behavior (steers by default; queues when `busyEnter=steer`) |
 | `Shift+Enter` | Insert newline                                      |
 | `Esc`         | Cancel current interaction / interrupt running work |
 | `Esc Esc`     | Open Rewind while idle                              |
@@ -551,22 +552,34 @@ dsh --profile pi-tui-dev
 
 ## DSH compatibility and validation
 
-This section contains Source Mode and CI validation details only; ordinary users do not need Source Mode to install the TUI.
+This section contains DSH compatibility and CI validation details only; ordinary users do not need them to install the TUI.
 
-### Source Mode (validation only)
+### npm mode (current `next`)
 
-Source Mode is the validation-only distribution selected by the tracked policy for `next` CI and available for local compatibility checks. It reads the full commit pin in `test/compat/dsh-source.json`, builds the official DSH tarball family, installs it through temporary pnpm overrides, and removes the temporary state afterward. Do not write DSH source paths, `file:` dependencies, or workspace symlinks into a published package.
+The current `next` line is npm mode: it targets the published
+`dsh-v0.1.5-rc.1` family declared by this checkout's `package.json` and
+resolved by its frozen lockfile. The isolated npm driver installs that exact
+family from the public registry and exercises the TUI build/test/package path:
 
 ```sh
-pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
 pnpm compat:dsh:npm
 ```
 
+### Source Mode (validation only)
+
+Source Mode is the validation-only distribution for an unpublished DSH
+checkout, available for local compatibility checks and explicit
+source-boundary work. It reads the full commit pin in
+`test/compat/dsh-source.json`, builds the official DSH tarball family, installs
+it through temporary pnpm overrides, and removes the temporary state afterward.
+Do not write DSH source paths, `file:` dependencies, or workspace symlinks into
+a published package.
+
 The published package already contains the Pi TUI fork required at runtime. No separate internal TUI package needs to be installed.
 
 ### CI validation policy
 
-CI follows the tracked `test/compat/dsh-mode.json` policy for pushes to `next` and pull requests targeting `next`; `main` and every tag use npm Mode. Both `next` lanes use `test/compat/dsh-source.json` for the current validated DSH target; Source Mode validates the complete official DSH tarball family, TUI presets, and the old-runtime boundary, while npm Mode runs the frozen registry lane. The published `pi2dsh` ecosystem check is explicitly marked skipped for an unpublished source family. See [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md) for the full workflow.
+CI follows the tracked `test/compat/dsh-mode.json` policy for pushes to `next` and pull requests targeting `next`; `main` and every tag use npm Mode. Source Mode reads the source target from `test/compat/dsh-source.json` and validates the complete official DSH tarball family, TUI presets, and the old-runtime boundary; npm Mode uses the DSH version declared by the checkout's `package.json` and frozen lockfile to run the registry lane. The published `pi2dsh` ecosystem check is explicitly marked skipped for an unpublished source family. See [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md) for the full workflow.
 
 ## Repository layout
 

package/README.md

@@ -18,20 +18,31 @@
 稳定版是普通用户的推荐渠道。请先安装 DSH，再将 TUI 添加到 `pi-tui` profile：
 
 ```sh
-npm install -g @deepseek-ai/dsh@0.1.2-rc.1
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@latest
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
 
-### Preview / next
+### Next / npm 线（验证）
 
-预览版包含未发布的变更，仅在需要体验或验证预发布版本时使用：
+预览安装使用 DSH 的 `alpha` channel 与 TUI 的 `next` channel；安装 DSH
+时需要显式允许其原生安装脚本：
 
 ```sh
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@alpha
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
 dsh --profile pi-tui
 ```
 
+隔离的 npm 驱动仍按本 checkout 声明的精确 DSH 版本运行，并执行完整的
+build/test/package 路径：
+
+```sh
+pnpm compat:dsh:npm
+```
+
+具体的稳定版最低版本、next 兼容范围和回退路径见[兼容性文档](docs/dsh-compatibility.md)。
+
 ### 环境要求
 
 * DeepSeek Harness
@@ -39,36 +50,21 @@ dsh --profile pi-tui
 
 ### DSH 与 TUI 版本对应（重要）
 
-| TUI 包版本 | 对应 DSH 版本 | 说明 |
+| TUI 包版本 | 对应的官方 DSH tags | 说明 |
 |---|---|---|
-| `0.4.1`（`@latest`） | `>=0.1.2-rc.1` | 当前稳定版；按 0.1.2-rc.1 family 验证 |
-| `0.4.x-alpha`（`@next`） | `>=0.1.2-rc.1` | 后续预发布线；按每个发布版本的具体 DSH family 验证 |
-| `0.4.0-alpha.2`（已发布） | `>=0.1.2-alpha.4` | 上一条 0.4 预发布线；其发布版本按 alpha.4/alpha.5 family 验证 |
-| `0.4.0-alpha.1`（已发布） | `>=0.1.2-alpha.2` | 更早的 0.4 预发布线；接受 alpha.2/alpha.3 运行时 |
-| `0.3.x`（`@0.3`） | `0.1.1-rc.2` | 旧运行时兼容线 |
-
-不要把两条线混装：DSH 0.1.1 不在 0.4 的 peer 支持范围内，运行时会在
-正常的不兼容边界以非零状态失败。启动行会在 Loader 并发挂载顺序允许时打印
-升级和回退提示，但该友好提示是 best-effort，不是启动顺序保证；保留 DSH
-0.1.1 时请使用 0.3，保留 alpha.2/alpha.3 时请使用
-`@xmoon76/dsh-pi-tui@0.4.0-alpha.1`，保留 alpha.4/alpha.5 时请使用
-`@xmoon76/dsh-pi-tui@0.4.0-alpha.2`。稳定版的安装方式已在上方“安装到 DSH
-Profile”中给出；如果需要保留旧 DSH，请使用下面的兼容恢复路径：
-
-```sh
-npm install -g @deepseek-ai/dsh@0.1.1-rc.2
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
-dsh --profile pi-tui
-```
+| `0.4.5`（已发布 `@latest`） | `dsh-v0.1.5-rc.1`、`dsh-v0.1.5-rc.2` | 当前稳定版；最低 rc.1，兼容 rc.2 |
+| 当前 `next` npm 线（本 checkout；版本 `0.4.5`） | `dsh-v0.1.5-rc.1`、`dsh-v0.1.5-rc.2` | 当前 next 线 |
 
-`0.4` 当前线的声明支持范围是 `>=0.1.2-rc.1`；每个发布版本都会验证
-具体的 DSH family。`npm install -g` 仅用于安装 DSH 本身；要将 dsh-pi-tui
-安装进 DSH profile，必须使用 `dsh plugin` 命令。
+不要把稳定线与 `next` 线混装。当前 `next` checkout 的 peer floor 是
+`>=0.1.5-rc.1`，旧 runtime 会在正常的不兼容边界以非零状态失败。完整的
+历史兼容矩阵和 fallback 命令见 [兼容性文档](docs/dsh-compatibility.md)；
+要查看 next 的最新集成状态，请看 [next 分支 README](https://github.com/XMoon/dsh-pi-tui/blob/next/README.md)。
 
 新的 Agent preset 使用当前 roster 中选定的 id。DSH 允许合法的自定义
 `code` preset；只要当前 roster 存在它，显式输入和持久化状态都会保留 `code`。
-旧数据中省略请求的 `code` default/session 值只有在确认 roster 不含 `code` 后
-才会回退到 `ptc`。
+DSH V3 migration 负责历史 session header/selection 的 `code -> ptc` 转换；
+当前 projection 会原样保留合法的自定义 `code`。只有省略请求的 legacy
+settings default `code` 才会在确认 roster 不含 `code` 后回退到 `ptc`。
 
 ### Profile management
 
@@ -132,7 +128,8 @@ dsh --profile pi-tui --session <session-id>
 * Fork
 * Rewind
 * Session lineage
-* Transcript 导出
+* `/export` — 完整 Session 归档(含子代理与附件),保存到 Client 本地目录
+* `/transcript` — 可读 Markdown 对话记录,保存到 Client 本地目录
 
 使用：
 
@@ -140,6 +137,8 @@ dsh --profile pi-tui --session <session-id>
 /sessions
 /fork
 /rewind
+/export
+/transcript
 ```
 
 空闲且编辑器为空时也可以快速按两次 `Esc` 打开 Rewind。
@@ -223,7 +222,7 @@ Shell 卡片默认只显示有限的输出预览，`Ctrl+O` 可以展开完整
 @"path with spaces/file.ts"
 ```
 
-`/image <path>` 也支持文件与目录补全；带空格、引号或 Windows 分隔符的路径会保留输入方言，目录可以继续展开。
+`/attach <path>` 是统一的 Client-local 图片/文件入口；`/image <path>` 保持图片专用兼容语义。两者都支持文件与目录补全；带空格、引号或 Windows 分隔符的路径会保留输入方言，目录可以继续展开。
 
 能够解析的相对路径会在提交时转换为明确的文件路径。
 
@@ -282,7 +281,7 @@ TUI 使用 DSH 提供的模型和设置服务。
 | 按键            | 功能                     |
 | ------------- | ---------------------- |
 | `Enter`       | 提交输入                   |
-| `Ctrl+Enter`  | Agent 忙碌时把草稿入队(与 Enter 相反) |
+| `Ctrl+Enter`  | 与 Enter 的忙碌行为相反(默认 steer,`busyEnter=steer` 时入队) |
 | `Shift+Enter` | 换行                     |
 | `Esc`         | 取消当前交互 / 中断运行          |
 | `Esc Esc`     | 空闲时打开 Rewind           |
@@ -529,22 +528,31 @@ dsh --profile pi-tui-dev
 
 ## DSH 兼容性与验证
 
-以下内容仅介绍 Source Mode 和 CI 验证细节；普通用户无需使用 Source Mode 安装 TUI。
+以下内容仅介绍 DSH 兼容性与 CI 验证细节；普通用户无需了解即可安装 TUI。
 
-### Source Mode（仅验证）
+### npm 模式（当前 `next`）
 
-Source Mode 是 `next` CI 按跟踪策略选用的、并可用于本地兼容性检查的验证专用 distribution。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
+当前 `next` 线是 npm 模式：以本 checkout 的 `package.json` 声明、冻结
+lockfile 解析的已发布 `dsh-v0.1.5-rc.1` family 为兼容目标。隔离的 npm
+驱动从公共 registry 安装该精确 family，并跑完整 build/test/package 路径：
 
 ```sh
-pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
 pnpm compat:dsh:npm
 ```
 
+### Source Mode（仅验证）
+
+Source Mode 是面向未发布 DSH checkout 的验证专用 distribution，用于本地
+兼容性检查与显式的 source 边界工作。它从 `test/compat/dsh-source.json` 的
+完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，
+并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace
+symlink 写入发布 package。
+
 安装包已经包含运行所需的 Pi TUI fork，不需要额外安装内部的 TUI package。
 
 ### CI 验证策略
 
-CI 对 push 到 `next` 以及目标为 `next` 的 PR 遵循跟踪的 `test/compat/dsh-mode.json` 策略；`main` 和所有 tag 使用 npm Mode。`next` 的两种 lane 都从 `test/compat/dsh-source.json` 读取当前 validated DSH target；Source Mode 会验证完整的官方 DSH tarball family、TUI 预设和旧 runtime 边界，npm Mode 则运行冻结的 registry lane。对于尚未发布的 source family，已发布 `pi2dsh` 的生态检查会明确标记为 skipped。详细流程见 [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md)。
+CI 对 push 到 `next` 以及目标为 `next` 的 PR 遵循跟踪的 `test/compat/dsh-mode.json` 策略；`main` 和所有 tag 使用 npm Mode。Source Mode 从 `test/compat/dsh-source.json` 读取 source target 并验证完整的官方 DSH tarball family、TUI 预设和旧 runtime 边界；npm Mode 则使用 checkout 的 `package.json`/冻结 lockfile 中声明的 DSH 版本运行 registry lane。对于尚未发布的 source family，已发布 `pi2dsh` 的生态检查会明确标记为 skipped。详细流程见 [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md)。
 
 ## 项目结构
 

package/cordis.patch.yml

@@ -42,11 +42,12 @@
     - id: authorization
       name: '@deepseek-ai/dsh-authorization'
 
-    # Consume DSH 0.1.2's official shipped presets directly. The upstream
+    # Official shipped presets are the composition authority. The upstream
     # service defaults includeShippedRoot/includeUserRoot to true, so this
     # bundle deliberately owns no duplicate standard/ptc/minimal/cordis root.
-    # The legacy persisted id `code` is normalized at the data boundary to
-    # `ptc`; it is not another preset row.
+    # DSH's V2→V3 format migration owns historical session preset conversion;
+    # the settings/default compatibility shim is kept separately at the TUI
+    # request boundary and does not add another preset row.
     - id: agent-presets
       name: '@deepseek-ai/dsh-agent-presets'
       config:
@@ -110,9 +111,6 @@
 - id: tool-fs-search
   disabled: true
 
-- id: tool-str-replace-editor
-  disabled: true
-
 - id: skill-filesystem
   disabled: true
 

package/dist/builtins.mjs

@@ -1,4 +1,4 @@
-import { H as PI_TUI_EXTENSIONS_SERVICE, L as dshVersion } from "./src-CeGK2mHo.mjs";
+import { W as PI_TUI_EXTENSIONS_SERVICE, z as dshVersion } from "./src-B65x1oP2.mjs";
 import { TUI_STARTUP_SERVICE } from "./startup.mjs";
 import { readFileSync } from "node:fs";
 import { join } from "node:path";

package/dist/extension/advanced.d.mts

@@ -1,4 +1,4 @@
-import { D as PiTuiApiInfo, E as NormalizedKey, _ as ExtensionTier, h as EditorSnapshot, ot as TuiOverlayOptions, v as ExtensionView } from "../public-types-_pe9ZH00.mjs";
+import { D as PiTuiApiInfo, E as NormalizedKey, _ as ExtensionTier, h as EditorSnapshot, ot as TuiOverlayOptions, v as ExtensionView } from "../public-types-YbB5Rhku.mjs";
 
 //#region src/extension/advanced-types.d.ts
 /** API level of the advanced tier. Bumped only on advanced breaking changes. */
@@ -8,6 +8,15 @@ declare const ADVANCED_API_LEVEL: 1;
  * sees. The Host has already decoded the terminal protocol (legacy + Kitty
  * CSI-u + modifyOtherKeys encodings, bracketed paste, key release/repeat
  * filtering), so an advanced plugin behaves identically on every terminal.
+ *
+ * EXPLICIT NON-EXPANSION (v0.85.1 mouse parity audit): this contract
+ * deliberately does NOT carry pointer/mouse events. Advanced interactive
+ * custom surfaces remain keyboard-input surfaces by contract; no raw
+ * mouse bytes are exposed and no API-level mouse feature is added here.
+ * A pointer-capable Advanced plugin API would require normalized mouse
+ * event design, capture ordering, docs, packed declaration checks and
+ * plugin migration semantics — a dedicated follow-up design, not a
+ * side effect of Host v0.85.1 integration.
  */
 type AdvancedInputEvent = /** One key press, normalized to the semantic identity. */{
   readonly kind: 'key';

package/dist/extension/unstable.d.mts

@@ -1,4 +1,4 @@
-import { D as PiTuiApiInfo, _ as ExtensionTier, ot as TuiOverlayOptions } from "../public-types-_pe9ZH00.mjs";
+import { D as PiTuiApiInfo, _ as ExtensionTier, ot as TuiOverlayOptions } from "../public-types-YbB5Rhku.mjs";
 
 //#region src/extension/unstable-types.d.ts
 /** API level of the unstable tier. Bumped only on unstable breaking changes. */

package/dist/extensions.d.mts

@@ -1,4 +1,4 @@
-import { $ as TuiKeybindingContribution, A as PiTuiSlotSemantic, B as TextView, C as InputWidget, D as PiTuiApiInfo, E as NormalizedKey, F as SpacerView, G as TuiAutocompleteQuery, H as TuiAction, I as StackView, J as TuiColorPalette, K as TuiAutocompleteRegistryView, L as StyledSpan, M as RegistrationSpec, N as RowsView, O as PiTuiCapability, P as SessionSnapshot, Q as TuiCommandHandle, R as SurfaceSnapshot, S as HeaderBadge, T as MessagePresentationSnapshot, U as TuiAutocompleteItem, V as ToolPresentationSnapshot, W as TuiAutocompleteProvider, X as TuiCommandBridgeView, Y as TuiCommandBridgeSnapshot, Z as TuiCommandContribution, _t as TuiThemeRegistrySnapshot, a as ContributionHealth, at as TuiOverlayHandle, b as FooterSegment, bt as describeKey, c as DockItem, ct as TuiRendererRegistrySnapshot, d as EditorHost, dt as TuiSettingHandle, et as TuiKeybindingHandle, f as EditorHostAction, ft as TuiSettingsRegistrySnapshot, g as ExtensionEditor, gt as TuiThemeHandle, h as EditorSnapshot, ht as TuiThemeContribution, i as AutocompleteProviderContribution, it as TuiMessageRendererContribution, j as RegistrationHandle, k as PiTuiSlotName, l as EditorContribution, lt as TuiRendererRegistryView, m as EditorInputEvent, mt as TuiSizeValue, n as ActivitySnapshot, nt as TuiKeybindingRegistryView, o as ContributionRecord, ot as TuiOverlayOptions, p as EditorHostActionResult, pt as TuiSettingsRegistryView, q as TuiAutocompleteSuggestions, r as AutocompleteHandle, rt as TuiLocalCommandHandler, s as ContributionState, st as TuiRendererHandle, t as API_VERSION, tt as TuiKeybindingRegistrySnapshot, u as EditorHandle, ut as TuiSettingContribution, v as ExtensionView, vt as TuiThemeRegistryView, w as MarkdownView, x as FrameView, y as FooterItemContribution, yt as TuiToolRendererContribution, z as SurfaceStateValues } from "./public-types-_pe9ZH00.mjs";
+import { $ as TuiKeybindingContribution, A as PiTuiSlotSemantic, B as TextView, C as InputWidget, D as PiTuiApiInfo, E as NormalizedKey, F as SpacerView, G as TuiAutocompleteQuery, H as TuiAction, I as StackView, J as TuiColorPalette, K as TuiAutocompleteRegistryView, L as StyledSpan, M as RegistrationSpec, N as RowsView, O as PiTuiCapability, P as SessionSnapshot, Q as TuiCommandHandle, R as SurfaceSnapshot, S as HeaderBadge, T as MessagePresentationSnapshot, U as TuiAutocompleteItem, V as ToolPresentationSnapshot, W as TuiAutocompleteProvider, X as TuiCommandBridgeView, Y as TuiCommandBridgeSnapshot, Z as TuiCommandContribution, _t as TuiThemeRegistrySnapshot, a as ContributionHealth, at as TuiOverlayHandle, b as FooterSegment, bt as describeKey, c as DockItem, ct as TuiRendererRegistrySnapshot, d as EditorHost, dt as TuiSettingHandle, et as TuiKeybindingHandle, f as EditorHostAction, ft as TuiSettingsRegistrySnapshot, g as ExtensionEditor, gt as TuiThemeHandle, h as EditorSnapshot, ht as TuiThemeContribution, i as AutocompleteProviderContribution, it as TuiMessageRendererContribution, j as RegistrationHandle, k as PiTuiSlotName, l as EditorContribution, lt as TuiRendererRegistryView, m as EditorInputEvent, mt as TuiSizeValue, n as ActivitySnapshot, nt as TuiKeybindingRegistryView, o as ContributionRecord, ot as TuiOverlayOptions, p as EditorHostActionResult, pt as TuiSettingsRegistryView, q as TuiAutocompleteSuggestions, r as AutocompleteHandle, rt as TuiLocalCommandHandler, s as ContributionState, st as TuiRendererHandle, t as API_VERSION, tt as TuiKeybindingRegistrySnapshot, u as EditorHandle, ut as TuiSettingContribution, v as ExtensionView, vt as TuiThemeRegistryView, w as MarkdownView, x as FrameView, y as FooterItemContribution, yt as TuiToolRendererContribution, z as SurfaceStateValues } from "./public-types-YbB5Rhku.mjs";
 import { Context, Service } from "@deepseek-ai/cordis";
 
 //#region src/extension/service.d.ts
@@ -26,9 +26,12 @@ interface PiTuiExtensionService {
    */
   subscribeState(listener: (state: SurfaceStateValues) => void): () => void;
   /**
-   * Register a TUI command contribution (M5): execution ownership metadata
-   * over an existing command. The bridge does NOT execute — actual
-   * execution stays in the commands service. Owned by the calling fiber.
+   * Register a CLIENT-OWNED command contribution (M5): a slash name whose
+   * behavior lives entirely on the client (the DSH client command
+   * contribution shape). It joins the `/` menu merged with the host catalog
+   * and the runner executes its own `handler` locally; a name that is also a
+   * host command fails loud at candidate synthesis and never shadows it.
+   * Owned by the calling fiber.
    * @param contribution - the command contribution.
    */
   registerCommand(contribution: TuiCommandContribution): TuiCommandHandle;

package/dist/extensions.mjs

@@ -1,3 +1,3 @@
-import { B as inject, H as PI_TUI_EXTENSIONS_SERVICE, U as API_VERSION, V as name, W as describeKey, z as apply } from "./src-CeGK2mHo.mjs";
+import { G as API_VERSION, H as inject, K as describeKey, U as name, V as apply, W as PI_TUI_EXTENSIONS_SERVICE } from "./src-B65x1oP2.mjs";
 import "./startup.mjs";
 export { API_VERSION, PI_TUI_EXTENSIONS_SERVICE, apply, describeKey, inject, name };