dsh-multi-folder 0.1.7 → 0.2.1

package/README.md

@@ -34,6 +34,15 @@ dsh plugin --profile web add dsh-multi-folder
 
 Then **restart the DSH backend** (host composition loads at process start) and **refresh the browser page** (the client bundle is served `no-cache`).
 
+## Compatibility
+
+Choose the plugin version that matches your DeepSeek Harness release:
+
+| DeepSeek Harness | Install |
+| --- | --- |
+| 0.1.1 or earlier | `dsh-multi-folder@0.1.7` |
+| 0.1.2-alpha or later | the latest `dsh-multi-folder` |
+
 ## Usage
 
 A Multi-folder button appears in the session header, and a second entry appears on the **session-creation page**: a chip row directly above the composer card (the same band the git-branch chip uses), aligned with the workspace/preset chips of the new-session screen. Clicking it opens the panel as a popover anchored to the chip. Exactly one session-creation entry is ever shown — the plugin registers three candidate seats and elects the best available one (upstream `conversation.hero.workspaceExtras` chip > `conversation.input.dock` row > fixed bottom-right launcher for shells declaring neither). The panel lets you:

package/README.zh.md

@@ -34,6 +34,15 @@ dsh plugin --profile web add dsh-multi-folder
 
 然后**重启 DSH 后端**（宿主组合在进程启动时装载）并**刷新浏览器页面**（客户端 bundle 以 `no-cache` 提供）。
 
+## 兼容性
+
+请选择与你的 DeepSeek Harness 版本匹配的插件版本：
+
+| DeepSeek Harness | 安装 |
+| --- | --- |
+| 0.1.1 及更早 | `dsh-multi-folder@0.1.7` |
+| 0.1.2-alpha 及更新 | 最新版 `dsh-multi-folder` |
+
 ## 使用
 
 会话头部出现「多工作目录」按钮（英文界面显示 "Multi-folder"）；**会话创建页**的入口位于**输入框上方**——与 git 分支胶囊同一条 dock 带，左边缘对齐新会话界面的工作区/预设胶囊，点击后面板以锚定在该胶囊上的浮层展开。会话创建页始终只显示**一个**入口：插件注册三个候选座位并选用当前可用的最佳者（上游 `conversation.hero.workspaceExtras` chip > `conversation.input.dock` 行 > 两者皆未声明时的右下角浮动按钮）。打开面板即可：

package/docs/design.md

@@ -154,8 +154,7 @@ window.__ModuleLoader__.load({
 - `inject: ['remote', 'remote.commands', 'slots', 'workspaces', 'connection', 'sessions', 'locale']`; the package's
   `dsh.client.inject` lists the packages providing them
   (`@deepseek-ai/dsh-api-gateway`, `@deepseek-ai/dsh-api-remotes`,
-  `@deepseek-ai/dsh-client-connection`, `@deepseek-ai/dsh-client-locale`,
-  `@deepseek-ai/dsh-client-runtime`).
+  `@deepseek-ai/dsh-client-connection`, `@deepseek-ai/dsh-client-locale`).
 - UI registrations: `conversation.session.header.actions` (session-scoped button),
   `shell.overlay` panel, `conversation.input.dock` chip row (session-scoped
   list entry above the composer card — the session-creation page's shipped
@@ -201,9 +200,13 @@ window.__ModuleLoader__.load({
     renders directly ABOVE the composer card, in the same band as the
     git-branch chip. The entry receives the dock owner share (`{ session,
     input }`) plus the standard `useSessions` / `useWorkspaces` selector hooks,
-    so the hero phase (`composerPhase === 'blank' && (openState === 'open' ||
-    blank)`) and the target workspace come from framework props instead of DOM
-    probing. The row stays **in flow** — `display:flex` with the official hero
+    so the hero phase and the target workspace come from framework props instead
+    of DOM probing. Detection is DSH-version-adaptive: a shell whose
+    `SessionSnapshot` carries `composerPhase` uses
+    `composerPhase === 'blank' && (openState === 'open' || blank)`, while DSH
+    0.1.2 (no `composerPhase`) uses the settled-blank fallback
+    `blank && !running && !promptAttempted && (openState === 'open' || blank)`.
+    The row stays **in flow** — `display:flex` with the official hero
     row's 20px indent, no absolute positioning — so the framework's list-slot
     arrangement keeps it clear of every other plugin's dock row. It renders
     only on the session-creation page; an active session keeps its entry in the

package/lib/client.js

@@ -214,12 +214,13 @@ window.__ModuleLoader__.load({
 
     // ------------------------------------------------------------- plugin
     var name = 'dsh-multi-folder';
-    var inject = ['remote', 'remote.commands', 'slots', 'workspaces', 'connection', 'sessions', 'locale'];
+    var inject = ['remote', 'remote.commands', 'slots', 'workspaces', 'uiWorkspace', 'connection', 'sessions', 'locale'];
 
     function apply(ctx) {
       var slots = ctx.slots;
       var remote = ctx.remote;
       var workspaces = ctx.workspaces;
+      var uiWorkspace = ctx.uiWorkspace;
       var connection = ctx.connection;
       var sessions = ctx.sessions;
       var locale = ctx.locale;
@@ -398,7 +399,18 @@ window.__ModuleLoader__.load({
       }
 
       function addDirectory() {
-        workspaces.pickDirectory().then(function (path) {
+        // DSH 0.1.2 moved the directory picker onto `uiWorkspace`; earlier
+        // shells kept it on `workspaces`. Pick whichever service actually
+        // exposes it (and call it with the right receiver), surfacing a clear
+        // error when neither does instead of throwing synchronously.
+        var picker = (uiWorkspace && typeof uiWorkspace.pickDirectory === 'function')
+          ? uiWorkspace
+          : (workspaces && typeof workspaces.pickDirectory === 'function') ? workspaces : null;
+        if (picker === null) {
+          patch({ error: 'multi-folder: the directory picker service is unavailable' });
+          return;
+        }
+        picker.pickDirectory().then(function (path) {
           if (path === null || path === undefined) return;
           var snapshot = getSnapshot();
           if (snapshot.sessionId) {
@@ -763,10 +775,22 @@ window.__ModuleLoader__.load({
       /** The shell's own hero predicate, read from the dock's owner share: a
        *  blank conversation with an open session. A still-loading blank
        *  session already lists as blank, so it may enter the hero phase
-       *  before the composer snapshot settles to `open`. */
+       *  before the composer snapshot settles to `open`.
+       *
+       *  DSH 0.1.2 exposes no `composerPhase` on SessionSnapshot; the hero
+       *  phase there is a settled blank session (mirroring ConversationRoot's
+       *  `hero = sessionId === undefined || (shellPhase === 'blank' && ...)`),
+       *  so the blank/lifecycle fields are used as the fallback. Newer DSH
+       *  shells that do carry `composerPhase` keep their original check. */
       function isHeroPhase(session, blank) {
         if (!session) return false;
-        return session.composerPhase === 'blank' && (session.openState === 'open' || blank === true);
+        if (session.composerPhase !== undefined) {
+          return session.composerPhase === 'blank' && (session.openState === 'open' || blank === true);
+        }
+        return session.blank === true
+          && !session.running
+          && !session.promptAttempted
+          && (blank === true || session.openState === 'open');
       }
 
       /** The workspace path a session belongs to, from the workspaces list. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-multi-folder",
-  "version": "0.1.7",
+  "version": "0.2.1",
   "description": "DeepSeek Harness plugin: secondary working directories for a project. The agent keeps the primary workspace as cwd, gains equal write/exec permissions on configured secondary directories under workspace-write mode, and is notified of configuration changes at the next message boundary. Configurable from the session header AND from the session-creation page (before the first message) through a sessionless multiFolder remote API.",
   "keywords": [
     "dsh-plugin",
@@ -42,7 +42,8 @@
     "compatibility": {
       "node": ">=20",
       "dshReleases": {
-        "0.1.1-rc.2": "compatible"
+        "0.1.1-rc.2": "incompatible",
+        "0.1.2-alpha.1": "compatible"
       }
     },
     "bundle": {
@@ -54,8 +55,7 @@
         "@deepseek-ai/dsh-api-gateway",
         "@deepseek-ai/dsh-api-remotes",
         "@deepseek-ai/dsh-client-connection",
-        "@deepseek-ai/dsh-client-locale",
-        "@deepseek-ai/dsh-client-runtime"
+        "@deepseek-ai/dsh-client-locale"
       ]
     }
   },