@xmoon76/dsh-pi-tui 0.4.1 → 0.4.3-alpha.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.en.md CHANGED
@@ -24,14 +24,20 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
24
24
  dsh --profile pi-tui
25
25
  ```
26
26
 
27
- ### Preview / next
27
+ ### Next / npm line (validation)
28
28
 
29
- Preview releases contain unreleased changes. Use this channel only when you need
30
- to try or validate a prerelease:
29
+ The current `next` line targets the published npm release `dsh-v0.1.3-alpha.2`.
30
+ Use the isolated npm driver (installs the exact DSH version declared by this
31
+ checkout and exercises the full build/test/package path):
31
32
 
32
33
  ```sh
33
- dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
34
- dsh --profile pi-tui
34
+ pnpm compat:dsh:npm
35
+ ```
36
+
37
+ The startup notice on an old runtime suggests the exact npm upgrade:
38
+
39
+ ```sh
40
+ npm install -g @deepseek-ai/dsh@0.1.3-alpha.2
35
41
  ```
36
42
 
37
43
  ### Requirements
@@ -43,21 +49,17 @@ dsh --profile pi-tui
43
49
 
44
50
  | TUI package line | Matching DSH line | Notes |
45
51
  |---|---|---|
46
- | `0.4.1` (`@latest`) | `>=0.1.2-rc.1` | Current stable; validated against the rc.1 family |
47
- | `0.4.x-alpha` (`@next`) | `>=0.1.2-rc.1` | Subsequent prerelease; each release validates its concrete DSH family |
48
- | `0.4.0-alpha.2` (published) | `>=0.1.2-alpha.4` | Previous 0.4 prerelease; its releases validated the alpha.4/alpha.5 family |
49
- | `0.4.0-alpha.1` (published) | `>=0.1.2-alpha.2` | Earlier 0.4 prerelease; accepts the alpha.2/alpha.3 runtime |
52
+ | `0.4.1` (published `@latest`) | `>=0.1.2-rc.1` | Historical stable; validated against the rc.1 family |
53
+ | Current `next` npm line (this checkout; version `0.4.3-alpha.2`) | `>=0.1.3-alpha.2` | Published npm alpha.2 target; validated against the exact 0.1.3-alpha.2 family |
50
54
  | `0.3.x` (`@0.3`) | `0.1.1-rc.2` | Legacy runtime line |
51
55
 
52
- Do not mix the lines: DSH 0.1.1 is outside the 0.4 peer window and the
53
- normal incompatible-runtime boundary will fail. The startup row prints upgrade
54
- and rollback guidance when concurrent Loader ordering allows it, but that
55
- friendly notice is best-effort rather than a startup-order guarantee. If you
56
- keep DSH 0.1.1, use the 0.3 TUI line; if you keep the alpha.2/alpha.3
57
- baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`; if you keep the
58
- alpha.4/alpha.5 baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.2`. The stable
59
- installation path is documented above under “Install into a DSH profile”; if
60
- you need to keep the legacy DSH runtime, use this compatibility recovery path:
56
+ Do not mix the stable and `next` lines. The published 0.4.1 stable line
57
+ still uses the 0.1.2-rc.1 family; if you keep a legacy DSH runtime, use the 0.3
58
+ compatibility line below. This `next` checkout declares the published
59
+ `0.1.3-alpha.2` npm floor, and older runtimes fail at the normal
60
+ incompatible-runtime boundary. The startup row's compatibility notice is
61
+ best-effort rather than a Loader startup-order guarantee; the suggested upgrade
62
+ target is a published npm version.
61
63
 
62
64
  ```sh
63
65
  npm install -g @deepseek-ai/dsh@0.1.1-rc.2
@@ -65,9 +67,10 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
65
67
  dsh --profile pi-tui
66
68
  ```
67
69
 
68
- The current 0.4 line declares `>=0.1.2-rc.1`; each release validates
69
- its concrete DSH family. `npm install -g` is only for installing DSH itself; to
70
- install dsh-pi-tui into a DSH profile, you must use the `dsh plugin` command.
70
+ The published `0.4.1` stable line declares `>=0.1.2-rc.1`; this checkout's
71
+ `next` npm line declares `>=0.1.3-alpha.2`. `npm install -g` is only for
72
+ installing a published DSH; to install dsh-pi-tui into a DSH profile, you must
73
+ use the `dsh plugin` command.
71
74
 
72
75
  New agent sessions use the official roster's selected preset id. A custom DSH
73
76
  preset literally named `code` is valid and remains `code` when it exists in the
@@ -234,7 +237,7 @@ Typing `@` opens workspace file search and completion:
234
237
  @"path with spaces/file.ts"
235
238
  ```
236
239
 
237
- `/image <path>` also completes files and directories; paths with spaces, quotes, or Windows separators preserve the input dialect, and directories can be expanded further.
240
+ `/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.
238
241
 
239
242
  Resolvable relative paths are canonicalized before submission.
240
243
 
@@ -551,22 +554,34 @@ dsh --profile pi-tui-dev
551
554
 
552
555
  ## DSH compatibility and validation
553
556
 
554
- This section contains Source Mode and CI validation details only; ordinary users do not need Source Mode to install the TUI.
557
+ This section contains DSH compatibility and CI validation details only; ordinary users do not need them to install the TUI.
555
558
 
556
- ### Source Mode (validation only)
559
+ ### npm mode (current `next`)
557
560
 
558
- 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.
561
+ The current `next` line is npm mode: it targets the published
562
+ `dsh-v0.1.3-alpha.2` family declared by this checkout's `package.json` and
563
+ resolved by its frozen lockfile. The isolated npm driver installs that exact
564
+ family from the public registry and exercises the TUI build/test/package path:
559
565
 
560
566
  ```sh
561
- pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
562
567
  pnpm compat:dsh:npm
563
568
  ```
564
569
 
570
+ ### Source Mode (validation only)
571
+
572
+ Source Mode is the validation-only distribution for an unpublished DSH
573
+ checkout, available for local compatibility checks and explicit
574
+ source-boundary work. It reads the full commit pin in
575
+ `test/compat/dsh-source.json`, builds the official DSH tarball family, installs
576
+ it through temporary pnpm overrides, and removes the temporary state afterward.
577
+ Do not write DSH source paths, `file:` dependencies, or workspace symlinks into
578
+ a published package.
579
+
565
580
  The published package already contains the Pi TUI fork required at runtime. No separate internal TUI package needs to be installed.
566
581
 
567
582
  ### CI validation policy
568
583
 
569
- 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.
584
+ 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.
570
585
 
571
586
  ## Repository layout
572
587
 
package/README.md CHANGED
@@ -23,13 +23,20 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
23
23
  dsh --profile pi-tui
24
24
  ```
25
25
 
26
- ### Preview / next
26
+ ### Next / npm 线(验证)
27
27
 
28
- 预览版包含未发布的变更,仅在需要体验或验证预发布版本时使用:
28
+ 当前 `next` 线以已发布的 npm 版本 `dsh-v0.1.3-alpha.2` 为兼容目标。使用
29
+ 隔离的 npm 驱动验证(安装 checkout 声明的精确 DSH 版本并跑完整
30
+ build/test/package 路径):
29
31
 
30
32
  ```sh
31
- dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
32
- dsh --profile pi-tui
33
+ pnpm compat:dsh:npm
34
+ ```
35
+
36
+ 旧 runtime 的启动提示会给出精确的 npm 升级命令:
37
+
38
+ ```sh
39
+ npm install -g @deepseek-ai/dsh@0.1.3-alpha.2
33
40
  ```
34
41
 
35
42
  ### 环境要求
@@ -41,19 +48,15 @@ dsh --profile pi-tui
41
48
 
42
49
  | TUI 包版本 | 对应 DSH 版本 | 说明 |
43
50
  |---|---|---|
44
- | `0.4.1`(`@latest`) | `>=0.1.2-rc.1` | 当前稳定版;按 0.1.2-rc.1 family 验证 |
45
- | `0.4.x-alpha`(`@next`) | `>=0.1.2-rc.1` | 后续预发布线;按每个发布版本的具体 DSH family 验证 |
46
- | `0.4.0-alpha.2`(已发布) | `>=0.1.2-alpha.4` | 上一条 0.4 预发布线;其发布版本按 alpha.4/alpha.5 family 验证 |
47
- | `0.4.0-alpha.1`(已发布) | `>=0.1.2-alpha.2` | 更早的 0.4 预发布线;接受 alpha.2/alpha.3 运行时 |
51
+ | `0.4.1`(已发布 `@latest`) | `>=0.1.2-rc.1` | 历史稳定版;按 0.1.2-rc.1 family 验证 |
52
+ | 当前 `next` npm 线(本 checkout;版本 `0.4.3-alpha.2`) | `>=0.1.3-alpha.2` | 已发布的 npm alpha.2 目标;按精确 0.1.3-alpha.2 family 验证 |
48
53
  | `0.3.x`(`@0.3`) | `0.1.1-rc.2` | 旧运行时兼容线 |
49
54
 
50
- 不要把两条线混装:DSH 0.1.1 不在 0.4 的 peer 支持范围内,运行时会在
51
- 正常的不兼容边界以非零状态失败。启动行会在 Loader 并发挂载顺序允许时打印
52
- 升级和回退提示,但该友好提示是 best-effort,不是启动顺序保证;保留 DSH
53
- 0.1.1 时请使用 0.3,保留 alpha.2/alpha.3 时请使用
54
- `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`,保留 alpha.4/alpha.5 时请使用
55
- `@xmoon76/dsh-pi-tui@0.4.0-alpha.2`。稳定版的安装方式已在上方“安装到 DSH
56
- Profile”中给出;如果需要保留旧 DSH,请使用下面的兼容恢复路径:
55
+ 不要把稳定线与 `next` 线混装。已发布的 0.4.1 稳定线仍按
56
+ 0.1.2-rc.1 family 使用;保留旧 DSH 时请使用下方的 0.3 兼容线。当前
57
+ `next` checkout 的 peer floor 是 `>=0.1.3-alpha.2`,旧 runtime 会在正常的
58
+ 不兼容边界以非零状态失败。启动行的兼容提示是 best-effort,不是 Loader
59
+ 启动顺序保证;它建议的升级目标是已发布的 npm 版本。
57
60
 
58
61
  ```sh
59
62
  npm install -g @deepseek-ai/dsh@0.1.1-rc.2
@@ -61,9 +64,10 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
61
64
  dsh --profile pi-tui
62
65
  ```
63
66
 
64
- `0.4` 当前线的声明支持范围是 `>=0.1.2-rc.1`;每个发布版本都会验证
65
- 具体的 DSH family。`npm install -g` 仅用于安装 DSH 本身;要将 dsh-pi-tui
66
- 安装进 DSH profile,必须使用 `dsh plugin` 命令。
67
+ 已发布的 `0.4.1` 稳定线声明支持范围是 `>=0.1.2-rc.1`;本 checkout 的
68
+ `next` npm 线则声明 `>=0.1.3-alpha.2`。`npm install -g` 仅用于
69
+ 安装已发布的 DSH;要将 dsh-pi-tui 安装进 DSH profile,必须使用
70
+ `dsh plugin` 命令。
67
71
 
68
72
  新的 Agent preset 使用当前 roster 中选定的 id。DSH 允许合法的自定义
69
73
  `code` preset;只要当前 roster 存在它,显式输入和持久化状态都会保留 `code`。
@@ -223,7 +227,7 @@ Shell 卡片默认只显示有限的输出预览,`Ctrl+O` 可以展开完整
223
227
  @"path with spaces/file.ts"
224
228
  ```
225
229
 
226
- `/image <path>` 也支持文件与目录补全;带空格、引号或 Windows 分隔符的路径会保留输入方言,目录可以继续展开。
230
+ `/attach <path>` 是统一的 Client-local 图片/文件入口;`/image <path>` 保持图片专用兼容语义。两者都支持文件与目录补全;带空格、引号或 Windows 分隔符的路径会保留输入方言,目录可以继续展开。
227
231
 
228
232
  能够解析的相对路径会在提交时转换为明确的文件路径。
229
233
 
@@ -529,22 +533,31 @@ dsh --profile pi-tui-dev
529
533
 
530
534
  ## DSH 兼容性与验证
531
535
 
532
- 以下内容仅介绍 Source Mode 和 CI 验证细节;普通用户无需使用 Source Mode 安装 TUI。
536
+ 以下内容仅介绍 DSH 兼容性与 CI 验证细节;普通用户无需了解即可安装 TUI。
533
537
 
534
- ### Source Mode(仅验证)
538
+ ### npm 模式(当前 `next`)
535
539
 
536
- Source Mode 是 `next` CI 按跟踪策略选用的、并可用于本地兼容性检查的验证专用 distribution。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family,通过临时 pnpm overrides 安装,并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
540
+ 当前 `next` 线是 npm 模式:以本 checkout 的 `package.json` 声明、冻结
541
+ lockfile 解析的已发布 `dsh-v0.1.3-alpha.2` family 为兼容目标。隔离的 npm
542
+ 驱动从公共 registry 安装该精确 family,并跑完整 build/test/package 路径:
537
543
 
538
544
  ```sh
539
- pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
540
545
  pnpm compat:dsh:npm
541
546
  ```
542
547
 
548
+ ### Source Mode(仅验证)
549
+
550
+ Source Mode 是面向未发布 DSH checkout 的验证专用 distribution,用于本地
551
+ 兼容性检查与显式的 source 边界工作。它从 `test/compat/dsh-source.json` 的
552
+ 完整 commit SHA 构建官方 DSH tarball family,通过临时 pnpm overrides 安装,
553
+ 并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace
554
+ symlink 写入发布 package。
555
+
543
556
  安装包已经包含运行所需的 Pi TUI fork,不需要额外安装内部的 TUI package。
544
557
 
545
558
  ### CI 验证策略
546
559
 
547
- 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)。
560
+ 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)。
548
561
 
549
562
  ## 项目结构
550
563
 
package/cordis.patch.yml CHANGED
@@ -110,9 +110,6 @@
110
110
  - id: tool-fs-search
111
111
  disabled: true
112
112
 
113
- - id: tool-str-replace-editor
114
- disabled: true
115
-
116
113
  - id: skill-filesystem
117
114
  disabled: true
118
115
 
package/dist/builtins.mjs CHANGED
@@ -1,4 +1,4 @@
1
- import { H as PI_TUI_EXTENSIONS_SERVICE, L as dshVersion } from "./src-CeGK2mHo.mjs";
1
+ import { I as dshVersion, V as PI_TUI_EXTENSIONS_SERVICE } from "./src-BL4AomX5.mjs";
2
2
  import { TUI_STARTUP_SERVICE } from "./startup.mjs";
3
3
  import { readFileSync } from "node:fs";
4
4
  import { join } from "node:path";
@@ -1,3 +1,3 @@
1
- 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";
1
+ 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-BL4AomX5.mjs";
2
2
  import "./startup.mjs";
3
3
  export { API_VERSION, PI_TUI_EXTENSIONS_SERVICE, apply, describeKey, inject, name };
package/dist/index.d.mts CHANGED
@@ -86,36 +86,6 @@ interface DraftImageStoreLike {
86
86
  values(): readonly DraftImage[];
87
87
  }
88
88
  //#endregion
89
- //#region src/diag.d.ts
90
- interface Diag {
91
- debug(message: string, fields?: Record<string, unknown>): void;
92
- info(message: string, fields?: Record<string, unknown>): void;
93
- warn(message: string, fields?: Record<string, unknown>): void;
94
- error(message: string, fields?: Record<string, unknown>): void;
95
- /** Release the file handle, if one is open. */
96
- dispose(): void;
97
- }
98
- //#endregion
99
- //#region src/tui-app.d.ts
100
- /** The compaction lifecycle phase the working row advertises: idle (no
101
- * compaction), summarizing (compaction/start seen, the summary is being
102
- * generated), or applying (the summary landed, the compacted surface is
103
- * being committed). Derived by the runner from compaction/start →
104
- * compaction/summary → compaction/end (foldCompactionEvent). */
105
- type CompactionPhase = 'idle' | 'summarizing' | 'applying';
106
- /** One queued inbox row for the queue pane (mirrors the agent Inbox's lists). */
107
- interface QueueItem {
108
- /** The pending message id (agent inbox identity). */
109
- id: string;
110
- /** The message text, single-line display form. */
111
- text: string;
112
- /** next-turn followup vs next-step steer. */
113
- mode: 'followup' | 'steer';
114
- /** Plugin notice (e.g. a background-job completion): NOT steerable — it
115
- * renders with its own marker and the hint drops the steer verbs. */
116
- notice?: boolean;
117
- }
118
- //#endregion
119
89
  //#region src/skill-catalog.d.ts
120
90
  /**
121
91
  * The standing-scope skill catalog adapter: the SINGLE narrow seam between
@@ -153,6 +123,36 @@ interface HumanSkillCatalog {
153
123
  readonly complete: boolean;
154
124
  }
155
125
  //#endregion
126
+ //#region src/diag.d.ts
127
+ interface Diag {
128
+ debug(message: string, fields?: Record<string, unknown>): void;
129
+ info(message: string, fields?: Record<string, unknown>): void;
130
+ warn(message: string, fields?: Record<string, unknown>): void;
131
+ error(message: string, fields?: Record<string, unknown>): void;
132
+ /** Release the file handle, if one is open. */
133
+ dispose(): void;
134
+ }
135
+ //#endregion
136
+ //#region src/tui-app.d.ts
137
+ /** The compaction lifecycle phase the working row advertises: idle (no
138
+ * compaction), summarizing (compaction/start seen, the summary is being
139
+ * generated), or applying (the summary landed, the compacted surface is
140
+ * being committed). Derived by the runner from compaction/start →
141
+ * compaction/summary → compaction/end (foldCompactionEvent). */
142
+ type CompactionPhase = 'idle' | 'summarizing' | 'applying';
143
+ /** One queued inbox row for the queue pane (mirrors the agent Inbox's lists). */
144
+ interface QueueItem {
145
+ /** The pending message id (agent inbox identity). */
146
+ id: string;
147
+ /** The message text, single-line display form. */
148
+ text: string;
149
+ /** next-turn followup vs next-step steer. */
150
+ mode: 'followup' | 'steer';
151
+ /** Plugin notice (e.g. a background-job completion): NOT steerable — it
152
+ * renders with its own marker and the hint drops the steer verbs. */
153
+ notice?: boolean;
154
+ }
155
+ //#endregion
156
156
  //#region src/surface-catalog.d.ts
157
157
  /** One effective command's discovery metadata (the official descriptor's
158
158
  * display fields; never a handler or a definition). */
@@ -584,17 +584,6 @@ declare function runningProfile(argv?: readonly string[], fallback?: string): st
584
584
  * @returns the resume command line, or undefined without a session.
585
585
  */
586
586
  declare function resumeCommand(profile: string, sessionId: string): string | undefined;
587
- /**
588
- * A launch-time open-lock refusal: the requested session is held by another
589
- * live dsh process (or its lock cannot be verified). Unlike a stale/missing
590
- * session id, this is NOT recoverable by falling back to a fresh session —
591
- * the user asked for a specific session and must resolve the holder first.
592
- * Thrown from the resume path and re-thrown past the resume catch so the
593
- * runner exits with the refusal as the error message.
594
- */
595
- declare class SessionLockRefusedError extends Error {
596
- constructor(message: string);
597
- }
598
587
  /** One fold of a compaction lifecycle event over the runner's in-flight
599
588
  * compaction state. Pure (the firehose applies the returned surface
600
589
  * effects): dsh-compaction is not a peer, so the event is read
@@ -762,4 +751,4 @@ declare function recomposeBlank(ctx: Context, agent: {
762
751
  */
763
752
  declare function apply(ctx: Context, config: Config): void;
764
753
  //#endregion
765
- export { AgentComposition, CompactionFold, CompactionSettleSurface, Config, HOST_COMMAND_CATALOG, InitialCatalogResolution, InterruptAgentLike, InterruptWriterLike, LOCAL_COMMANDS, PendingSubagentCall, QueueFoldResult, QueueInboxMessage, QueueNoticeSource, RecomposableSession, RecomposeOutcome, ResolveInitialCatalogOptions, SESSIONLESS_COMMANDS, SessionLockRefusedError, ViewerOpenToken, 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 };
754
+ export { AgentComposition, CompactionFold, CompactionSettleSurface, Config, HOST_COMMAND_CATALOG, InitialCatalogResolution, InterruptAgentLike, InterruptWriterLike, LOCAL_COMMANDS, PendingSubagentCall, QueueFoldResult, QueueInboxMessage, QueueNoticeSource, RecomposableSession, RecomposeOutcome, ResolveInitialCatalogOptions, SESSIONLESS_COMMANDS, ViewerOpenToken, 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 };
package/dist/index.mjs CHANGED
@@ -1,3 +1,3 @@
1
- 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-CeGK2mHo.mjs";
1
+ import { A as shouldSteerOnEnter, C as recomposeBlank, D as runningProfile, E as resumeCommand, F as viewerActionCapability, L as forkSeed, M as subagentJobViewHint, N as subagentNoticeIsFailure, O as settleCompactionSurface, P as teardownViewerForSessionSwap, S as normalizeSkillInvocation, T as resolveInitialCatalog, _ as isPlainExitPrompt, a as apply, b as matchPendingSubagentCall, c as compactingFromLog, d as createViewerOpenToken, f as dangerCommand, g as interruptAgent, h as inject, i as SESSIONLESS_COMMANDS, j as subagentJobTranscriptId, k as shouldConsumeAdvertisedMiss, l as composeAgent, m as foldQueueRows, n as HOST_COMMAND_CATALOG, o as busyAfterTurnBoundary, p as foldCompactionEvent, r as LOCAL_COMMANDS, s as commandRejectsImages, t as Config, u as contextRefreshKind, v as isSubagentSettlementNotice, w as recordedPreset, x as name, y as isUserQueueInput } from "./src-BL4AomX5.mjs";
2
2
  import "./startup.mjs";
3
- 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 };
3
+ export { Config, HOST_COMMAND_CATALOG, LOCAL_COMMANDS, SESSIONLESS_COMMANDS, 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 };