@xmoon76/dsh-pi-tui 0.4.0-alpha.1 → 0.4.0

package/README.en.md

@@ -18,7 +18,7 @@ dsh --profile pi-tui
 
 ## DSH compatibility and source validation
 
-The published package declares the lower-bound-only DSH peer contract `>=0.1.2-alpha.2`. Source validation does not change that contract or vendor DSH into this repository.
+The published package declares the lower-bound-only DSH peer contract `>=0.1.2-rc.1`. Source validation does not change that contract or vendor DSH into this repository.
 
 When the target DSH version is not yet available from npm, validate against the official checkout pinned by commit SHA:
 
@@ -26,7 +26,7 @@ When the target DSH version is not yet available from npm, validate against the
 pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
 ```
 
-CI uses Source Mode for `next` and npm Mode for `main` and every tag. The source lane validates the complete official DSH tarball family, TUI presets, and the old-runtime boundary; the published `pi2dsh` ecosystem check is explicitly marked skipped until a compatible published combination exists. 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. 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.
 
 ## Features
 
@@ -115,10 +115,17 @@ The browser distinguishes:
 
 Completed one-shot Subagents remain available for persisted Transcript inspection.
 
-A direct `continuable` Child can be opened in an interactive viewer and sent follow-up messages directly. The Child has its own Transcript, Draft, and runtime state, without modifying the main Session input.
+A direct `continuable` Child can be opened in an interactive viewer and sent follow-up messages directly (through DSH's official `subagents.prompt()` human channel — queued in order as the Child's own next turn, with user provenance). The Child has its own Transcript, Draft, and runtime state, without modifying the main Session input.
 
 Deeper nested Subagents are read-only by default.
 
+The official subagent model selection (the DSH `subagent-model-selection`
+setting) can be toggled and its allowlist maintained in `/settings`: once
+enabled, a NEW session's official `subagent` tool may pick the child
+provider/model per call (bounded by the allowlist). The setting is sampled at
+session composition and never rewrites the tools of an already-running
+session.
+
 ### Shell
 
 The editor supports two Shell modes:
@@ -312,19 +319,25 @@ dsh-pi-tui:
 
 | TUI package line | Matching DSH line | Notes |
 |---|---|---|
-| `0.4.0-alpha.1` (`@next`) | `>=0.1.2-alpha.2` | Current prerelease; each release validates its concrete DSH family |
+| `0.4.0` (`@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 two lines: DSH 0.1.1 is outside the 0.4 peer window and the
+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. For the current `0.4.0-alpha.1`, install
-DSH first and then add the TUI to a profile:
+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`. For the
+current 0.4 stable release, install the matching DSH first and then add the
+TUI to a profile:
 
 ```sh
-npm install -g @deepseek-ai/dsh@0.1.2-alpha.3
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
+npm install -g @deepseek-ai/dsh@0.1.2-rc.1
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
 
@@ -336,7 +349,7 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
 dsh --profile pi-tui
 ```
 
-The declared 0.4 support range is `>=0.1.2-alpha.2`; each release validates
+The current 0.4 line declares `>=0.1.2-rc.1`; each release validates
 its concrete DSH family. Running only `npm install -g @xmoon76/dsh-pi-tui` does
 not install the plugin into a DSH profile; the `dsh plugin` command is still
 required.
@@ -348,12 +361,11 @@ only after the roster proves that no custom `code` preset exists.
 
 ### npm
 
-Using a dedicated `pi-tui` profile is recommended. Once a stable 0.4 release
-exists, use the matching stable TUI channel (`@latest`); use `@next` for the
-prerelease channel:
+Using a dedicated `pi-tui` profile is recommended. Use the TUI channel that
+matches your DSH line: `@latest` for stable releases, `@next` for prereleases:
 
 ```sh
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
 
@@ -365,7 +377,7 @@ dsh --profile pi-tui --session <session-id>
 
 ### Source Mode (validation only)
 
-Source Mode is only for `next` CI and local compatibility validation. 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.
+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.
 
 ```sh
 pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"

package/README.md

@@ -18,7 +18,7 @@ dsh --profile pi-tui
 
 ## DSH 兼容性与源码验证
 
-发布包通过 `package.json` peer contract 使用 DSH `>=0.1.2-alpha.2`；源码验证不会修改这个发布契约，也不会把 DSH vendor 进本仓库。
+发布包通过 `package.json` peer contract 使用 DSH `>=0.1.2-rc.1`；源码验证不会修改这个发布契约，也不会把 DSH vendor 进本仓库。
 
 当目标 DSH 版本尚未发布到 npm 时，可以用固定 commit 的官方源码包做本地验证：
 
@@ -26,7 +26,7 @@ dsh --profile pi-tui
 pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
 ```
 
-CI 中 `next` 使用 Source Mode，`main` 和所有 tag 使用 npm Mode。源码 lane 会验证完整的官方 DSH tarball family、TUI 预设和旧 runtime 边界；依赖已发布 `pi2dsh` 的生态检查会明确标记为 skipped。详细流程见 [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md)。
+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)。
 
 ## 功能
 
@@ -94,7 +94,7 @@ Rewind 会从选中的历史 User Turn 创建新的 Child Session，并把对应
 
 ### Subagent 与后台任务
 
-`/tasks` 提供当前 Session 的任务浏览器。
+`/tasks` 打开完整 Task Center（当前 Session 的所有后台工作）；Footer 的 `↓` 直接打开轻量 Quick Tasks（只看正在运行的工作）。
 
 Subagent 按完整 lineage 显示，包括嵌套创建的 descendant：
 
@@ -113,12 +113,19 @@ main
 * nested descendant
 * 后台 Job
 
+两个视图共享同一份运行时状态：`A` 切换 Active / All scope，`Tab` 切换类型过滤，`/` 进入搜索，`S`（确认后）停止所选任务，`N` / `Shift+N` 在运行中的任务间跳转，Quick 内 `T` 或底部 "View all" 行进入完整 Task Center，`Esc` 逐层返回。
+
 已经结束的 one-shot Subagent 仍可以打开并查看持久化 Transcript。
 
-对于当前 Session 的直接 `continuable` Child，可以进入交互式 Viewer，并直接向该 Subagent 发送后续消息。Child 使用自己的 Transcript、Draft 和运行状态，不会修改主 Session 的输入。
+对于当前 Session 的直接 `continuable` Child，可以进入交互式 Viewer，并直接向该 Subagent 发送后续消息（走 DSH 官方 `subagents.prompt()` 人类输入通道——按顺序排队为 Child 自己的下一个 turn，并保留 user 来源）。Child 使用自己的 Transcript、Draft 和运行状态，不会修改主 Session 的输入。
 
 更深层的 nested Subagent 默认以只读方式查看。
 
+官方 Subagent 模型选择（DSH `subagent-model-selection` 设置）可在 `/settings`
+中开关并维护 allowlist：开启后**新建** Session 的官方 `subagent` 工具可以按调用
+选择子 Agent 的 provider/model（受 allowlist 限制）。设置在 Session 组合时采样，
+不会改写已在运行的 Session 的工具。
+
 ### Shell
 
 编辑器支持两种 Shell 模式：
@@ -301,18 +308,23 @@ dsh-pi-tui:
 
 | TUI 包版本 | 对应 DSH 版本 | 说明 |
 |---|---|---|
-| `0.4.0-alpha.1`（`@next`） | `>=0.1.2-alpha.2` | 当前预发布线；按每个发布版本的具体 DSH family 验证 |
+| `0.4.0`（`@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。`0.4.0-alpha.1` 的推荐安装顺序如下（先装 DSH，再把
-TUI 装入 profile）：
+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`。当前 0.4 稳定版的推荐安装顺序如下
+（先装 DSH，再把 TUI 装入 profile）：
 
 ```sh
-npm install -g @deepseek-ai/dsh@0.1.2-alpha.3
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
+npm install -g @deepseek-ai/dsh@0.1.2-rc.1
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
 
@@ -324,8 +336,8 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
 dsh --profile pi-tui
 ```
 
-`0.4` 的声明支持范围是 `>=0.1.2-alpha.2`；每个发布版本都会验证具体的
-DSH family。仅执行 `npm install -g @xmoon76/dsh-pi-tui` 不会把插件安装进
+`0.4` 当前线的声明支持范围是 `>=0.1.2-rc.1`；每个发布版本都会验证
+具体的 DSH family。仅执行 `npm install -g @xmoon76/dsh-pi-tui` 不会把插件安装进
 DSH profile，实际使用仍应执行上面的 `dsh plugin` 命令。
 
 新的 Agent preset 使用当前 roster 中选定的 id。DSH 允许合法的自定义
@@ -335,11 +347,11 @@ DSH profile，实际使用仍应执行上面的 `dsh plugin` 命令。
 
 ### npm
 
-推荐使用单独的 `pi-tui` profile。稳定版发布后，使用与 DSH 版本匹配的
+推荐使用单独的 `pi-tui` profile。使用与 DSH 版本匹配的
 TUI channel（稳定版用 `@latest`，预发布版用 `@next`）：
 
 ```sh
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
 
@@ -351,7 +363,7 @@ dsh --profile pi-tui --session <session-id>
 
 ### Source Mode（仅验证）
 
-Source Mode 只用于 `next` 的 CI 和本地兼容性验证，不是发布或用户安装方式。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
+Source Mode 是 `next` CI 按跟踪策略选用的、并可用于本地兼容性检查的验证专用 distribution。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
 
 ```sh
 pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"

package/cordis.patch.yml

@@ -52,9 +52,13 @@
       config:
         default: standard
 
-    # The official standard preset enables per-session subagent model
-    # selection. Its tool-subagent row requires this Host service when it
-    # mounts; without the row the default standard composition throws.
+    # 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.
+    # Mounting the service ALONE enables nothing: it only owns the
+    # `subagent-model-selection` settings section (default enabled=false,
+    # empty allowlist). Each NEW session samples that section at
+    # composition; the TUI exposes the toggle + allowlist in /settings.
     - id: subagent-model-selection-settings
       name: '@deepseek-ai/dsh-tool-subagent/model-selection-settings'
 
@@ -84,8 +88,8 @@
 #
 # Rows that STAY on the host plane (not listed): `tools` (registry), `shell-env`
 # (publishes the DSH env the model's shell sees), `subagent` + its spawn/fork
-# backends (process singletons), `tool-subagent-report` (host singleton),
-# `subagent-model-selection-settings`, the goal/jobs/compaction services and
+# backends (process singletons), `subagent-model-selection-settings`, the
+# goal/jobs/compaction services and
 # their host infrastructure, `permission`, `approval`, `sandbox*`,
 # `fs-observation-policy`, `spill*`, `timeout-policy`, `repeat-tool-reminder`,
 # `session-*`, `token-meter`. `command-goal` is disabled below and reintroduced

package/dist/builtins.mjs

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

package/dist/extension/unstable.d.mts

@@ -4,15 +4,35 @@ import { D as PiTuiApiInfo, _ as ExtensionTier, ot as TuiOverlayOptions } from "
 /** API level of the unstable tier. Bumped only on unstable breaking changes. */
 declare const UNSTABLE_API_LEVEL: 1;
 /**
- * One raw terminal input chunk (plan §5). The plugin receives the RAW
- * bytes exactly as the terminal delivered them — no decoding, no
- * sanitization. `surfaceId` identifies the surface generation the chunk
- * arrived on.
+ * One normalized terminal input sequence (plan §5). The plugin receives
+ * the input AFTER the terminal pipeline has reassembled and normalized it
+ * — NOT the raw OS byte stream. The Host's input path is:
+ *
+ * ```text
+ * OS stdin
+ *   → ProcessTerminal / StdinBuffer (batched chunks split into individual
+ *     sequences; bracketed-paste content re-wrapped in its markers)
+ *   → keyboard-protocol negotiation (Kitty flags / DA replies filtered)
+ *   → native modifier normalization (Windows / Apple Terminal Return →
+ *     CSI-u Shift+Enter)
+ *   → TUI-owned query replies filtered (OSC11 background, color-scheme
+ *     reports, cell-size responses)
+ *   → TUI input listeners
+ *   → THIS capture (BEFORE Host semantic routing)
+ * ```
+ *
+ * So the sequence is a `preHostInput` event: it can see, consume or
+ * rewrite anything the Host router would otherwise decode — Enter, Esc,
+ * Ctrl+C, bracketed paste (markers preserved), CSI-u sequences — but it
+ * CANNOT see the terminal-negotiation replies the TUI itself consumes
+ * (Kitty/DA, OSC11, color-scheme, cell-size), and it never sees raw
+ * multi-byte chunks mid-sequence. `surfaceId` identifies the surface
+ * generation the sequence arrived on.
  */
 interface UnstableRawInputEvent {
-  /** The raw terminal data (a chunk, not necessarily one key). */
+  /** The normalized terminal input sequence (a sequence, not a raw chunk). */
   readonly data: string;
-  /** The surface generation the chunk arrived on. */
+  /** The surface generation the sequence arrived on. */
   readonly surfaceId: string;
 }
 /** The outcome of one raw interception (plan §5). */
@@ -33,12 +53,17 @@ type UnstableRawInputResult = /** Pass the chunk through unchanged (the Host con
 type UnstableRawCaptureMode = 'observe' | 'capture' | 'exclusive';
 /**
  * One raw input capture registration (plan §5/§8). The capture is
- * consulted by the Host BEFORE terminal protocol decoding — it can see,
- * consume or rewrite ANY raw chunk, including Enter, Esc, Ctrl+C, paste,
- * CSI-u sequences and terminal-specific protocols. This is the Unstable
- * contract: a broken capture can make Host shortcuts stop working. The
- * ONLY Host-owned recovery is the emergency fail-safe (triple-Esc), which
- * the Unstable API cannot rewrite.
+ * consulted by the Host BEFORE semantic routing — after the terminal
+ * pipeline has reassembled and normalized the input (see
+ * {@link UnstableRawInputEvent}): it can see, consume or rewrite any
+ * sequence that would otherwise reach the Host router, including Enter,
+ * Esc, Ctrl+C, paste and CSI-u sequences. It is NOT consulted before
+ * terminal protocol decoding: the TUI's own negotiation replies (Kitty
+ * flags, DA, OSC11, color-scheme, cell-size) never reach a capture, and
+ * a capture cannot break the terminal negotiation. This is the Unstable
+ * contract: a broken capture can still make Host shortcuts stop working.
+ * The ONLY Host-owned recovery is the emergency fail-safe (triple-Esc),
+ * which the Unstable API cannot rewrite.
  *
  * Modes:
  * - `observe` — never consumes or rewrites; a pure observer.
@@ -48,8 +73,8 @@ type UnstableRawCaptureMode = 'observe' | 'capture' | 'exclusive';
  *   registration is an explicit error, never a load-order winner.
  *
  * Ordering is deterministic: `priority` ASC, then `id` ASC. A throwing
- * handler is isolated (health ledger) and FAILS OPEN — the chunk passes
- * through, so a broken capture can never stall the TUI.
+ * handler is isolated (health ledger) and FAILS OPEN — the sequence
+ * passes through, so a broken capture can never stall the TUI.
  */
 interface UnstableRawInputSpec {
   /** Stable diagnostic identity, unique per owner. */
@@ -83,7 +108,9 @@ interface UnstableRawInputHandle {
 interface UnstableMountedComponent {
   /** Render the current state as raw terminal lines at the given width. */
   render(width: number): string[];
-  /** Receive one raw input chunk while this component owns focus. */
+  /** Receive one normalized terminal input sequence while this component
+   * owns focus (the same preHostInput contract as
+   * {@link UnstableRawInputEvent} — never raw OS bytes). */
   handleInput?(raw: string): void;
   /** The component was disposed (mount closed / surface died). */
   dispose?(): void;
@@ -133,9 +160,10 @@ interface UnstableSurfaceHandle {
   requestRender(): void;
   /**
    * Mount a low-level component (plan §9 option A) as a capturing overlay.
-   * The plugin renders RAW lines and receives RAW input; the Host owns
-   * the physical mount, focus, stacking, fullscreen migration and
-   * teardown. Caller-fiber-owned lease.
+   * The plugin renders RAW lines and receives the normalized input
+   * sequence (the preHostInput contract — see UnstableRawInputEvent;
+   * never raw OS bytes); the Host owns the physical mount, focus,
+   * stacking, fullscreen migration and teardown. Caller-fiber-owned lease.
    */
   mountComponent(component: UnstableMountedComponent, options?: TuiOverlayOptions): UnstableMountLease;
 }

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-syk6h8J9.mjs";
+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-zkySYmLZ.mjs";
 import "./startup.mjs";
 export { API_VERSION, PI_TUI_EXTENSIONS_SERVICE, apply, describeKey, inject, name };

package/dist/index.d.mts

@@ -725,7 +725,7 @@ declare function recordedPreset(ctx: Context, sessionId: string): Promise<string
 /** The session surface {@link recomposeBlank} needs: its log and the append seam. */
 interface RecomposableSession {
   readonly id: string;
-  readonly events: readonly SessionEvent$1[];
+  snapshotEvents(): readonly SessionEvent$1[];
   append(type: 'agent-preset/selected', data: {
     agentPreset: string;
   }): unknown;

package/dist/index.mjs

@@ -1,3 +1,3 @@
-import { A as shouldConsumeAdvertisedMiss, C as normalizeSkillInvocation, D as resumeCommand, E as resolveInitialCatalog, F as teardownViewerForSessionSwap, I as viewerActionCapability, M as subagentJobTranscriptId, N as subagentJobViewHint, O as runningProfile, P as subagentNoticeIsFailure, R as forkSeed, S as name, T as recordedPreset, _ as interruptAgent, a as SessionLockRefusedError, b as isUserQueueInput, c as commandRejectsImages, d as contextRefreshKind, f as createViewerOpenToken, g as inject, h as foldQueueRows, i as SESSIONLESS_COMMANDS, j as shouldSteerOnEnter, k as settleCompactionSurface, l as compactingFromLog, m as foldCompactionEvent, n as HOST_COMMAND_CATALOG, o as apply, p as dangerCommand, r as LOCAL_COMMANDS, s as busyAfterTurnBoundary, t as Config, u as composeAgent, v as isPlainExitPrompt, w as recomposeBlank, x as matchPendingSubagentCall, y as isSubagentSettlementNotice } from "./src-syk6h8J9.mjs";
+import { A as shouldConsumeAdvertisedMiss, C as normalizeSkillInvocation, D as resumeCommand, E as resolveInitialCatalog, F as teardownViewerForSessionSwap, I as viewerActionCapability, M as subagentJobTranscriptId, N as subagentJobViewHint, O as runningProfile, P as subagentNoticeIsFailure, R as forkSeed, S as name, T as recordedPreset, _ as interruptAgent, a as SessionLockRefusedError, b as isUserQueueInput, c as commandRejectsImages, d as contextRefreshKind, f as createViewerOpenToken, g as inject, h as foldQueueRows, i as SESSIONLESS_COMMANDS, j as shouldSteerOnEnter, k as settleCompactionSurface, l as compactingFromLog, m as foldCompactionEvent, n as HOST_COMMAND_CATALOG, o as apply, p as dangerCommand, r as LOCAL_COMMANDS, s as busyAfterTurnBoundary, t as Config, u as composeAgent, v as isPlainExitPrompt, w as recomposeBlank, x as matchPendingSubagentCall, y as isSubagentSettlementNotice } from "./src-zkySYmLZ.mjs";
 import "./startup.mjs";
 export { Config, HOST_COMMAND_CATALOG, LOCAL_COMMANDS, SESSIONLESS_COMMANDS, SessionLockRefusedError, apply, busyAfterTurnBoundary, commandRejectsImages, compactingFromLog, composeAgent, contextRefreshKind, createViewerOpenToken, dangerCommand, foldCompactionEvent, foldQueueRows, forkSeed, inject, interruptAgent, isPlainExitPrompt, isSubagentSettlementNotice, isUserQueueInput, matchPendingSubagentCall, name, normalizeSkillInvocation, recomposeBlank, recordedPreset, resolveInitialCatalog, resumeCommand, runningProfile, settleCompactionSurface, shouldConsumeAdvertisedMiss, shouldSteerOnEnter, subagentJobTranscriptId, subagentJobViewHint, subagentNoticeIsFailure, teardownViewerForSessionSwap, viewerActionCapability };