dsh-ops 0.2.3 → 0.2.5-beta.1

package/CHANGELOG.md

@@ -5,6 +5,24 @@ All notable changes to this package are recorded here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.5-beta.1] — Automatic context compaction (prerelease candidate)
+
+- Add the fourth independent marketplace row, `@dsh-ops/auto-compact`, enabled by default; background remains opt-in. Bundle its internal companion package with dsh-ops so rc.2 discovers its browser face through a package-root row, with no separate publishing requirement.
+- Add a settings control on this row in the existing Plugins component region: live threshold (50%), cooldown (120 seconds) and compaction deadline (120 seconds), with revision-fenced profile writes and restore defaults.
+- Use the Web context-pressure projection and the same public `compactNow` API as `/compact`, only after a non-cancelled turn becomes idle; do not publish a model-callable compaction tool or modify the host's own automatic policy.
+- Serialize this component's compactions, suppress unchanged surfaces and self-generated replacements, back off failures, suspend sessions after commit/persistence failures, and abort/drain owned work on disable.
+- Keep host activation free of host value imports: a dependency-free Standard Schema descriptor and a scoped update hook retain validated live references. No Schemastery vendor impersonation.
+- Add targeted safety/lifecycle/schema/browser-registration regressions. Full historical gates still contain stale pre-0.2.4 expectations; no claim of a fully green legacy suite or live Desktop acceptance.
+
+## [0.2.4] — Independently toggled components
+
+- Split the market bundle into shell (on), file (on), and background (off) rows with exported per-component titles, descriptions, icons and locales.
+- Publish five tools by default, nine with background enabled. Stop publishing duplicate foreground ops_run. Preserve the bash/PowerShell 7 routing and the object-root bash schema.
+- Own separate prompt sections for each component; visibility and shutdown withdraw only the matching guidance/tools. Do not append to AGENTS.md.
+- Share one ref-counted plugin-owned FastCtx connection for file/background. Drain in-flight calls and attempt to kill only remembered owned jobs when background stops; report cleanup failures.
+- Replace the unconditional bundle pwshPath override with a runtime-only official config lifecycle overlay; shell OFF recomputes the executor's current owning raw config without persisting changes.
+- Document release-age version selection and the limits of token savings. No host/vendor implementation, old regression suite, or Actions changes.
+
 ## [0.2.3] — Strict-argument guidance and display metadata
 
 - Add one routing-section reminder: `ops_* arguments are strict: pass only declared fields.` Keep FastCtx's portable schema subset and runtime guards unchanged.

package/PROVENANCE.md

@@ -3,6 +3,30 @@
 What this repository is, where its parts came from, what was verified, and what
 was not.
 
+## 0.2.4 Component lifecycle
+
+Three exported subpath plugins replace the single bundle row: shell/file on by
+default, background off. Each owns its registrations and system-prompt section;
+file and background lease one plugin-owned MCP connection scoped to the Cordis root.
+No global host registry or service methods are replaced. Foreground ops_run is no
+longer published. Background shutdown drains tracked calls, attempts to kill only
+remembered job IDs, then releases its connection lease; disconnect can still lose
+ownership, so cleanup is not guaranteed for unknown durable jobs.
+
+The unconditional pwsh-sandbox patch is removed. Shell mounts an internal/config
+waterfall hook targeted at the official pwsh-sandbox row, then uses public
+Fiber.update(rawConfig, true) to apply/revoke the temporary path via the official
+config lifecycle (noSave). Removing the hook recomputes from the latest owning raw
+config, not a stale saved copy. It does not mutate a service/config reference, write
+profile files, change OS defaults or cancel existing host shell processes. An
+isolated real Cordis/ToolRuntime inspection verified independent tool/prompt
+withdrawal, permission-gated commands, shared-client leases, and config restoration
+with a stand-in executor. Real desktop marketplace toggles and the real sandbox
+executor require user validation; no model requests/old suites were run.
+
+Default schema bytes drop from 10,700 (0.2.3 ten tools) to 7,685 (five tools).
+This is a byte metric, not a tokenizer or proof of lower whole-task usage.
+
 ## 0.2.3 Prompt and display update
 
 Add one model-facing sentence in `lib/policy.js`: `ops_* arguments are strict:

package/README.en.md

@@ -8,6 +8,16 @@ Routing: **file tools → bash → PowerShell 7**. Prefer bash for general comma
 use pwsh only for necessary Windows-native operations. Fix bash errors in bash.
 Windows x64 only; target DSH `0.2.0-rc.2`. [中文](README.md)
 
+## Beta candidate
+
+`0.2.5-beta.1` adds the fourth component and its row configuration page. It is
+intended for the npm `beta` tag, without changing `latest`. Registry metadata is
+the authority for publication status. Once published, explicitly install
+`dsh-ops@0.2.5-beta.1` from the official npm registry. Exact version selection does
+not bypass pnpm's minimum release age: wait or narrowly exempt this version,
+never delete the lockfile or disable global policy. Fully quit/restart the app
+and verify the installed main version and four components.
+
 ## Install, update and remove
 
 In the official marketplace, enter **`dsh-ops`**, install, then enable. This installs
@@ -41,10 +51,12 @@ dsh plugin --profile dsh-tui add dsh-ops
 Update by repeating the npx install command, or official `add dsh-ops@latest`.
 Reload/restart as the application requests; replacing loaded code may require restart.
 
-The current version is `0.2.3`: it reminds the model to pass only declared `ops_*`
-fields and updates the display title, descriptions, and icon. It retains the 0.2.2
-bash parameter schema fix. Runtime dependencies remain pinned to `0.2.1`; their
-original release record is in [docs/release-0.2.1.md](docs/release-0.2.1.md).
+Version `0.2.4` adds three independently toggled components and retains the bash
+object-root schema fix and custom icon. Runtime dependencies remain at `0.2.1` and
+install automatically. Desktop pnpm's 24-hour release-age policy may show new metadata
+but select an older package for a bare name: specify `dsh-ops@0.2.4` from the official
+npm registry, confirm the installed version, then fully quit/restart. See the original
+[payload release record](docs/release-0.2.1.md).
 
 ```console
 npx --yes dsh-ops@latest status --profile desktop
@@ -56,11 +68,42 @@ also remove profile dependency references. Runtime files are package dependencie
 not a new shared provisioned directory. System shells, other profiles and package
 manager caches are never manually deleted. Clean legacy provisioned files separately
 with `npx --yes dsh-ops@latest uninstall --yes`; `~/.fastctx/` is kept unless
-`--purge-fastctx` is explicit. Unload/downgrade does not prove durable jobs stopped.
+`--purge-fastctx` is explicit. Background OFF drains in-flight calls and attempts to
+kill only jobs remembered by this component on its current connection; failures warn.
+Lost ownership after disconnect and permission downgrade do not guarantee termination.
+
+## Components and prompts
+
+| Component | Default | Capability |
+| --- | --- | --- |
+| dsh-ops-bash & powershell 7 | On | Prefer ops_bash for general commands; bundled PowerShell 7 for Windows-native work |
+| dsh-ops-file | On | Rust batch reads, search, path discovery and replacement |
+| dsh-ops-background | Off | Scientific simulations, model training and other long-running tasks |
+| Automatic context compaction | On | Idle-only host /compact service above a configurable Web context threshold; no additional model-facing tool |
+
+Each row owns its tools and runtime prompt section; OFF withdraws both. Nothing is
+appended to AGENTS.md. Shell ON adds a runtime-only configuration overlay for the
+stock pwsh-sandbox path; OFF recomputes its latest owning raw configuration via the
+official lifecycle, without writing profile files. It does not change the OS default
+terminal or cancel already-running host commands. File/background share one owned
+FastCtx connection; turning one off does not stop the other. Default tool count is
+five; duplicate ops_run is no longer published. Reduced fixed schema cost is not a
+promise of lower task-total tokens. Minimal's complete persona excludes extra sections;
+PTC invokes the tools through its generated SDK with unchanged permission checks.
 
 ## Configuration and tools
 
-Edit the dsh-ops row's `config` in the DSH configuration editor. Unknown keys fail.
+**Beta candidate feature:** the fourth row's configuration control is in
+Plugins → dsh-ops → Included components. Configure the threshold (default **50%**),
+cooldown (120 seconds) and timeout (120 seconds). The policy uses the Web meter,
+requires strictly more than the threshold, and waits for a non-cancelled idle turn.
+It uses revision-fenced host profile persistence and does not interrupt active tools.
+Summarization may call your model and incur cost. Disabling aborts/drains only owned
+compaction. Installed npm `0.2.4` does not yet include this feature. See
+[safety boundaries and validation](docs/auto-compact.md).
+
+Edit the corresponding dsh-ops/shell, dsh-ops/file or dsh-ops/background row's config.
+Unknown keys fail; normal component enablement is available in the marketplace.
 
 ```yaml
 config:
@@ -75,8 +118,8 @@ config:
   # bashPath: 'C:\tools\bash.exe'
 ```
 
-`enableShellTools` controls the FastCtx command/job group; `publishBashTool` controls
-bash. Both additionally require authoritative session `danger-full-access`; bash
+`enableShellTools` controls the background component's four run/job tools; file never
+publishes commands. `publishBashTool` controls bash. Both additionally require authoritative session `danger-full-access`; bash
 also requires the host subprocess service. `promptPolicy` controls compact routing;
 `extraGuidance` appends text. RPC wait timeout does not prove server termination.
 `required` fails activation on unavailable runtime. Explicit binary/bash paths are
@@ -90,7 +133,6 @@ authoritative. `shellPolicy: deny-host-shell` blocks `deniedHostTools` (default
 | ops_glob | Multiple path patterns and exclusions | No command gate¹ |
 | ops_replace | Mechanical cross-file replacement; host edit for precise edits | No command gate¹ |
 | ops_bash | Preferred general bash executor | Required |
-| ops_run | Bounded bash result | Required |
 | ops_run_background | Start background jobs | Required |
 | ops_job_output / ops_job_list / ops_job_kill | Operate on this session's owned jobs | Required |
 | Host pwsh | Bundled PowerShell 7 Windows-native operations | Host policy |

package/README.md

@@ -1,20 +1,28 @@
 # dsh-ops
 
-解决 Windows 下 DSH 反复使用 PowerShell 报错造成的 token、时间和模型注意力浪费。本插件提供：
+解决 Windows 下 DSH 反复使用 PowerShell 报错造成的 token、时间和模型注意力浪费。本插件的三个主要功能提供：
 
-- 独立 **bash 5.3.15**，用于通用命令、构建、Git、管道和脚本。
-- 独立 **PowerShell 7.6.6**，用于必要的 Windows 原生操作，沿用宿主 `pwsh` 工具。
-- Rust 编写的高性能增强工具，支持批量读取、搜索、替换和有界输出，减少不必要的输入输出。由于部分工具不经过 DSH 的受限终端后端，命令与后台任务工具只在**完全权限**时启用。
+- 提供独立 **bash 5.3.15** 并优先使用bash，让你的AI不再和PowerShell打架
+- 独立 **PowerShell 7.6.6**，用于必要的 Windows 原生操作，沿用宿主 `pwsh` 工具。PowerShell 7 比自带的 PowerShell 5 也有不少优化
+- 一些 Rust 编写的性能更好的，更快的读取、查找、替换工具，加速任务运行，减少不必要的输入输出。由于部分工具不经过 DSH 的受限终端后端，命令与后台任务工具只在**完全权限**时启用。
 
 执行顺序：**工具包 → bash → PowerShell 7**。bash 报错在 bash 内修正，不随意换 shell，不混用两套语法。
 
 仅支持 **Windows x64**；目标宿主 DSH `0.2.0-rc.2`。[English](README.en.md)
 
+## Beta 测试版候选
+
+`0.2.5-beta.1` 增加「上下文自动压缩」及其组件配置入口，默认阈值 50%。它仅计划发布到 npm 的 `beta` 标签；`latest` 保持正式版，不自动给普通用户升级。发布状态以 registry 查询为准，发布前不能据此认定包已在线。
+
+发布后在插件市场指定 **`dsh-ops@0.2.5-beta.1`**、选择 npm 官方源。精确指定版本**不会绕过** pnpm 的发布冷却策略；如被拦截，应等待冷却期结束或由用户对该精确版本设置豁免，不删除锁文件、不关闭全局供应链检查。安装后完全退出并重启应用，确认主包版本与四个组件。
+
 ## 安装、更新、卸载
 
 ### 官方插件市场
 
-在目标 DSH 应用的插件市场中输入 npm 包名 **`dsh-ops`**，安装后选择启用。安装归属于当前运行的 profile，桌面端为 `desktop`。发布包依赖完整 FastCtx、bash 和 PowerShell 7 载荷；不使用安装脚本下载，不改系统 PATH。
+在目标 DSH 应用的插件市场中输入 npm 包名 **`dsh-ops@0.2.4`**，安装后选择启用。安装归属于当前运行的 profile，桌面端为 `desktop`。发布包依赖完整 FastCtx、bash 和 PowerShell 7 载荷；不使用安装脚本下载，不改系统 PATH。
+
+注：新发布版本暂时明确写 dsh-ops@0.2.4，避免 pnpm 安全冷却期使裸包名选择旧版本。
 
 ### npm 一键安装
 
@@ -40,7 +48,7 @@ dsh plugin --profile dsh-tui add dsh-ops
 
 **更新**：重新运行相同的 `npx --yes dsh-ops@latest install --profile ...`，或用官方 CLI `add dsh-ops@latest`。按应用提示重载；替换已加载代码时重启应用。
 
-当前 npm 版本为 `0.2.3`：提示词提醒 `ops_*` 只传声明字段，标题统一为 `dsh-ops`，并更新中英文介绍和图标；保留 `0.2.2` 的 bash schema 修复，三个运行包仍使用 `0.2.1`。原始载荷发布记录见 [docs/release-0.2.1.md](docs/release-0.2.1.md)。
+当前版本 `0.2.4` 支持三个独立组件；bash 参数 schema 修复和自定义图标保留。三个二进制依赖继续使用 `0.2.1`，它们会自动安装，不影响主插件版本。新发布版本可能受桌面 pnpm 的 24 小时安全冷却策略影响：如果市场分析版号与安装结果不一致，指定 `dsh-ops@0.2.4` 并选择 npm 官方源，确认实际版本后完全退出并重启。原始载荷记录见 [docs/release-0.2.1.md](docs/release-0.2.1.md)。
 
 **卸载与查看状态**：
 
@@ -51,14 +59,32 @@ npx --yes dsh-ops@latest uninstall --profile desktop
 
 把 `desktop` 换成 `web` 或 `tui` 即可。也可在市场卸载，或执行官方 `dsh plugin --profile ... remove dsh-ops`。二进制随 profile 的插件依赖管理；卸载移除依赖引用，不误删系统 shell、其它 profile 的副本或包管理器共享缓存。
 
-旧版显式 provision 的 `<DSH_HOME>/dsh-ops/` 文件需单独清理：`npx --yes dsh-ops@latest uninstall --yes`。默认不删 `~/.fastctx/` 持久状态；需要时显式加 `--purge-fastctx`。卸载/降权不保证已经启动的持久后台任务终止，先处理自己的任务。
+旧版显式 provision 的 `<DSH_HOME>/dsh-ops/` 文件需单独清理：`npx --yes dsh-ops@latest uninstall --yes`。默认不删 `~/.fastctx/` 持久状态；需要时显式加 `--purge-fastctx`。关闭后台组件会等待已发出的调用，然后尝试终止该组件当前连接记住的自有任务；失败会告警。断线丢失归属的旧任务及单纯降权不保证终止，先处理自己的任务。
+
+## 组件开关与提示词
+
+官方市场显示四个组件，分别启停，首次安装默认开启 shell、file 和自动压缩：
+
+| 组件 | 介绍 | 默认 | 发布的工具 |
+| --- | --- | --- | --- |
+| `dsh-ops-bash & powershell 7` | 将默认终端改为bash，以及bash覆盖不到时提供powershell7 | 开 | `ops_bash`；宿主 `pwsh` 使用随包 PowerShell 7 |
+| `dsh-ops-file` | 更快、更高性能、输出更精简更省token的rust文件检索 | 开 | 四个文件工具 |
+| `dsh-ops-background` | 为科研仿真、模型训练及其他长进程后台任务提供托管 | 关 | 启动、输出、列出、终止后台任务 |
+| `上下文自动压缩` | Web 占用高于可设置阈值时，空闲后调用宿主 `/compact` 服务 | 开 | 自动策略，不新增模型工具 |
+
+“默认终端改为 bash”指模型提示优先使用 `ops_bash`，**不修改系统默认终端、PATH 或宿主原有 shell 工具名称**。Shell 组件开时，通过官方配置生命周期临时指定 `pwsh-sandbox` 的 PowerShell 7 路径；关时按执行器最新原配置恢复，不写 profile 配置。执行器配置切换不代表取消已在运行的宿主命令。
+
+提示词注册为独立运行时段，**不写 AGENTS.md**：Shell 关就撤销 bash/pwsh 路由；文件关就撤销检索说明；后台关就不发布后台工具及自有 job 指导。文件与后台共享一个插件拥有的 FastCtx 连接，关闭其中一个不关闭另一个。默认仅新增五个工具，不发布重复前台 `ops_run`。这些改变减少固定声明成本，**不保证任意任务总 token 降低**。极简预设会覆盖附加 system sections；PTC 模式经 SDK 调用底层工具，权限门不变。
 
 ## 配置方式与工具列表
 
-在 DSH 的配置编辑器中找到 `dsh-ops` 行，调整 `config` 后保存；未知配置键会点名报错。主要默认值：
+**Beta 测试版新增组件**：在上面的「包含的组件」中打开「上下文自动压缩」的配置入口，设置阈值（默认 **50%**）、冷却（120 秒）、超时（120 秒）。严格高于阈值、正常会话进入空闲后才触发，不打断运行中的工具；保存使用宿主 profile 持久化和版本冲突检查。压缩可能调用模型并产生费用。关闭组件会取消并等待它自己启动的压缩，不取消用户任务。该组件属于 `0.2.5-beta.1` 测试版候选，已安装的正式版 npm `0.2.4` 不含它；是否已发布请查 npm。详见[安全边界与验证记录](docs/auto-compact.md)。
+
+在 DSH 的配置编辑器中找到对应的 `dsh-ops/shell`、`dsh-ops/file` 或 `dsh-ops/background` 行，调整 `config` 后保存；未知配置键会点名报错。也可直接在市场切换组件。主要配置：
 
 ```yaml
 config:
+  # background component only; its market row is disabled by default
   enableShellTools: true
   publishBashTool: true
   promptPolicy: true
@@ -70,9 +96,9 @@ config:
   # bashPath: 'C:\tools\bash.exe'
 ```
 
-- `enableShellTools`：部署开关，开启仍须会话 `danger-full-access` 才发布 FastCtx 命令/job 组。
+- `enableShellTools`：后台组件的部署开关，开启仍须会话 `danger-full-access` 才发布四个后台工具；文件组件不发布命令工具。
 - `publishBashTool`：是否发布 `ops_bash`，同样要求完全权限和宿主 subprocess 服务。
-- `promptPolicy`：是否注入紧凑三层路由说明；可用 `extraGuidance` 追加指导。
+- `promptPolicy`：是否注入该组件的运行时说明；可用 `extraGuidance` 追加指导。
 - `toolCallTimeoutMs`：FastCtx RPC 等待超时，不代表服务端工作已终止。
 - `required`：运行时不可用时是否拒绝激活。
 - `shellPolicy`：默认 `advise`；`deny-host-shell` 拒绝 `deniedHostTools` 列表中的宿主 shell（默认 `[pwsh, bash, pwsh_persistent]`）。这也会禁用第三层 pwsh，谨慎开启。
@@ -85,7 +111,6 @@ config:
 | `ops_glob` | 多模式找路径，支持排除 | 无命令权限门¹ |
 | `ops_replace` | 跨文件批量替换；精确编辑仍用宿主 edit | 无命令权限门¹ |
 | `ops_bash` | 优先的通用 bash 命令执行器 | 是 |
-| `ops_run` | 有界 bash 命令结果 | 是 |
 | `ops_run_background` | 启动后台任务 | 是 |
 | `ops_job_output` / `ops_job_list` / `ops_job_kill` | 查看、列出、停止当前会话启动的任务 | 是 |
 | 宿主 `pwsh` | 使用随包 PowerShell 7 的 Windows 原生操作 | 沿用宿主策略 |

package/README.zh.md

@@ -1,20 +1,28 @@
 # dsh-ops
 
-解决 Windows 下 DSH 反复使用 PowerShell 报错造成的 token、时间和模型注意力浪费。本插件提供：
+解决 Windows 下 DSH 反复使用 PowerShell 报错造成的 token、时间和模型注意力浪费。本插件的三个主要功能提供：
 
-- 独立 **bash 5.3.15**，用于通用命令、构建、Git、管道和脚本。
-- 独立 **PowerShell 7.6.6**，用于必要的 Windows 原生操作，沿用宿主 `pwsh` 工具。
-- Rust 编写的高性能增强工具，支持批量读取、搜索、替换和有界输出，减少不必要的输入输出。由于部分工具不经过 DSH 的受限终端后端，命令与后台任务工具只在**完全权限**时启用。
+- 提供独立 **bash 5.3.15** 并优先使用bash，让你的AI不再和PowerShell打架
+- 独立 **PowerShell 7.6.6**，用于必要的 Windows 原生操作，沿用宿主 `pwsh` 工具。PowerShell 7 比自带的 PowerShell 5 也有不少优化
+- 一些 Rust 编写的性能更好的，更快的读取、查找、替换工具，加速任务运行，减少不必要的输入输出。由于部分工具不经过 DSH 的受限终端后端，命令与后台任务工具只在**完全权限**时启用。
 
 执行顺序：**工具包 → bash → PowerShell 7**。bash 报错在 bash 内修正，不随意换 shell，不混用两套语法。
 
 仅支持 **Windows x64**；目标宿主 DSH `0.2.0-rc.2`。[English](README.en.md)
 
+## Beta 测试版候选
+
+`0.2.5-beta.1` 增加「上下文自动压缩」及其组件配置入口，默认阈值 50%。它仅计划发布到 npm 的 `beta` 标签；`latest` 保持正式版，不自动给普通用户升级。发布状态以 registry 查询为准，发布前不能据此认定包已在线。
+
+发布后在插件市场指定 **`dsh-ops@0.2.5-beta.1`**、选择 npm 官方源。精确指定版本**不会绕过** pnpm 的发布冷却策略；如被拦截，应等待冷却期结束或由用户对该精确版本设置豁免，不删除锁文件、不关闭全局供应链检查。安装后完全退出并重启应用，确认主包版本与四个组件。
+
 ## 安装、更新、卸载
 
 ### 官方插件市场
 
-在目标 DSH 应用的插件市场中输入 npm 包名 **`dsh-ops`**，安装后选择启用。安装归属于当前运行的 profile，桌面端为 `desktop`。发布包依赖完整 FastCtx、bash 和 PowerShell 7 载荷；不使用安装脚本下载，不改系统 PATH。
+在目标 DSH 应用的插件市场中输入 npm 包名 **`dsh-ops@0.2.4`**，安装后选择启用。安装归属于当前运行的 profile，桌面端为 `desktop`。发布包依赖完整 FastCtx、bash 和 PowerShell 7 载荷；不使用安装脚本下载，不改系统 PATH。
+
+注：新发布版本暂时明确写 dsh-ops@0.2.4，避免 pnpm 安全冷却期使裸包名选择旧版本。
 
 ### npm 一键安装
 
@@ -40,7 +48,7 @@ dsh plugin --profile dsh-tui add dsh-ops
 
 **更新**：重新运行相同的 `npx --yes dsh-ops@latest install --profile ...`，或用官方 CLI `add dsh-ops@latest`。按应用提示重载；替换已加载代码时重启应用。
 
-当前 npm 版本为 `0.2.3`：提示词提醒 `ops_*` 只传声明字段，标题统一为 `dsh-ops`，并更新中英文介绍和图标；保留 `0.2.2` 的 bash schema 修复，三个运行包仍使用 `0.2.1`。原始载荷发布记录见 [docs/release-0.2.1.md](docs/release-0.2.1.md)。
+当前版本 `0.2.4` 支持三个独立组件；bash 参数 schema 修复和自定义图标保留。三个二进制依赖继续使用 `0.2.1`，它们会自动安装，不影响主插件版本。新发布版本可能受桌面 pnpm 的 24 小时安全冷却策略影响：如果市场分析版号与安装结果不一致，指定 `dsh-ops@0.2.4` 并选择 npm 官方源，确认实际版本后完全退出并重启。原始载荷记录见 [docs/release-0.2.1.md](docs/release-0.2.1.md)。
 
 **卸载与查看状态**：
 
@@ -51,14 +59,32 @@ npx --yes dsh-ops@latest uninstall --profile desktop
 
 把 `desktop` 换成 `web` 或 `tui` 即可。也可在市场卸载，或执行官方 `dsh plugin --profile ... remove dsh-ops`。二进制随 profile 的插件依赖管理；卸载移除依赖引用，不误删系统 shell、其它 profile 的副本或包管理器共享缓存。
 
-旧版显式 provision 的 `<DSH_HOME>/dsh-ops/` 文件需单独清理：`npx --yes dsh-ops@latest uninstall --yes`。默认不删 `~/.fastctx/` 持久状态；需要时显式加 `--purge-fastctx`。卸载/降权不保证已经启动的持久后台任务终止，先处理自己的任务。
+旧版显式 provision 的 `<DSH_HOME>/dsh-ops/` 文件需单独清理：`npx --yes dsh-ops@latest uninstall --yes`。默认不删 `~/.fastctx/` 持久状态；需要时显式加 `--purge-fastctx`。关闭后台组件会等待已发出的调用，然后尝试终止该组件当前连接记住的自有任务；失败会告警。断线丢失归属的旧任务及单纯降权不保证终止，先处理自己的任务。
+
+## 组件开关与提示词
+
+官方市场显示四个组件，分别启停，首次安装默认开启 shell、file 和自动压缩：
+
+| 组件 | 介绍 | 默认 | 发布的工具 |
+| --- | --- | --- | --- |
+| `dsh-ops-bash & powershell 7` | 将默认终端改为bash，以及bash覆盖不到时提供powershell7 | 开 | `ops_bash`；宿主 `pwsh` 使用随包 PowerShell 7 |
+| `dsh-ops-file` | 更快、更高性能、输出更精简更省token的rust文件检索 | 开 | 四个文件工具 |
+| `dsh-ops-background` | 为科研仿真、模型训练及其他长进程后台任务提供托管 | 关 | 启动、输出、列出、终止后台任务 |
+| `上下文自动压缩` | Web 占用高于可设置阈值时，空闲后调用宿主 `/compact` 服务 | 开 | 自动策略，不新增模型工具 |
+
+“默认终端改为 bash”指模型提示优先使用 `ops_bash`，**不修改系统默认终端、PATH 或宿主原有 shell 工具名称**。Shell 组件开时，通过官方配置生命周期临时指定 `pwsh-sandbox` 的 PowerShell 7 路径；关时按执行器最新原配置恢复，不写 profile 配置。执行器配置切换不代表取消已在运行的宿主命令。
+
+提示词注册为独立运行时段，**不写 AGENTS.md**：Shell 关就撤销 bash/pwsh 路由；文件关就撤销检索说明；后台关就不发布后台工具及自有 job 指导。文件与后台共享一个插件拥有的 FastCtx 连接，关闭其中一个不关闭另一个。默认仅新增五个工具，不发布重复前台 `ops_run`。这些改变减少固定声明成本，**不保证任意任务总 token 降低**。极简预设会覆盖附加 system sections；PTC 模式经 SDK 调用底层工具，权限门不变。
 
 ## 配置方式与工具列表
 
-在 DSH 的配置编辑器中找到 `dsh-ops` 行，调整 `config` 后保存；未知配置键会点名报错。主要默认值：
+**Beta 测试版新增组件**：在上面的「包含的组件」中打开「上下文自动压缩」的配置入口，设置阈值（默认 **50%**）、冷却（120 秒）、超时（120 秒）。严格高于阈值、正常会话进入空闲后才触发，不打断运行中的工具；保存使用宿主 profile 持久化和版本冲突检查。压缩可能调用模型并产生费用。关闭组件会取消并等待它自己启动的压缩，不取消用户任务。该组件属于 `0.2.5-beta.1` 测试版候选，已安装的正式版 npm `0.2.4` 不含它；是否已发布请查 npm。详见[安全边界与验证记录](docs/auto-compact.md)。
+
+在 DSH 的配置编辑器中找到对应的 `dsh-ops/shell`、`dsh-ops/file` 或 `dsh-ops/background` 行，调整 `config` 后保存；未知配置键会点名报错。也可直接在市场切换组件。主要配置：
 
 ```yaml
 config:
+  # background component only; its market row is disabled by default
   enableShellTools: true
   publishBashTool: true
   promptPolicy: true
@@ -70,9 +96,9 @@ config:
   # bashPath: 'C:\tools\bash.exe'
 ```
 
-- `enableShellTools`：部署开关，开启仍须会话 `danger-full-access` 才发布 FastCtx 命令/job 组。
+- `enableShellTools`：后台组件的部署开关，开启仍须会话 `danger-full-access` 才发布四个后台工具；文件组件不发布命令工具。
 - `publishBashTool`：是否发布 `ops_bash`，同样要求完全权限和宿主 subprocess 服务。
-- `promptPolicy`：是否注入紧凑三层路由说明；可用 `extraGuidance` 追加指导。
+- `promptPolicy`：是否注入该组件的运行时说明；可用 `extraGuidance` 追加指导。
 - `toolCallTimeoutMs`：FastCtx RPC 等待超时，不代表服务端工作已终止。
 - `required`：运行时不可用时是否拒绝激活。
 - `shellPolicy`：默认 `advise`；`deny-host-shell` 拒绝 `deniedHostTools` 列表中的宿主 shell（默认 `[pwsh, bash, pwsh_persistent]`）。这也会禁用第三层 pwsh，谨慎开启。
@@ -85,7 +111,6 @@ config:
 | `ops_glob` | 多模式找路径，支持排除 | 无命令权限门¹ |
 | `ops_replace` | 跨文件批量替换；精确编辑仍用宿主 edit | 无命令权限门¹ |
 | `ops_bash` | 优先的通用 bash 命令执行器 | 是 |
-| `ops_run` | 有界 bash 命令结果 | 是 |
 | `ops_run_background` | 启动后台任务 | 是 |
 | `ops_job_output` / `ops_job_list` / `ops_job_kill` | 查看、列出、停止当前会话启动的任务 | 是 |
 | 宿主 `pwsh` | 使用随包 PowerShell 7 的 Windows 原生操作 | 沿用宿主策略 |

package/cordis.patch.yml

@@ -1,160 +1,32 @@
-# ============================================================================
-# dsh-ops — DSH bundle patch
-# ============================================================================
-# This is the plugin's "mount declaration". DSH applies every bundle patch in
-# the profile's `dsh.profile.bundles` order at startup; this file inserts the
-# dsh-ops row into that tree.
-#
-# Install:
-#   dsh plugin --profile desktop add <path to this package>
-#   dsh plugin --profile web     add <path to this package>
-#
-# The row's config is validated by lib/config.js; every key below is optional
-# and the values shown are the defaults. An unknown key fails the plugin at load
-# rather than being ignored.
-# ----------------------------------------------------------------------------
-
+# Four independent market components; no unconditional host executor override.
+# Shell, file and idle-only automatic compaction are enabled by default.
+# Background remains explicitly opt-in.
 - insert:
-    - id: dsh-ops
-      name: dsh-ops
+    - id: dsh-ops-shell
+      name: dsh-ops/shell
       config:
-        # Absolute path to the FastCtx executable. When set, the plugin hosts
-        # exactly this file and fails loud if it is unusable.
-        # binaryPath: 'C:\path\to\fastctx.exe'
-
-        # The FastCtx server's own name, used to attribute the server
-        # instructions this plugin publishes as a prompt section. The model
-        # never sees it: this plugin speaks MCP to the server it spawns itself
-        # and registers every tool under its own ops_<tool> name.
-        serverName: fastctx
-
-        # Deployment opt-in only. Command/job tools are published per session
-        # only when sandboxPolicy.resolve() reports danger-full-access.
-        enableShellTools: true
-
-        # Per-call deadline for one FastCtx tool call, in milliseconds.
-        toolCallTimeoutMs: 300000
-
-        # Fail plugin activation when the FastCtx server cannot start. Keep
-        # false so a missing runtime degrades to "prompt policy only" instead of
-        # taking the plugin down.
-        required: false
-
-        # 'advise'   — inject the prompt policy only.
-        # 'deny-host-shell' — additionally refuse the host shell tools below at
-        #                     the tools/pre-execute gate.
-        shellPolicy: advise
-
-        # Host tool names refused under 'deny-host-shell'.
-        deniedHostTools:
-          - pwsh
-          - bash
-          - pwsh_persistent
-
-        # Inject the repository-tooling prompt section.
         promptPolicy: true
-
-        # ---- L2: the plugin's own bash -------------------------------------
-        # Absolute path to the bash this plugin runs `ops_bash` through. When
-        # set, the plugin runs exactly this file and refuses the rung when it is
-        # unusable; leave it unset to search the plugin's own bundled copy
-        # first, then PATH, then the well-known Git for Windows locations.
-        # bashPath: 'C:\Program Files\Git\bin\bash.exe'
-
-        # Layer 2: preferred executor for general commands, pipelines and scripts.
-        # Requires a resolved bash, host subprocess and session full access.
         publishBashTool: true
-
-        # Fall back to a system-installed bash when the plugin carries no copy
-        # of its own. Set false to confine the bash rung to plugin-provided
-        # shells. (L3 needs no such switch: whether the host's pwsh row runs
-        # the plugin's own pwsh is decided by the executable's presence — see
-        # the L3 override below.)
+        shellPolicy: advise
         allowSystemShellFallback: true
-
-# ----------------------------------------------------------------------------
-# L3: run the host's pwsh tool on the plugin's own PowerShell 7.
-#
-# WHY ONE LINE IS ENOUGH. `pwsh-local`'s Config owns a `pwshPath` field
-# ("Explicit pwsh executable", packages/shell/pwsh-local/src/index.ts:71-77),
-# and `pwsh-sandbox` inherits it verbatim because it declares
-# `type Config = LocalConfig` (packages/shell/pwsh-sandbox/src/index.ts:40).
-# Pointing this row at the plugin's executable therefore gets the bundled pwsh
-# 7 under the host's sandbox, credential scrub, and output governance with no
-# custom executor and no patched internals.
-#
-# WHY IT CAN EVALUATE TO `undefined` — and that is the safe answer. The row's
-# `pwshPath` default is `undefined`, and `undefined` means "resolve a pwsh the
-# official way" (PowerShell 7 install, PATH, Windows PowerShell 5.1;
-# packages/shell/pwsh-local/src/resolve.ts:67-79). The expression keeps exactly
-# four guards:
-#
-#   1. the platform gate, matching the row's own `disabled` gate: this override
-#      is meaningless off Windows, where `pwsh-sandbox` is not mounted;
-#   2. an existence check over the SAME THREE PLACES, IN THE SAME ORDER, as the
-#      plugin's own probe in `lib/shells.js` (`PWSH_LAYOUT_ORDER`): first the
-#      provisioned store, `<DSH_HOME>/dsh-ops/shells/pwsh/<version>/bin/pwsh.exe`
-#      (what `dsh-ops provision-shells` installs, and the copy the plugin
-#      prefers), then `@dsh-ops/pwsh-<platform>-<arch>` with the shell at
-#      `bin/pwsh.exe` (a deployment that installed the platform package), then
-#      the vendored `vendor/pwsh/<platform>-<arch>/pwsh.exe` (a checkout that
-#      carries its own copy). Keeping the order identical is what makes the
-#      ladder's L3 and the host row the same fact rather than two guesses;
-#   3. a `lstat`-based usability test, so a Windows Store execution alias (a
-#      symlink whose target is not statable) counts, while a directory named
-#      `pwsh.exe` does not — the same rule `resolveShells` applies;
-#   4. a wrapping `try`/`catch` around the whole body, plus a `try` each for the
-#      store scan, the plugin-package resolution, and the platform-package
-#      resolution: an absent store, an unresolvable package, and a malformed
-#      manifest alike may not fail the boot. The store scan sits outside the
-#      plugin resolution on purpose — a provisioned copy is an absolute path
-#      under `DSH_HOME`, so a profile whose `baseUrl` cannot resolve `dsh-ops`
-#      still gets it rather than losing the rung.
-#
-# The store scan picks the greatest version name that holds the executable —
-# the identical comparison `provisionedShell` makes in `lib/shells.js`, which is
-# why it is one expression rather than a version list repeated here. The store's
-# root mirrors `dshHome` there too: `DSH_HOME` when the deployment names one,
-# `~/.dsh` otherwise.
-#
-# Until one of those three places actually carries the executable, the
-# expression yields `undefined` and the host row is left completely untouched.
-#
-# "Installed means used" is the point of the rung: a deployment that carries
-# the plugin's pwsh 7 wants the host's pwsh tool to run it, not the machine's.
-# A deployment that does NOT want this rewrite removes or edits this patch
-# entry in its OWN profile `cordis.patch.yml` — that layer applies after every
-# bundle layer (docs/user/develop/basic/publish.md:118-130), so it has the last
-# word. There is deliberately no plugin config key for it: a bundle patch is
-# evaluated before any dsh-ops row is mounted (the Loader defers a row's `!!js`
-# interpolation until that row's own injections are active), so a config key
-# could not reach this expression, and a key that pretends to is a ladder that
-# lies about the row it never changed.
-#
-# `!!js` SCOPE, VERIFIED IN THE VENDORED LOADER. The Loader evaluates these
-# expressions as `with (ctx) { return eval(expr) }`
-# (vendor/loader/src/config/utils.ts:5-9), so bare `baseUrl` (the owning config
-# tree's base URL) and `ctx` are both in scope — the same convention the shipped
-# bundle uses at packages/bundle/web-app/presets/cordis.patch.yml:147.
-# `dsh-ops` is a dependency of the profile, so
-# `createRequire(baseUrl).resolve('dsh-ops/package.json')` finds the package
-# whether it was installed as a link or from the registry.
-#
-# WHOLE-OBJECT REPLACEMENT — AUDITED, NOT ASSUMED. A patch replaces the target
-# row's ENTIRE `config` object rather than deep-merging it
-# (docs/user/develop/basic/publish.md:129), so every non-default field of the
-# target must be restated here. The base row this targets is
-# packages/bundle/base/cordis.patch.yml:241-243:
-#
-#     - id: pwsh-sandbox
-#       name: '@deepseek-ai/dsh-pwsh-sandbox'
-#       disabled: !!js process.platform !== 'win32'
-#
-# It declares NO `config` at all, and this patch writes only `config` (the
-# row's `name` and its platform `disabled` gate are untouched), so there is no
-# non-default field to restate and nothing is silently dropped. If the base row
-# ever gains one, it must be restated here.
-# ----------------------------------------------------------------------------
-- id: pwsh-sandbox
-  config:
-    pwshPath: !!js "(() => { if (process.platform !== 'win32') return undefined; try { const builtin = (name) => process.getBuiltinModule(name); const fs = builtin('node:fs'); const nodePath = builtin('node:path'); const win = process.platform + '-' + process.arch; const usable = (file) => { try { const stat = fs.lstatSync(file); return stat.isFile() || stat.isSymbolicLink(); } catch { return false; } }; const named = process.env.DSH_HOME; const home = typeof named === 'string' && named.trim() !== '' ? nodePath.resolve(named) : nodePath.join(builtin('node:os').homedir(), '.dsh'); const layouts = []; try { const store = nodePath.join(home, 'dsh-ops', 'shells', 'pwsh'); const versions = fs.readdirSync(store, { withFileTypes: true }).filter((entry) => entry.isDirectory()).map((entry) => entry.name).sort().reverse(); for (const version of versions) layouts.push(nodePath.join(store, version, 'bin', 'pwsh.exe')); } catch {} try { const requires = builtin('node:module').createRequire(String(baseUrl).replace(/[^/]*$/, 'noop.json')); const dir = nodePath.dirname(requires.resolve('dsh-ops/package.json')); try { const pluginRequire = builtin('node:module').createRequire(nodePath.join(dir, 'package.json')); const pkg = nodePath.dirname(pluginRequire.resolve('@dsh-ops/pwsh-' + win + '/package.json')); layouts.push(nodePath.join(pkg, 'bin', 'pwsh.exe')); } catch {} layouts.push(nodePath.join(dir, 'vendor', 'pwsh', win, 'pwsh.exe')); } catch {} for (const candidate of layouts) { if (usable(candidate)) return candidate; } return undefined; } catch { return undefined; } })()"
+    - id: dsh-ops-file
+      name: dsh-ops/file
+      config:
+        promptPolicy: true
+        enableShellTools: false
+        required: false
+        toolCallTimeoutMs: 300000
+    - id: dsh-ops-background
+      name: dsh-ops/background
+      disabled: true
+      config:
+        promptPolicy: true
+        enableShellTools: true
+        required: false
+        toolCallTimeoutMs: 300000
+    - id: dsh-ops-auto-compact
+      name: '@dsh-ops/auto-compact'
+      config:
+        thresholdPercent: 50
+        cooldownSeconds: 120
+        timeoutSeconds: 120