@xth26/dsh-plan-build-mode 0.3.0 → 0.3.1

package/README.md

@@ -1,175 +1,139 @@
-# dsh-plan-build-mode
-
-OpenCode-style Plan / Build hard permission model for DeepSeek Harness.
-
-This plugin adds an independent Plan/Build mode switch to DSH:
-
-- **Plan mode** enforces a `read-only` sandbox and blocks mutating tools (`write`, `edit`).
-- **Build mode** restores `workspace-write` and allows edits.
-- DSH's built-in `/plan` soft-guidance mode is left untouched.
-
-The tool denial only takes effect when Plan mode is configured as `read-only`. When the session has not been switched, Build mode is active by default.
-
-## Installation
-
-DSH plugins are loaded through a DSH profile. Install the plugin into the profile(s) you use:
-
-```bash
-# For the web profile
-dsh plugin --profile web add @xth26/dsh-plan-build-mode
-
-# For the TUI profile
-dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode
-```
-
-The plugin ships with a `cordis.patch.yml` that auto-injects the required row
-when the package is loaded by a DSH profile.
-
-## Using the same Plan/Build mode in both web and TUI
-
-Plan/Build mode state is stored in the session event log (`sandbox/mode` event). Both `dsh web` and `dsh --profile <name>` use the same session store when they share the same profile and session ID.
-
-- **Same profile**: if you run `dsh web --profile web` and `dsh --profile web`, the mode is shared because the session events are shared.
-- **Different profiles**: by default `web` and `dsh-tui` are separate profiles with separate session directories. Switching in one does **not** affect the other.
-
-To make web and TUI share the same mode and session history, use the **same profile** for both:
-
-```bash
-# Use the web profile for both interfaces
-dsh web --profile web
-dsh --profile web
-```
-
-Or, if you prefer to keep separate profiles but want to share only the session store, override the session root in each profile's `cordis.patch.yml` to point to the same directory:
-
-```yaml
-- id: session-root
-  config:
-    root: /path/to/shared/sessions
-```
-
-Note: sharing session directories across profiles requires both profiles to mount compatible service bundles; otherwise event interpretation may differ.
-
-## Local development / link
-
-To try the plugin from a local checkout without publishing:
-
-```bash
-# From the plugin checkout
-cd /path/to/dsh-plan-build-mode
-pnpm link --global
-
-# From your DSH profile directory
-pnpm link --global @xth26/dsh-plan-build-mode
-```
-
-Then start DSH with that profile. The `dsh.bundle.patch` field in the plugin's
-`package.json` makes the patch apply automatically.
-
-## Updating
-
-For `0.x` versions, the semver range `^0.1.0` only matches `0.1.x` and will **never** auto-update to `0.2.0`. Always bump the declaration explicitly and restart the DSH process:
-
-```bash
-# Bump the installed version in the target profile
-# (run this outside a sandboxed agent session; the profile directory is not writable from DSH)
-dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@0.2.3
-
-# Restart the DSH process that uses that profile
-# (old Node process still holds the previous plugin code in memory)
-Stop-Process -Name dsh -Force   # PowerShell
-# or: taskkill /IM dsh.exe /F   # CMD
-```
-
-Then start `dsh web` or `dsh tui` again. To always pull the latest published version:
-
-```bash
-dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@latest
-```
-
-## Usage
-
-| Command | Effect |
-|---|---|
-| `/plan-build` | Toggle between Plan and Build modes |
-| `/plan-build status` | Show the current mode |
-| `/plan-build switch plan` | Enter Plan mode (read-only) |
-| `/plan-build switch build` | Enter Build mode (writable) |
-| `/plan-build switch` | Same as `/plan-build`; toggles between modes |
-
-## Keyboard shortcuts
-
-`Ctrl+Alt+Shift+P` toggles between Plan and Build mode (the same action as
-bare `/plan-build`) in both frontends:
-
-- **dsh-tui** — bound through the plugin shortcut registry (`ctx.tuiShortcuts`).
-  It matches only in the plain chat state; overlays and pickers own the
-  keyboard while open.
-- **dsh web** — a global keydown listener runs `/plan-build` against the
-  current session. Inert while no session is open and during IME composition.
-
-The combo is deliberately complex (three modifiers) so it collides with no
-terminal, browser, or OS built-in. Change it with the `shortcut` config key,
-which accepts a single string or an array:
-
-```yaml
-- id: plan-build-mode
-  name: '@xth26/dsh-plan-build-mode'
-  config:
-    shortcut: ['ctrl+alt+shift+p', 'alt+p']
-```
-
-Combos use the `ctrl+alt+shift+p` grammar and must include Ctrl or Alt. The
-TUI refuses combos reserved by its built-in keymap (with a warning; the plugin
-keeps running).
-
-## Configuration
-
-```yaml
-- id: plan-build-mode
-  name: '@xth26/dsh-plan-build-mode'
-  config:
-    planSandbox: read-only
-    buildSandbox: workspace-write
-    denyWriteTools: true
-    section: true
-```
-
-`planSandbox` and `buildSandbox` must differ.
-
-## Plan mode: command-line Python for inspection
-
-While Plan mode is read-only and blocks `write`/`edit` tools, it is **encouraged** to run short, read-only command-line Python snippets to inspect data and validate assumptions. For example:
-
-```bash
-python -B -c "import json, sys; data = json.load(open('data/sample.json')); print(len(data))"
-python -B -c "import pandas as pd; print(pd.read_csv('data.csv').describe())"
-pytest -p no:cacheprovider -q tests/test_sanity.py
-```
-
-Use `-B` (or set `PYTHONDONTWRITEBYTECODE=1`) and `pytest -p no:cacheprovider` to avoid writing `__pycache__` or `.pytest_cache`. The read-only sandbox is the final guardrail; any command that tries to write files will still be blocked at the sandbox layer.
-
-## Local integration check
-
-After installing/linking the plugin in a DSH profile:
-
-1. Start DSH with that profile.
-2. Run `/plan-build` to enter Plan mode (read-only). You should see a confirmation.
-3. Ask the agent to call the `write` tool. It should be denied with a reason.
-4. Run `/plan-build` again to enter Build mode (writable). You should see a confirmation.
-5. Ask the agent to call `write` again. It should now be allowed.
-6. Run `/plan-build status` to check the current mode without switching.
-
-## Changelog
-
-### 0.3.0 (unreleased)
-
-- Add a Plan/Build toggle keyboard shortcut (`Ctrl+Alt+Shift+P` by default) in
-  both the TUI (`ctx.tuiShortcuts`) and the web frontend (global keydown). The
-  shortcut executes `/plan-build`, so mode state, lifecycle events and grants
-  stay single-source. Configurable via the new `shortcut` config key (a string
-  or an array of combos).
-
-## License
-
-MIT
+# dsh-plan-build-mode
+
+OpenCode-style Plan / Build hard permission model for DeepSeek Harness.
+
+This plugin adds an independent Plan/Build mode switch to DSH:
+
+- **Plan mode** enforces a `read-only` sandbox and blocks mutating tools (`write`, `edit`).
+- **Build mode** restores `workspace-write` and allows edits.
+- DSH's built-in `/plan` soft-guidance mode is left untouched.
+
+The tool denial only takes effect when Plan mode is configured as `read-only`. When the session has not been switched, Build mode is active by default.
+
+## Installation
+
+DSH plugins are loaded through a DSH profile. Install the plugin into the profile(s) you use:
+
+```bash
+# For the web profile
+dsh plugin --profile web add @xth26/dsh-plan-build-mode
+
+# For the TUI profile
+dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode
+```
+
+The plugin ships with a `cordis.patch.yml` that auto-injects the required row
+when the package is loaded by a DSH profile.
+
+## Using the same Plan/Build mode in both web and TUI
+
+Plan/Build mode state is stored in the session event log (`sandbox/mode` event). Both `dsh web` and `dsh --profile <name>` use the same session store when they share the same profile and session ID.
+
+- **Same profile**: if you run `dsh web --profile web` and `dsh --profile web`, the mode is shared because the session events are shared.
+- **Different profiles**: by default `web` and `dsh-tui` are separate profiles with separate session directories. Switching in one does **not** affect the other.
+
+To make web and TUI share the same mode and session history, use the **same profile** for both:
+
+```bash
+# Use the web profile for both interfaces
+dsh web --profile web
+dsh --profile web
+```
+
+Or, if you prefer to keep separate profiles but want to share only the session store, override the session root in each profile's `cordis.patch.yml` to point to the same directory:
+
+```yaml
+- id: session-root
+  config:
+    root: /path/to/shared/sessions
+```
+
+Note: sharing session directories across profiles requires both profiles to mount compatible service bundles; otherwise event interpretation may differ.
+
+## Local development / link
+
+To try the plugin from a local checkout without publishing:
+
+```bash
+# From the plugin checkout
+cd /path/to/dsh-plan-build-mode
+pnpm link --global
+
+# From your DSH profile directory
+pnpm link --global @xth26/dsh-plan-build-mode
+```
+
+Then start DSH with that profile. The `dsh.bundle.patch` field in the plugin's
+`package.json` makes the patch apply automatically.
+
+## Updating
+
+For `0.x` versions, the semver range `^0.1.0` only matches `0.1.x` and will **never** auto-update to `0.2.0`. Always bump the declaration explicitly and restart the DSH process:
+
+```bash
+# Bump the installed version in the target profile
+# (run this outside a sandboxed agent session; the profile directory is not writable from DSH)
+dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@0.3.1
+
+# Restart the DSH process that uses that profile
+# (old Node process still holds the previous plugin code in memory)
+Stop-Process -Name dsh -Force   # PowerShell
+# or: taskkill /IM dsh.exe /F   # CMD
+```
+
+Then start `dsh web` or `dsh tui` again. To always pull the latest published version:
+
+```bash
+dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@latest
+```
+
+## Usage
+
+| Command | Effect |
+|---|---|
+| `/plan-build` | Toggle between Plan and Build modes |
+| `/plan-build status` | Show the current mode |
+| `/plan-build switch plan` | Enter Plan mode (read-only) |
+| `/plan-build switch build` | Enter Build mode (writable) |
+| `/plan-build switch` | Same as `/plan-build`; toggles between modes |
+
+## Configuration
+
+```yaml
+- id: plan-build-mode
+  name: '@xth26/dsh-plan-build-mode'
+  config:
+    planSandbox: read-only
+    buildSandbox: workspace-write
+    denyWriteTools: true
+    section: true
+```
+
+`planSandbox` and `buildSandbox` must differ.
+
+## Plan mode: command-line Python for inspection
+
+While Plan mode is read-only and blocks `write`/`edit` tools, it is **encouraged** to run short, read-only command-line Python snippets to inspect data and validate assumptions. For example:
+
+```bash
+python -B -c "import json, sys; data = json.load(open('data/sample.json')); print(len(data))"
+python -B -c "import pandas as pd; print(pd.read_csv('data.csv').describe())"
+pytest -p no:cacheprovider -q tests/test_sanity.py
+```
+
+Use `-B` (or set `PYTHONDONTWRITEBYTECODE=1`) and `pytest -p no:cacheprovider` to avoid writing `__pycache__` or `.pytest_cache`. The read-only sandbox is the final guardrail; any command that tries to write files will still be blocked at the sandbox layer.
+
+## Local integration check
+
+After installing/linking the plugin in a DSH profile:
+
+1. Start DSH with that profile.
+2. Run `/plan-build` to enter Plan mode (read-only). You should see a confirmation.
+3. Ask the agent to call the `write` tool. It should be denied with a reason.
+4. Run `/plan-build` again to enter Build mode (writable). You should see a confirmation.
+5. Ask the agent to call `write` again. It should now be allowed.
+6. Run `/plan-build status` to check the current mode without switching.
+
+## License
+
+MIT

package/README.zh.md

@@ -1,160 +1,136 @@
-# dsh-plan-build-mode
-
-OpenCode 风格的 Plan / Build 硬权限模型插件。
-
-本插件为 DSH 增加一个独立的 Plan/Build 模式切换，不影响 DSH 原生的 `/plan` 软提示模式：
-
-- **Plan 模式**：强制 `read-only` 沙箱，并拦截写工具（`write`、`edit`）。
-- **Build 模式**：恢复 `workspace-write`，允许编辑。
-
-写工具拦截仅在 Plan 模式配置为 `read-only` 时生效。首次使用或未切换时，默认处于 Build 模式。
-
-## 安装
-
-DSH 插件通过 DSH profile 加载。把它装到你实际使用的 profile 里：
-
-```bash
-# 装到 web profile
-dsh plugin --profile web add @xth26/dsh-plan-build-mode
-
-# 装到 TUI profile
-dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode
-```
-
-插件自带的 `cordis.patch.yml` 会在 DSH profile 加载时自动注入。
-
-## 让 Web 和 TUI 共享同一个 Plan/Build 模式
-
-Plan/Build 模式状态存在会话事件日志里（`sandbox/mode` 事件）。`dsh web` 和 `dsh --profile <名称>` 只有在共用同一个 profile、同一个 session ID 时，才会读写同一个会话事件流。
-
-- **同一个 profile**：比如 `dsh web --profile web` 和 `dsh --profile web` 启动的两个入口，会共享 session 事件，因此模式切换会同步生效。
-- **不同 profile**：默认 `web` 和 `dsh-tui` 是两个独立 profile，会话目录也分开。在一处切换不会影响另一处。
-
-想让 web 和 TUI 共享模式状态，最简单的方法是**两个入口都使用同一个 profile**：
-
-```bash
-# 两个入口都用 web profile
-dsh web --profile web
-dsh --profile web
-```
-
-如果你确实想用不同 profile，但只想共享会话存储，可以在每个 profile 的 `cordis.patch.yml` 里把 session root 指向同一个目录：
-
-```yaml
-- id: session-root
-  config:
-    root: /path/to/shared/sessions
-```
-
-注意：跨 profile 共享会话目录要求两个 profile 挂载的服务组合兼容，否则事件解释可能出现差异。
-
-## 本地开发 / link 试用
-
-想在发布前从本地源码试用：
-
-```bash
-# 在插件目录
-cd /path/to/dsh-plan-build-mode
-pnpm link --global
-
-# 在你的 DSH profile 目录
-pnpm link --global @xth26/dsh-plan-build-mode
-```
-
-然后启动 DSH。插件 `package.json` 里的 `dsh.bundle.patch` 会自动生效。
-
-## 更新
-
-对于 `0.x` 版本，semver 范围 `^0.1.0` 只会匹配 `0.1.x`，**永远不会**自动更新到 `0.2.0`。升级时必须显式提升声明并重启 DSH 进程：
-
-```bash
-# 在目标 profile 中提升已安装版本
-# （这条命令需要在非沙箱的终端里执行；DSH agent 无法写入 profile 目录）
-dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@0.2.3
-
-# 重启使用该 profile 的 DSH 进程
-# （旧的 Node 进程仍缓存着旧插件代码）
-Stop-Process -Name dsh -Force   # PowerShell
-# 或: taskkill /IM dsh.exe /F   # CMD
-```
-
-然后重新启动 `dsh web` 或 `dsh tui`。如果想始终安装最新发布版本：
-
-```bash
-dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@latest
-```
-
-## 使用
-
-| 命令 | 效果 |
-|---|---|
-| `/plan-build` | 在 Plan 与 Build 模式之间切换 |
-| `/plan-build status` | 显示当前模式 |
-| `/plan-build switch plan` | 进入 Plan 模式（只读） |
-| `/plan-build switch build` | 进入 Build 模式（可写） |
-| `/plan-build switch` | 同 `/plan-build`，切换当前模式 |
-
-## 快捷键
-
-`Ctrl+Alt+Shift+P` 在两个前端里都能切换 Plan / Build 模式（等同裸 `/plan-build`）：
-
-- **dsh-tui** — 通过插件快捷键注册表（`ctx.tuiShortcuts`）绑定。仅在普通聊天态生效；弹层/选择器打开时会独占键盘。
-- **dsh web** — 全局 keydown 监听对当前会话执行 `/plan-build`。无会话打开或处于输入法组合期间不生效。
-
-组合键刻意做得复杂（三个修饰键），不会与终端、浏览器或系统的内置快捷键冲突。可通过 `shortcut` 配置修改，支持单个字符串或数组：
-
-```yaml
-- id: plan-build-mode
-  name: '@xth26/dsh-plan-build-mode'
-  config:
-    shortcut: ['ctrl+alt+shift+p', 'alt+p']
-```
-
-组合键遵循 `ctrl+alt+shift+p` 语法，必须包含 Ctrl 或 Alt。TUI 会拒绝与其内置键位表冲突的组合（仅警告，插件照常运行）。
-
-## 配置
-
-```yaml
-- id: plan-build-mode
-  name: '@xth26/dsh-plan-build-mode'
-  config:
-    planSandbox: read-only
-    buildSandbox: workspace-write
-    denyWriteTools: true
-    section: true
-```
-
-`planSandbox` 和 `buildSandbox` 必须不同。
-
-## Plan 模式：命令行 Python 做数据检查
-
-Plan 模式只读并拦截 `write`/`edit` 工具，但**鼓励**在命令行里跑简短、只读的 Python 片段来读数据和验证假设。例如：
-
-```bash
-python -B -c "import json, sys; data = json.load(open('data/sample.json')); print(len(data))"
-python -B -c "import pandas as pd; print(pd.read_csv('data.csv').describe())"
-pytest -p no:cacheprovider -q tests/test_sanity.py
-```
-
-使用 `-B`（或设置 `PYTHONDONTWRITEBYTECODE=1`）以及 `pytest -p no:cacheprovider`，避免写入 `__pycache__` 或 `.pytest_cache`。read-only 沙箱仍是最终防线，任何试图写文件的命令仍会在沙箱层被拒绝。
-
-## 本地集成验证
-
-安装或 link 插件到 DSH profile 后：
-
-1. 启动 DSH。
-2. 输入 `/plan-build`，应提示进入 Plan 模式。
-3. 让 agent 调用 `write` 工具，应被拒绝。
-4. 再次输入 `/plan-build`，应提示进入 Build 模式。
-5. 再次让 agent 调用 `write`，应允许执行。
-6. 输入 `/plan-build status`，可只查看当前模式而不切换。
-
-## 变更日志
-
-### 0.3.0（未发布）
-
-- 在 TUI（`ctx.tuiShortcuts`）与 web 前端（全局 keydown）都新增 Plan / Build 切换快捷键（默认 `Ctrl+Alt+Shift+P`）。快捷键执行 `/plan-build`，因此模式状态、生命周期事件与授权保持单一来源。可通过新增的 `shortcut` 配置键自定义（单个字符串或组合数组）。
-
-## 许可证
-
-MIT
+# dsh-plan-build-mode
+
+OpenCode 风格的 Plan / Build 硬权限模型插件。
+
+本插件为 DSH 增加一个独立的 Plan/Build 模式切换，不影响 DSH 原生的 `/plan` 软提示模式：
+
+- **Plan 模式**：强制 `read-only` 沙箱，并拦截写工具（`write`、`edit`）。
+- **Build 模式**：恢复 `workspace-write`，允许编辑。
+
+写工具拦截仅在 Plan 模式配置为 `read-only` 时生效。首次使用或未切换时，默认处于 Build 模式。
+
+## 安装
+
+DSH 插件通过 DSH profile 加载。把它装到你实际使用的 profile 里：
+
+```bash
+# 装到 web profile
+dsh plugin --profile web add @xth26/dsh-plan-build-mode
+
+# 装到 TUI profile
+dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode
+```
+
+插件自带的 `cordis.patch.yml` 会在 DSH profile 加载时自动注入。
+
+## 让 Web 和 TUI 共享同一个 Plan/Build 模式
+
+Plan/Build 模式状态存在会话事件日志里（`sandbox/mode` 事件）。`dsh web` 和 `dsh --profile <名称>` 只有在共用同一个 profile、同一个 session ID 时，才会读写同一个会话事件流。
+
+- **同一个 profile**：比如 `dsh web --profile web` 和 `dsh --profile web` 启动的两个入口，会共享 session 事件，因此模式切换会同步生效。
+- **不同 profile**：默认 `web` 和 `dsh-tui` 是两个独立 profile，会话目录也分开。在一处切换不会影响另一处。
+
+想让 web 和 TUI 共享模式状态，最简单的方法是**两个入口都使用同一个 profile**：
+
+```bash
+# 两个入口都用 web profile
+dsh web --profile web
+dsh --profile web
+```
+
+如果你确实想用不同 profile，但只想共享会话存储，可以在每个 profile 的 `cordis.patch.yml` 里把 session root 指向同一个目录：
+
+```yaml
+- id: session-root
+  config:
+    root: /path/to/shared/sessions
+```
+
+注意：跨 profile 共享会话目录要求两个 profile 挂载的服务组合兼容，否则事件解释可能出现差异。
+
+## 本地开发 / link 试用
+
+想在发布前从本地源码试用：
+
+```bash
+# 在插件目录
+cd /path/to/dsh-plan-build-mode
+pnpm link --global
+
+# 在你的 DSH profile 目录
+pnpm link --global @xth26/dsh-plan-build-mode
+```
+
+然后启动 DSH。插件 `package.json` 里的 `dsh.bundle.patch` 会自动生效。
+
+## 更新
+
+对于 `0.x` 版本，semver 范围 `^0.1.0` 只会匹配 `0.1.x`，**永远不会**自动更新到 `0.2.0`。升级时必须显式提升声明并重启 DSH 进程：
+
+```bash
+# 在目标 profile 中提升已安装版本
+# （这条命令需要在非沙箱的终端里执行；DSH agent 无法写入 profile 目录）
+dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@0.3.1
+
+# 重启使用该 profile 的 DSH 进程
+# （旧的 Node 进程仍缓存着旧插件代码）
+Stop-Process -Name dsh -Force   # PowerShell
+# 或: taskkill /IM dsh.exe /F   # CMD
+```
+
+然后重新启动 `dsh web` 或 `dsh tui`。如果想始终安装最新发布版本：
+
+```bash
+dsh plugin --profile dsh-tui add @xth26/dsh-plan-build-mode@latest
+```
+
+## 使用
+
+| 命令 | 效果 |
+|---|---|
+| `/plan-build` | 在 Plan 与 Build 模式之间切换 |
+| `/plan-build status` | 显示当前模式 |
+| `/plan-build switch plan` | 进入 Plan 模式（只读） |
+| `/plan-build switch build` | 进入 Build 模式（可写） |
+| `/plan-build switch` | 同 `/plan-build`，切换当前模式 |
+
+## 配置
+
+```yaml
+- id: plan-build-mode
+  name: '@xth26/dsh-plan-build-mode'
+  config:
+    planSandbox: read-only
+    buildSandbox: workspace-write
+    denyWriteTools: true
+    section: true
+```
+
+`planSandbox` 和 `buildSandbox` 必须不同。
+
+## Plan 模式：命令行 Python 做数据检查
+
+Plan 模式只读并拦截 `write`/`edit` 工具，但**鼓励**在命令行里跑简短、只读的 Python 片段来读数据和验证假设。例如：
+
+```bash
+python -B -c "import json, sys; data = json.load(open('data/sample.json')); print(len(data))"
+python -B -c "import pandas as pd; print(pd.read_csv('data.csv').describe())"
+pytest -p no:cacheprovider -q tests/test_sanity.py
+```
+
+使用 `-B`（或设置 `PYTHONDONTWRITEBYTECODE=1`）以及 `pytest -p no:cacheprovider`，避免写入 `__pycache__` 或 `.pytest_cache`。read-only 沙箱仍是最终防线，任何试图写文件的命令仍会在沙箱层被拒绝。
+
+## 本地集成验证
+
+安装或 link 插件到 DSH profile 后：
+
+1. 启动 DSH。
+2. 输入 `/plan-build`，应提示进入 Plan 模式。
+3. 让 agent 调用 `write` 工具，应被拒绝。
+4. 再次输入 `/plan-build`，应提示进入 Build 模式。
+5. 再次让 agent 调用 `write`，应允许执行。
+6. 输入 `/plan-build status`，可只查看当前模式而不切换。
+
+## 许可证
+
+MIT

package/lib/helpers.d.ts

@@ -10,15 +10,6 @@ import type { ToolExecution } from '@deepseek-ai/dsh-tools';
 export declare const DEFAULT_PLAN_SANDBOX: SandboxMode;
 /** Default sandbox mode while Build mode is active. */
 export declare const DEFAULT_BUILD_SANDBOX: SandboxMode;
-/**
- * Default keyboard shortcut that toggles Plan/Build mode. Kept deliberately
- * complex (three modifiers) so it collides with no terminal or browser
- * built-in: the TUI reserved set (ctrl+c/d/e/a/u/k/w, ctrl+left/right,
- * ctrl+return, alt+return, alt+up, tab, …) and the built-in actions
- * (ctrl+v/r/g/o/t/a/p/e/l/q, …) are all single-modifier, and no browser or
- * OS binds ctrl+alt+shift+p.
- */
-export declare const DEFAULT_SHORTCUT = "ctrl+alt+shift+p";
 /** Tools forbidden while in Plan mode. */
 export declare const WRITE_TOOLS: Set<string>;
 /**

package/lib/helpers.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"helpers.d.ts","sourceRoot":"","sources":["../src/helpers.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,wBAAwB,CAAA;AACnD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,0BAA0B,CAAA;AAG3D,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAA;AAC5D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAA;AAE3D,sDAAsD;AACtD,eAAO,MAAM,oBAAoB,EAAE,WAAyB,CAAA;AAE5D,uDAAuD;AACvD,eAAO,MAAM,qBAAqB,EAAE,WAA+B,CAAA;AAEnE;;;;;;;GAOG;AACH,eAAO,MAAM,gBAAgB,qBAAqB,CAAA;AAElD,0CAA0C;AAC1C,eAAO,MAAM,WAAW,aAA6B,CAAA;AAErD;;;GAGG;AACH,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,SAAS,YAAY,EAAE,GAAG,WAAW,GAAG,SAAS,CAQ3F;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,SAAS,YAAY,EAAE,EAAE,WAAW,EAAE,WAAW,GAAG,OAAO,CAEnG;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,KAAK,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,EAAE,WAAW,EAAE,WAAW,EAAE,YAAY,EAAE,WAAW,GAAG,IAAI,CAGhI;AAED;;;;;;;;GAQG;AACH,wBAAgB,cAAc,CAC5B,IAAI,EAAE,aAAa,EACnB,WAAW,EAAE,WAAW,EACxB,UAAU,GAAE,WAAW,CAAC,MAAM,CAAe,GAC5C,MAAM,GAAG,SAAS,CAQpB"}
+{"version":3,"file":"helpers.d.ts","sourceRoot":"","sources":["../src/helpers.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,wBAAwB,CAAA;AACnD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,0BAA0B,CAAA;AAG3D,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAA;AAC5D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAA;AAE3D,sDAAsD;AACtD,eAAO,MAAM,oBAAoB,EAAE,WAAyB,CAAA;AAE5D,uDAAuD;AACvD,eAAO,MAAM,qBAAqB,EAAE,WAA+B,CAAA;AAEnE,0CAA0C;AAC1C,eAAO,MAAM,WAAW,aAA6B,CAAA;AAErD;;;GAGG;AACH,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,SAAS,YAAY,EAAE,GAAG,WAAW,GAAG,SAAS,CAQ3F;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,SAAS,YAAY,EAAE,EAAE,WAAW,EAAE,WAAW,GAAG,OAAO,CAEnG;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,KAAK,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,EAAE,WAAW,EAAE,WAAW,EAAE,YAAY,EAAE,WAAW,GAAG,IAAI,CAGhI;AAED;;;;;;;;GAQG;AACH,wBAAgB,cAAc,CAC5B,IAAI,EAAE,aAAa,EACnB,WAAW,EAAE,WAAW,EACxB,UAAU,GAAE,WAAW,CAAC,MAAM,CAAe,GAC5C,MAAM,GAAG,SAAS,CAQpB"}

package/lib/helpers.js

@@ -6,15 +6,6 @@
 export const DEFAULT_PLAN_SANDBOX = 'read-only';
 /** Default sandbox mode while Build mode is active. */
 export const DEFAULT_BUILD_SANDBOX = 'workspace-write';
-/**
- * Default keyboard shortcut that toggles Plan/Build mode. Kept deliberately
- * complex (three modifiers) so it collides with no terminal or browser
- * built-in: the TUI reserved set (ctrl+c/d/e/a/u/k/w, ctrl+left/right,
- * ctrl+return, alt+return, alt+up, tab, …) and the built-in actions
- * (ctrl+v/r/g/o/t/a/p/e/l/q, …) are all single-modifier, and no browser or
- * OS binds ctrl+alt+shift+p.
- */
-export const DEFAULT_SHORTCUT = 'ctrl+alt+shift+p';
 /** Tools forbidden while in Plan mode. */
 export const WRITE_TOOLS = new Set(['write', 'edit']);
 /**