dsh-plugin-dshm 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## 0.1.1 — Unreleased
+
+- Support DSH 0.2.1-rc.5 (npm latest verified 2026-10-30), retaining exact
+  support for 0.2.1-rc.3. Other prereleases and future versions remain blocked.
+- Include the previously verified task-032 interaction-status correction:
+  concurrent read/correlation timeouts publish the native running/idle fallback
+  and its warning before returning a session snapshot.
+- Native macOS integration covers approvals/questions, reconnects, transfers,
+  path policy and restart. Windows verification of this new combination is
+  pending; no new Windows compatibility result is claimed.
+
 ## 0.1.0 — 2026-10-28
 
 Initial DSHM bridge release for DeepSeek Harness 0.2.1-rc.3.

package/README.md

@@ -8,9 +8,10 @@ your paired device over your local network or your own VPN.
 
 ## Requirements and compatibility
 
-- DeepSeek Harness **0.2.1-rc.3**, the exact currently supported `engines.dsh`
-  value. DSH is a Developer Preview; a newer version is not automatically
-  compatible.
+- DeepSeek Harness **0.2.1-rc.3 or 0.2.1-rc.5**. Plugin 0.1.1 adds support for
+  **0.2.1-rc.5**, the npm `latest` release verified on 2026-10-30. These are
+  exact tested versions; other releases, including the separate 0.2.2 alpha
+  channel, are not automatically compatible.
 - A running DSH desktop app or `dsh web` on your computer, and a compatible DSHM
   iPhone/iPad build. This npm package does not install the iOS app.
 - Node 24 or later in the DSH runtime, and `openssl` on its PATH for the initial
@@ -19,9 +20,10 @@ your paired device over your local network or your own VPN.
   connected VPN such as Tailscale.
 
 The bridge has been exercised with DSH 0.2.1-rc.3 on macOS, including the desktop
-app and isolated `dsh web`. Windows is an intended platform, but its native
-runtime/firewall checklist is still pending; do not treat the macOS tests as
-Windows verification. Physical-phone network acceptance is also separate from
+app and isolated `dsh web`. Plugin 0.1.1 is also tested against real DSH
+0.2.1-rc.5 in isolated `dsh web`, including approvals, reconnects, file transfers,
+path restrictions and restart. The new 0.1.1 / rc.5 combination still needs a
+Windows native check; macOS results do not substitute for Windows verification. Physical-phone network acceptance is also separate from
 the local test-client and Simulator results. Mainland China is outside the v1
 release scope; mainland network reachability is not claimed.
 
@@ -190,8 +192,10 @@ credentials/session directories. Uninstall does not remove your DSH sessions.
 
 ## New DSH release checklist (maintainers)
 
-1. Keep `engines.dsh` at the currently verified version while testing. Review
-   upstream DSH changes, especially the projection APIs and bundle loader.
+1. Review upstream DSH changes, especially the projection APIs and bundle
+   loader. In an unpublished candidate, update the explicit runtime allowlist
+   and `engines.dsh` together so DSH can install it for isolated verification.
+   Do not publish or claim support before the following tests pass.
 2. Install the candidate DSH runtime through its normal distribution and run
    `pnpm -C bridge test:integration` against it in the isolated `.dsh-test` home.
    Review the explicit runtime version guard in `bridge/src/projection/native.ts`
@@ -203,7 +207,7 @@ credentials/session directories. Uninstall does not remove your DSH sessions.
 3. Run `pnpm -C bridge test`, `pnpm -C protocol validate` and
    `pnpm -C protocol gen:check`. Fix compatibility changes only inside the
    appropriate boundary and review the results.
-4. **Only after the real-DSH suite passes**, widen `engines.dsh` to the explicit
+4. **Only after the real-DSH suite passes**, finalize `engines.dsh` as the explicit
    tested versions/range. Never assume an entire future minor release is safe.
    Update the tested range in `tools/release-plugin/check-release.mjs` with the
    recorded evidence, keeping it aligned with the runtime compatibility guard.

package/README.zh-CN.md

@@ -7,8 +7,10 @@
 
 ## 环境与兼容性
 
-- DeepSeek Harness **0.2.1-rc.3**，这是当前 `engines.dsh` 声明的精确版本。
-  DSH 仍处于 Developer Preview 阶段，不能假定新版本自动兼容。
+- DeepSeek Harness **0.2.1-rc.3 或 0.2.1-rc.5**。插件 0.1.1 新增对
+  **0.2.1-rc.5** 的支持，这是 2026-10-30 验证的 npm `latest` 版本。
+  仅支持这些已测试的精确版本；其他版本（包括独立的 0.2.2 alpha 通道）
+  不会自动视为兼容。
 - 电脑正在运行 DSH 桌面应用或 `dsh web`，手机或平板已安装兼容的 DSHM
   构建版本。这个 npm 包不会安装 iOS 应用。
 - DSH 运行环境使用 Node 24 或更新版本，且 PATH 中有 `openssl`，供首次
@@ -16,8 +18,9 @@
 - 两台设备之间能够直接通信，或已连接到你自己的 Tailscale 等 VPN。
 
 目前已在 macOS 上使用 DSH 0.2.1-rc.3 验证桌面应用及隔离的 `dsh web`。
-Windows 是计划支持的平台，但原生运行和防火墙验证清单尚未完成；macOS
-通过的测试不能代替 Windows 验证。真实手机的网络测试也与本地测试客户端、
+插件 0.1.1 还在真实 DSH 0.2.1-rc.5 的隔离 `dsh web` 中通过了审批、重连、
+文件传输、路径限制及重启测试。新的 0.1.1 / rc.5 组合仍需 Windows 原生验证；
+macOS 通过的测试不能代替 Windows 验证。真实手机的网络测试也与本地测试客户端、
 Simulator 的结果分别记录。v1 不包含中国大陆市场，也不声明已验证大陆网络可达性。
 
 ## 在 DSH 中安装
@@ -158,8 +161,9 @@ APNs 已经接收的通知无法撤回。终端输出仍仅供查看；桥接插
 
 ## 新 DSH 版本发布检查清单（维护者）
 
-1. 测试期间保持当前已验证的 `engines.dsh` 值不变，先阅读上游改动，尤其是
-   projection 接口和插件加载器的变化。
+1. 先阅读上游改动，尤其是 projection 接口和插件加载器。在尚未发布的候选包中，
+   同步更新显式运行时允许列表及 `engines.dsh`，以便通过 DSH 安装并进行隔离
+   验证。以下测试通过前，不发布该包，也不对外声明支持新版本。
 2. 通过 DSH 的正常发布渠道安装候选运行时，在隔离的 `.dsh-test` home 中对
    **该候选版本**运行 `pnpm -C bridge test:integration`。兼容性改动必须同时
    审查 `bridge/src/projection/native.ts` 中的显式运行时版本保护；只改包元数据
@@ -168,7 +172,7 @@ APNs 已经接收的通知无法撤回。终端输出仍仅供查看；桥接插
    记录实际版本和结果；声明新的 Windows 组合已支持前，完成 Windows 清单。
 3. 运行 `pnpm -C bridge test`、`pnpm -C protocol validate` 和
    `pnpm -C protocol gen:check`。在正确的架构边界内修复兼容性问题并审查结果。
-4. **只有真实 DSH 集成测试通过后**，才把 `engines.dsh` 扩大到明确验证过的
+4. **只有真实 DSH 集成测试通过后**，才最终确定 `engines.dsh` 中明确验证过的
    版本或范围。不要假定未来整个小版本都兼容。根据实际验证记录，更新
    `tools/release-plugin/check-release.mjs` 中的已测试范围，并与运行时版本保护
    保持一致。从 `bridge/package.json`

package/lib/projection/compatibility.d.mts

@@ -0,0 +1,2 @@
+export const supportedDSHVersions: readonly string[];
+export function supportsDSH(version: any): boolean;

package/lib/projection/compatibility.mjs

@@ -0,0 +1,4 @@
+// Enumerate verified carriers; a future prerelease is not implicitly compatible.
+// Keep package metadata and the release gate aligned with the native test receipt.
+export const supportedDSHVersions = Object.freeze(['0.2.1-rc.3', '0.2.1-rc.5']);
+export const supportsDSH = version => supportedDSHVersions.includes(version);

package/lib/projection/native.d.ts

@@ -87,6 +87,7 @@ export declare class LivePeer implements ProjectionPeer {
     private accept;
     private waitForProjection;
     private expireMissingInteractions;
+    private warnUnidentifiedInteraction;
     private interactionsReady;
     private loadChanges;
     private acceptNative;

package/lib/projection/native.js

@@ -5,6 +5,7 @@ import { dirname, resolve } from 'node:path';
 import { homedir } from 'node:os';
 import { createProjectionFold } from './fold-recording.mjs';
 import { FileProjection } from './files.js';
+import { supportsDSH } from './compatibility.mjs';
 import { interactionIdentity, expectedInteractionIds } from './interactions.js';
 const object = (value) => value !== null && typeof value === 'object' && !Array.isArray(value) ? value : {};
 const array = (value) => Array.isArray(value) ? value : [];
@@ -82,7 +83,7 @@ export function createProjectionHost(context) {
         }
         catch { /* The bundle may not run under a DSH CLI carrier. */ }
     }
-    const status = version === '0.2.1-rc.3' ? 'ok' : 'incompatible';
+    const status = supportsDSH(version) ? 'ok' : 'incompatible';
     const diagnostics = { createdPeers: 0, disposedPeers: 0, activePeers: 0 };
     const peers = new Set();
     const attachments = new Map();
@@ -259,7 +260,8 @@ export class LivePeer {
             const state = await this.ensure(sessionId);
             const request = object(frame.request);
             const nativeId = string(frame.eventId);
-            state.identifying.add(nativeId);
+            const kind = frame.event === 'approval/request' ? 'approval' : 'question';
+            state.identifying.set(nativeId, kind);
             let identity;
             try {
                 identity = await this.waitForProjection(state, () => interactionIdentity(sessionId, string(frame.event), request, state.records));
@@ -274,7 +276,7 @@ export class LivePeer {
             }
             if (!identity) {
                 this.expireMissingInteractions(state);
-                this.accept(state, { source: 'interaction-warning', frame: { kind: frame.event === 'approval/request' ? 'approval' : 'question', status: this.summary(this.nativeSummaries.get(sessionId) ?? { sessionId }).status }, atMs: 0 });
+                this.warnUnidentifiedInteraction(state, kind);
                 return;
             }
             const { id, callId } = identity;
@@ -405,13 +407,23 @@ export class LivePeer {
         if (ids.length)
             this.accept(state, { source: 'interaction-expire', frame: { ids, status: this.summary(this.nativeSummaries.get(state.id) ?? { sessionId: state.id }).status }, atMs: 0 });
     }
+    warnUnidentifiedInteraction(state, kind) {
+        this.accept(state, { source: 'interaction-warning', frame: { kind, status: this.summary(this.nativeSummaries.get(state.id) ?? { sessionId: state.id }).status }, atMs: 0 });
+    }
     async interactionsReady(state, signal, deadline = Date.now() + 2000) {
         const ready = await this.waitForProjection(state, () => state.followReady && !state.identifying.size &&
             expectedInteractionIds(state.id, state.records).every(id => this.deliveries.has(id) || state.expiredInteractions.has(id)) ? true : undefined, signal, deadline);
         // A durable audit can outlive its native waterfall after a crash. Keep the
         // session readable, but never present an unanswerable row as live.
-        if (!ready)
+        if (!ready) {
             this.expireMissingInteractions(state);
+            // The read deadline can settle before the correlation callback. Publish
+            // the fallback now so its snapshot cannot retain stale running state or
+            // omit the warning. The later callback may still identify a valid delivery.
+            const kind = state.identifying.values().next().value;
+            if (kind)
+                this.warnUnidentifiedInteraction(state, kind);
+        }
     }
     async loadChanges(state, seq) {
         const url = new URL('http://localhost/api/changes.summary');
@@ -458,7 +470,7 @@ export class LivePeer {
         if (!native)
             throw fault('not-found');
         const metadata = { live: true, scenario: 'live', sessionId: id, title: null, recordedAt: iso(native.updatedAt), summary: this.summary(native), cwd: native.cwd };
-        const state = { id, metadata, fold: createProjectionFold(metadata), records: [], nativeSeq: -1, listeners: new Set(), ready: Promise.resolve(), followReady: false, cancel: new AbortController(), changed: new Set(), identifying: new Set(), expiredInteractions: new Set() };
+        const state = { id, metadata, fold: createProjectionFold(metadata), records: [], nativeSeq: -1, listeners: new Set(), ready: Promise.resolve(), followReady: false, cancel: new AbortController(), changed: new Set(), identifying: new Map(), expiredInteractions: new Set() };
         this.lifetime.signal.addEventListener('abort', () => state.cancel.abort(), { once: true });
         this.sessions.set(id, state);
         state.ready = this.startStream('session/follow', { request: { address: { kind: 'session', sessionId: id }, assistantStream: true, maxMessages: 200 } }, async (frame) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-dshm",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Pair your iPhone or iPad with DeepSeek Harness over a private, authenticated connection",
   "license": "MIT",
   "repository": {
@@ -31,7 +31,7 @@
   ],
   "engines": {
     "node": ">=24",
-    "dsh": "0.2.1-rc.3"
+    "dsh": "0.2.1-rc.3 || 0.2.1-rc.5"
   },
   "dsh": {
     "bundle": {