dsh-more 0.1.0 → 0.1.2

package/CONTRIBUTING.md

@@ -270,6 +270,19 @@ pnpm run check
 pnpm run package:check
 ```
 
+适配官方 macOS 桌面端时，另外运行已安装桌面包的真实运行时检查：
+
+```sh
+pnpm run test:desktop
+DSH_MORE_DESKTOP_ASAR='/Applications/DeepSeek Harness.app/Contents/Resources/app.asar' pnpm exec vitest run src/patches/projectless-tasks/native-factory.test.tsx
+```
+
+`test:desktop` 默认使用 `/Applications/DeepSeek Harness.app`，可通过 `DSH_MORE_DESKTOP_APP` 指定其他安装位置。它在临时 `DSH_HOME` 中启动安装包自带的 Host，用本地模型替身验证导出内容、编辑后续跑、删除消息后重建、分组持久化、会话物理删除、模型能力保存与冲突处理、标题中间件。不会读取用户 profile、调用外部模型或修改用户会话。该检查验证真实 SDK 与后端行为；发布前仍应重载实际桌面窗口，验证功能入口、弹窗、导航和文件下载。
+
+DSH 0.1.7 的会话菜单提供 `sidebar.workspaces.session.menu.item`。优先通过共享 `platform/dsh/client/session-menu.tsx` 注册动作，直接使用该行的 `sessionId`；不要用点击原生归档按钮来获取目标会话。新版原生归档回调由菜单子插槽独立注入，且菜单包含快捷键文本，旧的父组件拦截与整行文字匹配不再可靠。旧版 DSH 才使用原有 DOM 适配。
+
+只有需要跨补丁开关保留的被动生命周期信息，才使用 HostPatch 的 `observe()`；其 disposer 在整个插件卸载时执行。例如永久删除必须跟踪补丁关闭期间创建的 Agent 句柄，才能在重新开启后安全释放写入锁。实际用户操作仍由 `setup()` 和启用状态控制的 API 执行。方法包装必须保留调用者的 `this`，避免改变 Cordis 的资源所属作用域。
+
 说明：
 
 - `build`、`typecheck` 和 `test` 都会自动运行生成器；

package/README.md

@@ -6,7 +6,7 @@ Practical, independently switchable patches for missing context and history cont
 
 `dsh-more` integrates with the existing DSH interface instead of adding a separate management dashboard. Its current patch set can edit a user message and restart from that point, remove one message while preserving the surrounding context, and permanently delete a session while leaving native archive behavior intact.
 
-> **Compatibility:** the current release targets DeepSeek Harness `0.1.5-rc.2` and requires Node.js `>= 24`. DSH is still a release candidate, so upgrades may require changes in the centralized adapter layer described below.
+> **Compatibility:** the development/test baseline is DeepSeek Harness `0.2.1-rc.2`. All patches and existing peer ranges are preserved. Type, feature and isolated Host checks pass against the target RC; Windows path/build/script fixes are not a claim of Windows Desktop end-to-end verification. Node.js 24+ is recommended; the package engine also allows Node.js 22.19+.
 
 ## Features
 
@@ -16,6 +16,10 @@ Practical, independently switchable patches for missing context and history cont
 | Delete one message | User- and assistant-message action rows | Removes the selected model-surface node, expands only when tool call/result pairing requires it, rebuilds the surviving context, and opens a child session | On |
 | Permanently delete session | Separate item beside the native Archive action | Stops and unloads the target session, removes its exact JSONL persistence directory, detaches it from workspaces, and synchronizes the lists incrementally | On |
 | Model capabilities | Settings → Models → Model capabilities | Configure image support, selectable thinking types and parameter formats per model | On |
+| Fast mode | Composer toolbar and `/fast` | Toggle faster model service for the current session (may consume quota faster) | On |
+| Markdown export | Conversation toolbar / More menu | Export messages and tool results with Windows-safe download filenames | On |
+| Automatic titles | After the first request | Generate a title using the current model, preserving manual names | On |
+| Independent tasks and grouping | Workspace picker / session menu | Create an independent task with its draft intact; group sessions without changing their working directories | On |
 
 Patch switches live under **Settings → Plugins → Plugin configuration → DSH More** and take effect without rebuilding the plugin.
 
@@ -24,11 +28,24 @@ Patch switches live under **Settings → Plugins → Plugin configuration → DS
 ### Requirements
 
 - Node.js `>= 24`
-- A working `dsh` CLI and a Web profile compatible with DSH `0.1.5-rc.2`
+- A working `dsh` CLI and a Web or Desktop profile on DeepSeek Harness `0.2.1-rc.2`
 - Access to the npm registry that publishes `dsh-more`
 
 pnpm is needed only when installing or developing from source. For a published release, use the DSH plugin command so the package is installed into the selected DSH profile; do not install it globally with `npm install -g`.
 
+### Windows: install this unreleased fix
+
+The existing npm release is not this working-tree fix. Build a tarball with `pnpm install --frozen-lockfile`, `pnpm run check`, `pnpm run test:runtime`, then `npm pack`, or copy the resulting tarball from another machine.
+
+For Desktop, initialize the app once, fully quit it, and use the **Desktop-supplied `dsh` command** (verify `Get-Command dsh` and `dsh --version`) to run:
+
+```powershell
+dsh plugin --profile desktop add "C:\Downloads\dsh-more-0.1.1.tgz"
+dsh plugin --profile desktop list dsh-more --depth 0
+```
+
+The generic npm CLI rejects the reserved Desktop profile; use the installed Desktop carrier instead of replacing its profile. For a browser Web service, use `--profile web` and restart the original `dsh web`. Web and Desktop profiles are separate. Reopen Desktop / reload the browser and check all DSH More switches. Quote paths containing spaces or non-ASCII characters. Windows Desktop manual acceptance is still required; see the [compatibility record](./docs/desktop-compatibility.md).
+
 ### Install the latest release from npm
 
 ```sh
@@ -235,14 +252,14 @@ Generated source, `dist/`, and tarballs are not committed. `prepack` runs the co
 
 ### Dependency updates
 
-`package.json` uses compatible version ranges so installs and updates can resolve newer versions within those ranges. `pnpm-lock.yaml` preserves reproducible builds; a normal install keeps already locked versions. To refresh dependencies and validate them:
+`package.json` declares compatible Host peer ranges, but pins the DSH development SDK to `0.2.1-rc.2` (with Cordis 4.0.5, Schemastery 3.18.5 and Zod 4.4.3). `pnpm-lock.yaml` preserves the verified graph. When changing the SDK baseline, update these pins together, reinstall, and validate:
 
 ```sh
 pnpm update
 pnpm run check
 ```
 
-The DSH range `^0.1.5-rc.2` accepts later stable `0.1.x` releases and newer `0.1.5` RCs. It does not cross into `0.2` or include alpha/RC releases with a different version tuple.
+DSH Host peers use `^0.1.5-rc.2 || ^0.2.0-rc.2 || ^0.2.1-alpha.5`. The `^0.2.1-alpha.5` range includes `0.2.1-rc.2` on the same version tuple, without bypassing compatibility checks. Prereleases on other version tuples still require verification.
 
 ### Verification scope
 
@@ -252,13 +269,15 @@ The repository does not currently contain a full browser end-to-end suite agains
 
 ## Compatibility notes
 
-Development and host dependency ranges use `^0.1.5-rc.2`; the lockfile records the versions currently verified. The adapters and tests cover the current session format, message provenance, `main.conversation` slot, and JSONL persistence snapshots and location capability. For an existing local linked install, rebuild, restart DSH, and reload the page to load both the new Host and Client.
+See the [desktop verification record](./docs/desktop-compatibility.md) for the actual macOS `0.1.7-rc.2` window checks. The desktop adapter navigates through `uiWorkspace.openSession()`, reads current selection from `retainedBy.mainView`, and temporarily retains newly created Sessions until their drafts can be transferred. Independent tasks, edit/delete handoffs, and current-session deletion share this adapter.
+
+Development uses the pinned `0.2.1-rc.2` SDK; Host peer ranges preserve existing RC/alpha compatibility. The removed `webRuntime` service is no longer required; requests use the authenticated Connection Fetch registry. Settings adapters support ConfigForms/SettingsForms and the previous APIs. The adapters and tests cover the current session format, message provenance, `main.conversation` slot, and JSONL persistence snapshots and location capability. For an existing local linked install, rebuild, restart DSH, and reload the page to load both the new Host and Client.
 
-- The current dependency set targets DSH `0.1.5-rc.2`; pre-release API or DOM changes can require adapter updates.
+- The current test baseline is DSH `0.2.1-rc.2`; future pre-release API or DOM changes can require adapter updates. Run `pnpm run test:runtime` for isolated RC Host integration checks (temporary profile and fake model; no user history or credentials).
 - In-product DSH More copy is currently primarily Simplified Chinese, although native Copy/Archive selectors recognize both Chinese and English labels.
 - Message actions operate only on ordinary user messages and assistant messages still present in the current model surface; editing requires a completed owning turn.
 - Permanent deletion requires a `jsonl` backend with a valid location capability. Its current `locate` hook is internal; the adapter checks its presence and result. Tests cover plain and Zstandard-compressed session files.
-- Unloading a live session uses tracked public Agent handles. With handle-based persistence, deletion refuses an already-live session whose Agent handle was not tracked and asks for a DSH restart, preserving write ownership and file locks.
+- Unloading a live session uses tracked public Agent handles. Passive tracking spans the plugin lifetime, including periods when deletion is disabled, and preserves the caller's Cordis ownership. A live writer that predates the plugin's observation is still refused with a restart instruction, preserving write ownership and file locks.
 
 ## License
 

package/README.zh-CN.md

@@ -6,7 +6,7 @@
 
 `dsh-more` 不创建平行的“管理中心”，而是把能力直接嵌入 DSH 现有界面。当前补丁可以编辑用户消息并从该处重新开始、在保留前后上下文的前提下删除单条消息，以及在不改变原生归档语义的情况下永久删除会话。
 
-> **兼容性：** 当前发布面向 DeepSeek Harness `0.1.5-rc.2`，要求 Node.js `>= 24`。DSH 仍是 RC 版本，升级后可能需要调整下文所述的集中适配层。
+> **兼容性：** 开发与测试基线为 DeepSeek Harness `0.2.1-rc.2`。保留全部补丁及已有 peer 兼容范围，已通过目标 RC 的类型、功能和隔离 Host 验收；Windows 路径、构建与脚本兼容修复不等同于 Windows Desktop 实机逐项验收。推荐 Node.js 24+；包引擎也允许 Node.js 22.19+。
 
 ## 功能概览
 
@@ -16,6 +16,10 @@
 | 单条消息删除 | 用户和助手消息操作区 | 删除所选 model-surface 节点；只有工具调用/结果配对需要时才扩大范围；重建存活上下文并打开子会话 | 开启 |
 | 永久删除会话 | 原生“归档会话”旁的独立菜单项 | 停止并卸载目标会话，移除其精确 JSONL 持久化目录，从 Workspace 脱离并增量同步列表 | 开启 |
 | 模型能力配置 | 设置 → 模型 → 模型能力 | 按模型配置识图、可选思考类型及接口参数格式，不自动猜测能力 | 开启 |
+| 加速 | 输入框工具栏与 `/fast` 命令 | 开关当前会话的加速。响应更快，但会更快消耗额度 | 开启 |
+| Markdown 导出 | 会话工具栏 / 更多操作 | 导出消息与工具结果，下载文件名兼容 Windows | 开启 |
+| 自动标题 | 新会话首次需求后 | 用当前模型生成标题，保留手动命名 | 开启 |
+| 独立任务与手动归组 | 工作区下拉框 / 会话菜单 | 保留草稿创建独立任务；归组不改变工作目录 | 开启 |
 
 补丁开关位于 **设置 → 插件 → 插件配置 → DSH More**，修改后实时生效，无需重新构建插件。
 
@@ -24,11 +28,38 @@
 ### 环境要求
 
 - Node.js `>= 24`
-- 可正常使用的 `dsh` CLI，以及与 DSH `0.1.5-rc.2` 兼容的 Web profile
+- 可正常使用的 `dsh` CLI，以及 DeepSeek Harness `0.2.1-rc.2` 的 Web 或 Desktop profile
 - 能访问发布 `dsh-more` 的 npm registry
 
 只有从源码安装或参与开发时才需要 pnpm。安装已发布版本时，应通过 DSH 插件命令把包加入指定 profile；不要使用 `npm install -g` 全局安装。
 
+### Windows 安装本次修复（尚未发布到 npm）
+
+不要把 npm 上的旧包当成本次修复版。可将本仓库构建的 `dsh-more-0.1.1.tgz` 复制到 Windows 后安装；也可在 Windows 源码目录执行：
+
+```powershell
+node --version
+pnpm install --frozen-lockfile
+pnpm run check
+pnpm run test:runtime
+npm pack
+```
+
+- **桌面应用**：先启动 Desktop 一次完成初始化，再完整退出。使用 **Desktop 安装附带的 `dsh` 命令**，确认 `dsh --version` 为 `0.2.1-rc.2`，然后安装到 `desktop` profile：
+
+```powershell
+Get-Command dsh | Select-Object Source
+dsh --version
+dsh plugin --profile desktop add "C:\Downloads\dsh-more-0.1.1.tgz"
+dsh plugin --profile desktop list dsh-more --depth 0
+```
+
+若提示 desktop 由 Electron 专属管理，说明调用的是 npm 安装的通用 CLI，而非 Desktop 的配套命令；请切换命令来源，不要重建或覆盖 Desktop profile。
+
+- **浏览器 Web 服务**：改用 `dsh plugin --profile web add "C:\Downloads\dsh-more-0.1.1.tgz"`，之后重启原来的 `dsh web`。
+
+安装后重新打开 Desktop / 刷新 Web 页面，在 **设置 → 插件 → 插件配置 → DSH More** 确认所有补丁开关。Web 与 Desktop 是不同 profile，安装到 web 不会自动影响桌面应用。路径含空格或中文时务必加引号。本次没有修改用户 DSH 安装或会话，也没有发布 npm；Windows 实机逐项验收仍需执行，见[兼容记录](./docs/desktop-compatibility.md)。
+
 ### 从 npm 安装最新版
 
 ```sh
@@ -235,14 +266,14 @@ pnpm run package        # 构建并生成 npm tarball
 
 ### 依赖更新
 
-`package.json` 使用兼容版本范围，允许安装或更新时解析范围内的新版本；`pnpm-lock.yaml` 保留可复现的构建结果，普通安装不会自动改写已经锁定的版本。更新依赖并验证：
+`package.json` 的宿主 peer 使用兼容范围；DSH 开发 SDK 则固定为 `0.2.1-rc.2`，并同步固定 Cordis 4.0.5、Schemastery 3.18.5 与 Zod 4.4.3，避免不同版本类型混用。`pnpm-lock.yaml` 保留已验证依赖图。更换 SDK 基线时应一起更新这些固定版本，重新安装并验证：
 
 ```sh
 pnpm update
 pnpm run check
 ```
 
-DSH 的 `^0.1.5-rc.2` 接受后续 `0.1.x` 正式版本和 `0.1.5` 的更新 RC，不自动跨入 `0.2`，也不包含其他版本基线的 alpha/RC。
+宿主 DSH peer 使用 `^0.1.5-rc.2 || ^0.2.0-rc.2 || ^0.2.1-alpha.5`。其中 `^0.2.1-alpha.5` 包含同一版本基线的 `0.2.1-rc.2`，不需要禁用版本检查；不同版本基线的预发布版仍需重新验证。
 
 ### 验证范围
 
@@ -252,13 +283,15 @@ DSH 的 `^0.1.5-rc.2` 接受后续 `0.1.x` 正式版本和 `0.1.5` 的更新 RC
 
 ## 兼容性说明
 
-开发与宿主依赖统一使用 `^0.1.5-rc.2`，锁文件记录当前已验证版本。已适配新版会话格式、消息来源字段、`main.conversation` 插槽，以及 JSONL 后端的持久化快照和定位能力。已有本地链接安装在重新构建后，需要重启 DSH 并刷新页面以加载新的 Host 和 Client。
+官方 macOS 桌面端 `0.1.7-rc.2` 的实际窗口验证记录见 [桌面端兼容检查](./docs/desktop-compatibility.md)。新版使用 `uiWorkspace.openSession()` 导航，以 `retainedBy.mainView` 识别当前会话；创建后通过临时 Session reference 等待草稿可用，完成交接后释放。独立任务、消息编辑/删除后的跳转和当前会话删除共用该适配。
+
+开发 SDK 固定在 `0.2.1-rc.2`；宿主 peer 保留已有 RC/alpha 兼容范围。插件不再强依赖已移除的 `webRuntime`，请求走受认证的 Connection Fetch registry；设置层同时兼容 ConfigForms/SettingsForms 与旧接口。已适配新版会话格式、消息来源字段、`main.conversation` 插槽，以及 JSONL 后端的持久化快照和定位能力。已有本地链接安装在重新构建后，需要重启 DSH 并刷新页面以加载新的 Host 和 Client。
 
-- 当前依赖面向 DSH `0.1.5-rc.2`；预发布 API 或 DOM 变化可能要求更新 adapter。
+- 当前测试基线为 DSH `0.2.1-rc.2`；后续预发布 API 或 DOM 变化仍可能要求更新 adapter。`pnpm run test:runtime` 会用临时 profile 和模型替身运行隔离 RC Host 验收，不使用用户历史或密钥。
 - DSH More 的产品内文案目前以简体中文为主；对 DSH 原生 Copy/Archive 元素的定位同时识别中英文标签。
 - 消息操作只面向仍在当前 model surface 中的普通用户消息和助手消息；编辑要求所属轮次已经完成。
 - 永久删除只支持提供有效定位能力的 `jsonl` 后端；当前后端的 `locate` 为内部接口，调用前会检查能力及返回值，测试覆盖普通和 Zstandard 压缩会话文件。
-- 卸载实时会话时使用插件追踪到的公开 Agent handle。新版持久化后端仍持有写入句柄、但插件未追踪到对应 Agent handle 时，会拒绝删除并提示重启 DSH，避免遗留写入锁。
+- 卸载实时会话时使用插件追踪到的公开 Agent handle。被动句柄跟踪覆盖整个插件生命周期，开关关闭期间创建的会话也可在重新开启后安全删除，且不会改变调用者的 Cordis 资源所有权。若会话在插件加载前就已持有未被观察到的写入句柄，仍会拒绝删除并提示重启 DSH，避免遗留写入锁。
 
 ## 许可证
 

package/cordis.patch.yml

@@ -2,5 +2,7 @@
 - insert:
     - id: dsh-more-session-groups
       name: dsh-more/session-groups
+    - id: dsh-more/fast-mode
+      name: dsh-more/fast-mode
     - id: dsh-more
       name: dsh-more