@xmoon76/dsh-pi-tui 0.4.7-alpha.2 → 0.4.9

package/README.en.md

@@ -54,23 +54,28 @@ next compatibility range, and fallback paths.
 
 | TUI package line | Official DSH tags for the pairing | Notes |
 |---|---|---|
-| `0.4.6` (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.7-alpha.2`) | `dsh-v0.1.6-alpha.2` | Current next line |
-
-Do not mix the stable and `next` lines. The current `next` checkout declares
-the published `0.1.6-alpha.2` 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`
+| `0.4.9` (stable / `@latest`) | `dsh-v0.1.7-rc.2` | Current stable line; 0.1.7-rc.2 minimum |
+| `0.4.8` (stable, previous) | `dsh-v0.1.7-rc.1` | Previous stable; the compatible TUI for a 0.1.7-rc.1 runtime |
+| `0.4.6` (stable, previous) | `dsh-v0.1.5-rc.1`, `dsh-v0.1.5-rc.2` | Previous stable; the compatible TUI for a 0.1.5 runtime |
+| `0.4.7-alpha.2` (next, previous) | `dsh-v0.1.6-alpha.2` | Previous next line; the compatible TUI for a 0.1.6-alpha.2 runtime |
+
+Do not mix the stable and `@next` prerelease lines. The `0.4.9` line unifies its
+whole DSH peer floor at `>=0.1.7-rc.2` (the rc.2 preset registry peers
+`dsh-agent` exactly, so a wider legacy floor no longer satisfies a standalone
+tarball install); older runtimes fail at the normal incompatible-runtime
+boundary, so install the paired TUI line from the table above. 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. 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.
+conversion, while the current projection preserves a legal custom `code`. An
+omitted legacy settings default is never aliased: with no matching declaration
+in the current roster it is simply an invalid preference.
 
 ### Profile management
 
@@ -119,11 +124,15 @@ dsh --profile pi-tui --session <session-id>
 
 `Ctrl+O` controls Tool and System details and expands/collapses long user prompts in regular mode and in fullscreen outside Focus — in fullscreen Focus it bulk-expands the recent Thought roots or collapses them all, while long user prompts are expanded by clicking the marker (or by a search hit) and collapsed with `Ctrl+O`. `Alt+T` controls Thinking separately.
 
-### Focus Mode
+### Conversation display
 
-`/focus` groups the current turn's Thinking, Tool Calls, and intermediate replies into a live Thought block.
+`/display focus` groups the current turn's Thinking, Tool Calls, and intermediate replies into a live Thought block; `/display full` restores the normal Transcript projection. `/focus` remains available as a compatibility command. The Compact preset is reserved and `/display compact` is rejected until its projection ships.
 
-The full process can still be expanded when needed. In fullscreen Focus, Thought roots can be expanded/collapsed in bulk or opened with an individual card click, and the viewport survives switches and resizes. Disabling Focus restores the normal Transcript projection. Focus only changes presentation; it does not modify Session events.
+The full process can still be expanded when needed. In fullscreen Focus, Thought roots can be expanded/collapsed in bulk or opened with an individual card click, and the viewport survives switches and resizes. Display presets only change presentation; they do not modify Session events.
+
+### Communication policy
+
+`/settings` exposes two independent communication controls. **Progress updates** owns the mid-turn update cadence: `milestones` (default) posts a brief update only when a substantial phase completes, the direction materially changes, or required user input blocks progress — never for a freshly discovered partial finding; `frequent` keeps the user actively informed through longer multi-step work; `off` suppresses progress narration entirely. **Response style** owns the visible answer's density: `default` adds no extra guidance, `concise` is compact and result-first, `explanatory` adds rationale, architecture, and tradeoffs. Changes apply on the next prompt assembly without restarting the agent and are saved across sessions. Focus is a surface capability, not a third preference: while Focus is active the progress section is simply ineffective (progress-only intermediate messages are not generated) and the saved cadence is untouched; the response style stays active in Focus.
 
 ### Sessions
 
@@ -166,10 +175,31 @@ History results include the Prompt, working directory, timestamp, and Session in
 
 Regular `↑` / `↓` history recall is still available for recent input.
 
-### Subagents and background tasks
-
-`/tasks` opens the full Task Center for all background work in the current
-Session; the Footer's `↓` opens the lightweight Quick Tasks view for running work.
+### Subagents and the Task Center
+
+`/tasks` opens the full Task Center, showing the work the current Session's
+Job Registry / Subagent catalog still tracks; the Footer's `↓` opens the
+lightweight Quick Tasks view for the current active work. Selecting a Job
+opens a detail with the official non-consuming live
+output preview (status, progress and the retained output tail); it never consumes
+the model's `job_output` cursor and never becomes session history.
+
+Task Center is a live tracked/control projection, not an execution-history
+list. `ACTIVE` / `TRACKED` are presentation scopes: `ACTIVE` shows only the
+currently active items, `TRACKED` shows everything the current authority
+still lists. DSH `0.1.7` temporarily registers a Job while an ordinary
+foreground `bash` / `pwsh` command runs, so it can be observed and stopped
+from the Task Center; if the command finishes inside the foreground wait,
+DSH removes that temporary record and the final result stays in the
+Transcript's tool card. Explicit `run_in_background: true` jobs (and jobs
+promoted to the background after a foreground timeout) remain visible in
+`TRACKED` after completion as long as the Job Registry keeps their record.
+
+`/plugins` opens the active profile's Plugin Manager: installed bundles and
+plugins are grouped into Current TUI / TUI Extensions / DSH Plugins, with
+enable/disable, remove and install; the `dsh-pi-tui` bundle currently providing
+the surface is read-only and cannot be disabled or removed from its own screen.
+The `Plugins  Manage…` row in `/settings` opens the same surface on demand.
 
 Subagents are shown using their complete lineage, including nested descendants:
 
@@ -186,14 +216,14 @@ The browser distinguishes:
 * `one-shot`
 * running / inactive
 * nested descendants
-* background Jobs
+* Job Registry rows (including running foreground shell work)
 
 The Footer's `↓` opens Quick Tasks as a lightweight browsing view: it only
 supports arrow navigation, left/right expand/collapse, `Tab` type cycling,
 `Enter` open, and `Esc` close. The bottom “Open Task Center” row opens the full
 Task Center.
 
-The full Task Center additionally offers `A` to toggle Active / All, `/` search,
+The full Task Center additionally offers `A` to toggle Active / Tracked, `/` search,
 `Tab` / `Shift+Tab` to cycle types in both directions, `S` to stop the selected
 task after confirmation, and `R` to refresh/retry. Quick Tasks consumes only the
 whitelist above; every other keystroke is a no-op that never enters search, stop
@@ -328,20 +358,22 @@ Use `/help` inside the TUI for the current command and keybinding list. The tabl
 Host shortcuts are semantic actions (`app.*`) resolved through a
 context-aware keymap — the UI (footer hints, `/help`, `/keybindings`)
 always shows the EFFECTIVE keys, so a remap updates every hint. Configure
-them in the `dsh-pi-tui` settings namespace; apply with `/keybindings
-reload` (explicit — a settings edit takes effect after the reload, no
-restart):
+them through the in-TUI `/keybindings` panel (it writes the `keybindings`
+field of the `tui-app` plugin's profile-owned configuration — since DSH
+0.1.7 TUI preferences live on the profile Config, not the retired
+`dsh-pi-tui` settings namespace); apply with `/keybindings reload`
+(explicit — a configuration edit takes effect after the reload, no
+restart). Field shape:
 
 ```yaml
-dsh-pi-tui:
-  keybindings:
-    app.input.steer: ctrl+s          # one key
-    app.permission.cycle: [shift+tab, ctrl+shift+p]   # several keys
-    app.history.search: ctrl+r
-    app.transcript.toggleThinking: false   # disable the action's keys
-    leader: ctrl+x                    # M6: leader sequences
-    bindings:
-      app.tasks.open: <leader>t
+keybindings:
+  app.input.steer: ctrl+s          # one key
+  app.permission.cycle: [shift+tab, ctrl+shift+p]   # several keys
+  app.history.search: ctrl+r
+  app.transcript.toggleThinking: false   # disable the action's keys
+  leader: ctrl+x                    # M6: leader sequences
+  bindings:
+    app.tasks.open: <leader>t
 ```
 
 - A plain printable key can never be bound to a Host action (it would
@@ -562,9 +594,9 @@ This section contains DSH compatibility and CI validation details only; ordinary
 
 ### npm mode (current `next`)
 
-The current `next` line is npm mode: it targets the published
-`dsh-v0.1.6-alpha.2` family declared by this checkout's `package.json` and
-resolved by its frozen lockfile. The isolated npm driver installs that exact
+The current compatibility-train line is npm mode: it targets the published
+`dsh-v0.1.7-rc.2` family declared by this checkout's `package.json` and
+resolved by its lockfile. The isolated npm driver installs that exact
 family from the public registry and exercises the TUI build/test/package path:
 
 ```sh

package/README.md

@@ -52,19 +52,23 @@ pnpm compat:dsh:npm
 
 | TUI 包版本 | 对应的官方 DSH tags | 说明 |
 |---|---|---|
-| `0.4.6`（已发布 `@latest`） | `dsh-v0.1.5-rc.1`、`dsh-v0.1.5-rc.2` | 当前稳定版；最低 rc.1，兼容 rc.2 |
-| 当前 `next` npm 线（本 checkout；版本 `0.4.7-alpha.2`） | `dsh-v0.1.6-alpha.2` | 当前 next 线 |
-
-不要把稳定线与 `next` 线混装。当前 `next` checkout 的 peer floor 是
-`>=0.1.6-alpha.2`，旧 runtime 会在正常的不兼容边界以非零状态失败。完整的
-历史兼容矩阵和 fallback 命令见 [兼容性文档](docs/dsh-compatibility.md)；
-要查看 next 的最新集成状态，请看 [next 分支 README](https://github.com/XMoon/dsh-pi-tui/blob/next/README.md)。
+| `0.4.9`（stable / `@latest`） | `dsh-v0.1.7-rc.2` | 当前稳定版；最低 0.1.7-rc.2 |
+| `0.4.8`（stable，历史） | `dsh-v0.1.7-rc.1` | 上一稳定版；0.1.7-rc.1 runtime 的兼容 TUI |
+| `0.4.6`（stable，历史） | `dsh-v0.1.5-rc.1`、`dsh-v0.1.5-rc.2` | 上一稳定版；0.1.5 runtime 的兼容 TUI |
+| `0.4.7-alpha.2`（next，历史） | `dsh-v0.1.6-alpha.2` | 上一条 next 线；0.1.6-alpha.2 runtime 的兼容 TUI |
+
+不要把稳定线与 `@next` 预发布线混装。`0.4.9` 的整个 DSH peer floor 统一为
+`>=0.1.7-rc.2`（rc.2 的 preset registry 精确 peer `dsh-agent`，更宽的旧
+floor 已无法满足独立 tarball 安装）；旧 runtime 会在正常的不兼容边界以非零状态失败，
+请按上表安装配对的 TUI 线。完整的历史兼容矩阵和 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`。
 DSH V3 migration 负责历史 session header/selection 的 `code -> ptc` 转换；
-当前 projection 会原样保留合法的自定义 `code`。只有省略请求的 legacy
-settings default `code` 才会在确认 roster 不含 `code` 后回退到 `ptc`。
+当前 projection 会原样保留合法的自定义 `code`。省略请求的 legacy settings
+default 不再做任何别名映射：当前 roster 没有声明就是无效偏好。
 
 ### Profile management
 
@@ -113,11 +117,15 @@ dsh --profile pi-tui --session <session-id>
 
 `Ctrl+O` 控制工具和系统详情，并在普通模式与全屏非 Focus 下展开/收起超长用户 Prompt;全屏 Focus 下它整体展开最近几个 Thought root 或全部收起，超长用户 Prompt 改用点击提示行（或搜索命中）展开、`Ctrl+O` 收回。`Alt+T` 单独控制 Thinking。
 
-### Focus Mode
+### Conversation display
+
+`/display focus` 将运行中的 Thinking、Tool Call 和中间回复聚合为一个实时更新的 Thought 区块；`/display full` 恢复普通 Transcript 展示。`/focus` 仍作为兼容命令保留。Compact 预设尚未开放，`/display compact` 会明确拒绝。
+
+需要查看过程时可以展开，关闭 Focus 后恢复普通 Transcript 展示。全屏 Focus 中可以按 Thought root 批量展开/收起,也可以单独点击卡片;切换或缩放时会保留 viewport。展示预设只影响界面投影，不修改 Session 中保存的事件。
 
-`/focus` 可以把运行中的 Thinking、Tool Call 和中间回复聚合为一个实时更新的 Thought 区块。
+### 沟通策略
 
-需要查看过程时可以展开，关闭 Focus 后恢复普通 Transcript 展示。全屏 Focus 中可以按 Thought root 批量展开/收起,也可以单独点击卡片;切换或缩放时会保留 viewport。Focus 只影响界面投影，不修改 Session 中保存的事件。
+`/settings` 提供两个独立的沟通设置。**Progress updates** 控制 Agent 工作时的中途更新节奏：`milestones`（默认）只在完整的阶段结束、方向实质变化或需要用户输入时简短汇报，不为「刚发现一个局部结论」而打断；`frequent` 在较长的多步工作中持续带用户跟进；`off` 完全不做过程叙述。**Response style** 控制可见回复的密度：`default` 不附加表达指导，`concise` 紧凑且结果优先，`explanatory` 补充原理、架构与取舍。两项切换都在下一次提示词组装时生效，无需重启 Agent，并跨会话保存。Focus 是展示能力而非第三个偏好：进入 Focus 时进度更新节只是暂时失效（不生成只含进度的中间消息），保存的节奏偏好不变，Response style 在 Focus 下仍然生效。
 
 ### Session
 
@@ -160,9 +168,13 @@ Rewind 会从选中的历史 User Turn 创建新的 Child Session，并把对应
 
 普通的 `↑` / `↓` 仍用于快速浏览最近输入。
 
-### Subagent 与后台任务
+### Subagent 与 Task Center
+
+`/tasks` 打开完整 Task Center，显示当前 Session 中仍由 Job Registry / Subagent catalog 跟踪的工作；Footer 的 `↓` 打开轻量 Quick Tasks，只看当前活动（active）工作。选中 Job 后，详情会显示官方非消耗式的实时输出预览（状态、进度与保留的输出尾部），不会消耗模型的 `job_output` 游标，也不写入会话历史。
+
+Task Center 的 `ACTIVE` / `TRACKED` 是展示范围：`ACTIVE` 只显示当前活动项，`TRACKED` 显示当前跟踪源（Job Registry / Subagent catalog）仍列出的全部项；`TRACKED` 不是 Session 执行历史。DSH `0.1.7` 会在普通前台 `bash` / `pwsh` 执行期间临时注册 Job，使其可以在 Task Center 中观察和停止；如果命令在前台等待内完成，DSH 会移除该临时记录，最终结果仍保留在 Transcript 的 tool card 中。显式 `run_in_background: true` 或被提升为后台的 Job 在完成后，只要 Job Registry 继续保留其记录，就仍可在 `TRACKED` 中查看。
 
-`/tasks` 打开完整 Task Center（当前 Session 的所有后台工作）；Footer 的 `↓` 直接打开轻量 Quick Tasks（只看正在运行的工作）。
+`/plugins` 打开当前 profile 的 Plugin Manager：按 Current TUI / TUI Extensions / DSH Plugins 分区查看已安装的 bundle 与插件，并执行启用/禁用、删除与安装；正在提供当前界面的 `dsh-pi-tui` 只读且不可从自身界面禁用或移除。`/settings` 中的 `Plugins  Manage…` 按需打开同一界面。
 
 Subagent 按完整 lineage 显示，包括嵌套创建的 descendant：
 
@@ -179,11 +191,11 @@ main
 * `one-shot`
 * running / inactive
 * nested descendant
-* 后台 Job
+* Job Registry 跟踪的 Job（含运行中的前台 shell）
 
 Footer `↓` 打开的 Quick Tasks 是轻量浏览视图，只提供方向键导航、左右展开/折叠、`Tab` 类型过滤、`Enter` 打开和 `Esc` 关闭。底部 “Open Task Center” 行可进入完整 Task Center。
 
-完整 Task Center 额外提供 `A` 切换 Active / All、`/` 搜索、`Tab` / `Shift+Tab` 双向切换类型、`S`（确认后）停止所选任务以及 `R` 刷新 / 重试。Quick Tasks 只消费上述白名单按键，其余输入一律 no-op，不会进入搜索、停止确认或任务管理状态，因此 `Esc` 始终一层关闭。
+完整 Task Center 额外提供 `A` 切换 Active / Tracked、`/` 搜索、`Tab` / `Shift+Tab` 双向切换类型、`S`（确认后）停止所选任务以及 `R` 刷新 / 重试。Quick Tasks 只消费上述白名单按键，其余输入一律 no-op，不会进入搜索、停止确认或任务管理状态，因此 `Esc` 始终一层关闭。
 
 已经结束的 one-shot Subagent 仍可以打开并查看持久化 Transcript。
 
@@ -310,20 +322,21 @@ TUI 使用 DSH 提供的模型和设置服务。
 
 Host 快捷键是语义 action(`app.*`),通过 context-aware keymap 解析——
 UI(页脚提示、`/help`、`/keybindings`)始终显示**生效**的按键,因此
-改键后所有提示自动更新。在 `dsh-pi-tui` settings 命名空间中配置,
-然后用 `/keybindings reload` 应用(显式 reload——改设置后执行 reload
-即生效,无需重启):
+改键后所有提示自动更新。配置入口是 TUI 里的 `/keybindings` 面板
+(写入 `tui-app` 插件的 profile 配置的 `keybindings` 字段——DSH 0.1.7
+起 TUI 偏好保存在 profile-owned Config,不再使用旧 `dsh-pi-tui`
+settings 命名空间);保存后用 `/keybindings reload` 应用(显式
+reload——配置变更后执行 reload 即生效,无需重启)。字段形状:
 
 ```yaml
-dsh-pi-tui:
-  keybindings:
-    app.input.steer: ctrl+s          # 单个按键
-    app.permission.cycle: [shift+tab, ctrl+shift+p]   # 多个按键
-    app.history.search: ctrl+r
-    app.transcript.toggleThinking: false   # 禁用该 action 的按键
-    leader: ctrl+x                    # M6:leader 序列
-    bindings:
-      app.tasks.open: <leader>t
+keybindings:
+  app.input.steer: ctrl+s          # 单个按键
+  app.permission.cycle: [shift+tab, ctrl+shift+p]   # 多个按键
+  app.history.search: ctrl+r
+  app.transcript.toggleThinking: false   # 禁用该 action 的按键
+  leader: ctrl+x                    # M6:leader 序列
+  bindings:
+    app.tasks.open: <leader>t
 ```
 
 - 普通可打印键永远不能绑定到 Host action(会吞掉输入);坏配置只是
@@ -535,8 +548,8 @@ dsh --profile pi-tui-dev
 
 ### npm 模式（当前 `next`）
 
-当前 `next` 线是 npm 模式：以本 checkout 的 `package.json` 声明、冻结
-lockfile 解析的已发布 `dsh-v0.1.6-alpha.2` family 为兼容目标。隔离的 npm
+当前兼容列车线是 npm 模式：以本 checkout 的 `package.json` 声明、
+lockfile 解析的已发布 `dsh-v0.1.7-rc.2` family 为兼容目标。隔离的 npm
 驱动从公共 registry 安装该精确 family，并跑完整 build/test/package 路径：
 
 ```sh

package/cordis.patch.yml

@@ -32,10 +32,25 @@
       # can fork. The row below is this bundle's own, so the dependency is
       # self-contained and a profile that disables it fails loud instead of
       # silently forking without workspace inheritance.
-      inject: [tuiStartup, piTuiExtensions, authorization, workspaceRegistry]
+      # `pluginManager` is injected for the P1-A Plugin Manager surface: the
+      # dsh-base layer already mounts it (disabled only without a profile),
+      # so this is an explicit lifecycle ordering dependency, never a second
+      # package-manager row.
+      inject: [tuiStartup, piTuiExtensions, authorization, workspaceRegistry, pluginManager, jobController]
       config:
         sessionId: ''
 
+    # One background Job's observation stream (P1-B): the official Host
+    # controller wraps `jobs.events` + `jobs.readAt()` into a
+    # NON-CONSUMING follow stream (never `jobs.read()`), so the selected Job
+    # detail can render a live retained-output tail without touching the
+    # model's `job_output` cursor or completion notices. The rc.1 web bundle
+    # mounts this same row; the dsh-base layer does not, so the TUI inserts
+    # it. This is NOT M3: same process, same Host Context, no Client Context,
+    # no Connection, no transport.
+    - id: job-controller
+      name: '@deepseek-ai/dsh-api-job-controller'
+
     # Host-owned workspace membership (`ctx.workspaceRegistry`): D2.4 Direct
     # fork mirrors the official Host rule (use the source's directly owning
     # workspace, else the nearest ancestor workspace of a subagent source) and
@@ -61,17 +76,52 @@
     - id: authorization
       name: '@deepseek-ai/dsh-authorization'
 
-    # 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.
-    # 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'
+    # The 0.1.7 declarative preset registry: preset identity, revisions and
+    # default/selection policy are registry-owned (deployment `default` here;
+    # the user's `selectedDefault` rides the profile form). The four shipped
+    # preset declarations follow as separate patch files under
+    # generated/dsh-presets/, listed after this file in package.json
+    # `dsh.bundle.patch` — a generated, parity-gated byte-exact mirror of
+    # @deepseek-ai/dsh-web-app's exported preset assets (0.1.7
+    # dsh.bundle.patch cannot reference another package's files).
+    - id: agent-preset-registry
+      name: '@deepseek-ai/dsh-agent-preset-registry'
       config:
         default: standard
 
+    # Production hardening for per-session preset composition. A live Agent
+    # whose standing preset generation disappears (the DSH registry owns that
+    # lifetime; the TUI must not remount/reparent/recreate an Agent) would
+    # otherwise keep addressing the model with only its Agent-own rows — the
+    # observed failure mode was a request whose tool list had collapsed to
+    # `subagent` alone, with no error anywhere. This official companion turns
+    # that into a loud, early failure at the next prompt assembly instead.
+    #
+    # The allowlist is deliberate and minimal: this bundle introduces exactly
+    # ONE production invariant, so a future layer shipping another invariant
+    # companion cannot silently enable itself here. The companion's own
+    # `/invariant` entry declares `inject = ['invariants']`; no second
+    # dependency management is written here.
+    #
+    # DEPENDENCY CONTRACT: `@deepseek-ai/dsh-invariants` is a COMPOSITION row
+    # resolved by the dsh Host (the package ships inside the dsh installation),
+    # not a module-graph peer — exactly like `@deepseek-ai/dsh-agent-preset`,
+    # which the same rule keeps in devDependencies. It therefore carries an
+    # exact devDependency pin for the real-mount tests and deliberately NO
+    # peerDependency: `scripts/naming-gate.mjs` rejects a `@deepseek-ai/*` peer
+    # that `src/` never imports as a dead peer, and a phantom peer would invite
+    # duplicate in-box copies in the profile. The companion subpath below is
+    # covered by the registry's own runtime peer.
+    - id: invariants
+      name: '@deepseek-ai/dsh-invariants'
+      config:
+        enabled: true
+        package_allowlist:
+          - '^@deepseek-ai/dsh-agent-preset-registry$'
+
+    - id: agent-preset-registry-invariant
+      name: '@deepseek-ai/dsh-agent-preset-registry/invariant'
+
     # The official standard preset composes its `subagent` tool with
     # `modelSelectionSettings: true`, which injects this Host-owned setting
     # service — the row is required for the standard composition to mount.
@@ -94,7 +144,8 @@
 # its tools, its prompt sections, its delegation backends. The base keeps them
 # for single-session surfaces that compose their agent process-wide; the TUI
 # now composes one preset per session, so these rows are disabled here and the
-# `agent-presets` row above lets each session mount a preset instead.
+# official `agent-preset-registry` row above, plus the declarations it resolves,
+# lets each session mount a preset instead.
 #
 # Disabling rather than deleting is deliberate: the base is shared, and a row
 # absent from a surface overlay would silently reappear the day someone

package/dist/builtins.mjs

@@ -1,5 +1,5 @@
-import { B as PI_TUI_EXTENSIONS_SERVICE, I as dshVersion } from "./src-5aY9svZj.mjs";
-import { n as TUI_STARTUP_SERVICE } from "./startup-CGeJ1k1B.mjs";
+import { L as dshVersion, V as PI_TUI_EXTENSIONS_SERVICE } from "./src-BAwPimrH.mjs";
+import { n as TUI_STARTUP_SERVICE } from "./startup-xTIOW90U.mjs";
 import { readFileSync } from "node:fs";
 import { join } from "node:path";
 //#region src/builtins.ts

package/dist/extension/advanced.d.mts

@@ -302,7 +302,12 @@ interface AdvancedHostState {
   setTitle(title: string | undefined): void;
   /** Override the working-indicator message (undefined clears). */
   setWorkingMessage(message: string | undefined): void;
-  /** Set the tool-output expansion master switch. */
+  /** Set the transcript-detail bulk-expansion master switch (recent
+   * collapsible transcript content). */
+  setTranscriptDetailExpanded(expanded: boolean): void;
+  /** Set the transcript-detail bulk-expansion master switch.
+   * @deprecated Use {@link setTranscriptDetailExpanded} — the same runtime
+   * state under its canonical name (post-F6 plan §5.6). */
   setToolsExpanded(expanded: boolean): void;
 }
 /** The full advanced facade (plan §4: `advanced(service)`). */

package/dist/extensions.mjs

@@ -1,2 +1,2 @@
-import { B as PI_TUI_EXTENSIONS_SERVICE, H as describeKey, L as apply, R as inject, V as API_VERSION, z as name } from "./src-5aY9svZj.mjs";
+import { B as name, H as API_VERSION, R as apply, U as describeKey, V as PI_TUI_EXTENSIONS_SERVICE, z as inject } from "./src-BAwPimrH.mjs";
 export { API_VERSION, PI_TUI_EXTENSIONS_SERVICE, apply, describeKey, inject, name };