dsh-remote-bridge 2.7.0 → 2.7.1

package/README.en.md

@@ -9,7 +9,7 @@
 </p>
 
 <p align="center">
-  <img alt="Version" src="https://img.shields.io/badge/version-v2.7.0-087f8c">
+  <img alt="Version" src="https://img.shields.io/badge/version-v2.7.1-087f8c">
   <img alt="DSH plugin" src="https://img.shields.io/badge/DeepSeek_Harness-plugin-1f2328">
   <img alt="Platforms" src="https://img.shields.io/badge/platform-Windows%20%7C%20macOS%20%7C%20Linux-586069">
   <img alt="License" src="https://img.shields.io/badge/license-AGPL--3.0-2da44e">
@@ -102,10 +102,10 @@ dsh plugin --profile web add dsh-remote-bridge
 dsh plugin --profile web add dsh-remote-bridge --registry https://registry.npmmirror.com
 
 # 2. tarball from the GitHub release
-dsh plugin --profile web add https://github.com/westanke/dsh-remote-bridge/releases/download/v2.7.0/dsh-remote-bridge-v2.7.0.tgz
+dsh plugin --profile web add https://github.com/westanke/dsh-remote-bridge/releases/download/v2.7.1/dsh-remote-bridge-v2.7.1.tgz
 
 # 3. tarball from the Gitee release (faster from mainland China)
-dsh plugin --profile web add https://gitee.com/westanke/dsh-remote-bridge/releases/download/v2.7.0/dsh-remote-bridge-v2.7.0.tgz
+dsh plugin --profile web add https://gitee.com/westanke/dsh-remote-bridge/releases/download/v2.7.1/dsh-remote-bridge-v2.7.1.tgz
 
 npx @deepseek-ai/dsh web
 ```
@@ -122,7 +122,7 @@ Restart DSH after installation, then open settings — The section is titled **
 To install a downloaded release archive:
 
 ```sh
-dsh plugin --profile web add ./dsh-remote-bridge-v2.7.0.tgz
+dsh plugin --profile web add ./dsh-remote-bridge-v2.7.1.tgz
 ```
 
 ## First connection
@@ -386,6 +386,10 @@ pnpm pack
 
 v2.5.0 was verified on DSH **0.2.1-rc.2** on real hardware: all 14/14 host services injected, the three jobs endpoints exercised, and the permission catalog returned the kernel's real three presets. The development baseline is upstream `dsh-v0.2.1-rc.2` (commit `687f282e8625c6b8d11ff58211a90524be2e4317`); see `engines.dsh` above for the supported range. CI covers Windows, Ubuntu, and macOS.
 
+**v2.7.1 verification status**: 76 test files / **701 cases** green; `typecheck`, `docs:check`, and the
+build all pass. This release touches only `agentFor` in `src/host/dsh-0.2-bridge.ts` plus its regression
+tests; every other byte is identical to v2.7.0.
+
 **v2.7.0 verification status**: 76 test files / 698 cases green, plus 8 Playwright browser cases
 (including the 375px narrow-viewport contract); `typecheck`, `docs:check`, and the build all pass.
 All four capabilities were exercised on an isolated DSH **0.2.1-rc.3** instance rather than inferred:
@@ -398,7 +402,17 @@ inside the zero-change set, and 4 slots retained with 0 removed.
 
 ## Project
 
-- Version: `v2.7.0`
+- Version: `v2.7.1`
+- **v2.7.1 is a defect-fix release**: the kernel's `sessionController.resolveAgent()` returns an
+  `{ agent }` / `{ error }` **envelope**, not the Agent itself (`dsh-api-session-controller/lib/index.js:365-368`
+  `liveAgent()` and `:221-246` `resolve()` both have that shape). The bridge used to hand the envelope
+  straight to `fileUploads.upload()`, so the kernel reading `agent.session.header.origin` blew up with
+  `DSH_TYPEERROR: Cannot read properties of undefined (reading 'header')` — on a real device this showed up
+  as "sending a file always fails with 400/500 and the message points nowhere", breaking both attachment
+  upload and agent-preset selection. The bridge now detects the envelope, unwraps `.agent` on success, and
+  rethrows `.error` as-is (keeping the kernel's stable code, so "session not found" is no longer flattened
+  into "session not running"), while still accepting a bare object. Three regression tests pin all three
+  return shapes.
 - **v2.7.0 aligns with DSH 0.2.1-rc.3 and lifts four capabilities**: (1) the model catalog now carries
   `contextWindow` / `maxTokens` — the kernel's `ModelCatalogModel` only has id/name/description, so the
   bridge resolves capacity through `llm.resolveModelInfo`, caching per `provider + model` for ten

package/README.md

@@ -9,7 +9,7 @@
 </p>
 
 <p align="center">
-  <img alt="Version" src="https://img.shields.io/badge/version-v2.7.0-087f8c">
+  <img alt="Version" src="https://img.shields.io/badge/version-v2.7.1-087f8c">
   <img alt="DSH plugin" src="https://img.shields.io/badge/DeepSeek_Harness-plugin-1f2328">
   <img alt="Platforms" src="https://img.shields.io/badge/platform-Windows%20%7C%20macOS%20%7C%20Linux-586069">
   <img alt="License" src="https://img.shields.io/badge/license-AGPL--3.0-2da44e">
@@ -93,10 +93,10 @@ dsh plugin --profile web add dsh-remote-bridge
 dsh plugin --profile web add dsh-remote-bridge --registry https://registry.npmmirror.com
 
 # ② GitHub Release 的 tarball
-dsh plugin --profile web add https://github.com/westanke/dsh-remote-bridge/releases/download/v2.7.0/dsh-remote-bridge-v2.7.0.tgz
+dsh plugin --profile web add https://github.com/westanke/dsh-remote-bridge/releases/download/v2.7.1/dsh-remote-bridge-v2.7.1.tgz
 
 # ③ Gitee Release 的 tarball（国内访问更快）
-dsh plugin --profile web add https://gitee.com/westanke/dsh-remote-bridge/releases/download/v2.7.0/dsh-remote-bridge-v2.7.0.tgz
+dsh plugin --profile web add https://gitee.com/westanke/dsh-remote-bridge/releases/download/v2.7.1/dsh-remote-bridge-v2.7.1.tgz
 
 npx @deepseek-ai/dsh web
 ```
@@ -112,7 +112,7 @@ npx @deepseek-ai/dsh web
 从 GitHub Release 下载离线安装包时，可直接安装 tarball：
 
 ```sh
-dsh plugin --profile web add ./dsh-remote-bridge-v2.7.0.tgz
+dsh plugin --profile web add ./dsh-remote-bridge-v2.7.1.tgz
 ```
 
 ## 第一次使用
@@ -419,6 +419,9 @@ v2.5.0 在 DSH **0.2.1-rc.2** 上完成真机验证：14/14 宿主服务全部
 权限档位目录返回内核真实三档。开发基线为上游 `dsh-v0.2.1-rc.2`（commit `687f282e8625c6b8d11ff58211a90524be2e4317`），
 兼容范围见上文 `engines.dsh`。CI 覆盖 Windows、Ubuntu 和 macOS。
 
+**v2.7.1 的验证状态**：76 个测试文件 / **701 个用例**全绿、`typecheck`/`docs:check`/构建通过。
+这一版只改 `src/host/dsh-0.2-bridge.ts` 的 `agentFor` 与对应回归测试，其余代码与 v2.7.0 逐字节相同。
+
 **v2.7.0 的验证状态**：76 个测试文件 / 698 个用例全绿、8 个 Playwright 浏览器用例
 （含 375px 窄屏契约）、`typecheck`/`docs:check`/构建通过。这一版的四项能力都在
 DSH **0.2.1-rc.3** 隔离实例上**实跑验过**，不是静态推断：插件清单返回
@@ -430,7 +433,15 @@ DSH **0.2.1-rc.3** 隔离实例上**实跑验过**，不是静态推断：插件
 
 ## 项目信息
 
-- 当前版本：`v2.7.0`
+- 当前版本：`v2.7.1`
+- **v2.7.1 是缺陷修复版**：内核 `sessionController.resolveAgent()` 返回的是 `{ agent }` / `{ error }`
+  **包装对象**而非 Agent 本体（`dsh-api-session-controller/lib/index.js:365-368` 的 `liveAgent()` 与
+  `:221-246` 的 `resolve()` 都是这个形状），桥此前把包装对象直接当 Agent 传给 `fileUploads.upload()`，
+  内核读 `agent.session.header.origin` 就炸成
+  `DSH_TYPEERROR: Cannot read properties of undefined (reading 'header')` —— 真机表现是
+  「发文件永远 400/500，报错信息完全指不到原因」，附件上传与 agent preset 选择两条路径都挂在这里。
+  现在识别包装形状、成功解出 `.agent`、失败原样抛 `.error`（保留内核稳定 code，「会话不存在」不再
+  被压成「会话没在跑」），同时保留裸对象兼容。新增 3 条回归测试钉住三种返回形状。
 - **v2.7.0 是对齐 DSH 0.2.1-rc.3 的能力提升版**：四项 —— ①模型目录补上 `contextWindow` / `maxTokens`
   （内核的 `ModelCatalogModel` 只有 id/name/description，容量得另走 `llm.resolveModelInfo`，桥按
   `provider + model` 缓存 10 分钟、失败不缓存、内核自己给了就不覆盖）；②插件清单多了右侧栏形态

package/docs/api/asyncapi.yaml

@@ -1,7 +1,7 @@
 asyncapi: 3.0.0
 info:
   title: DeepSeek Harness Mobile Events
-  version: 2.7.0
+  version: 2.7.1
   description: |
     Live file and authorized DSH chat events. Reconnect clients must refresh
     REST state; unbounded replay is not provided.

package/docs/api/openapi.yaml

@@ -1,7 +1,7 @@
 openapi: 3.1.0
 info:
   title: DeepSeek Harness Mobile API
-  version: 2.7.0
+  version: 2.7.1
   description: Versioned file and chat BFF for mobile and third-party DSH clients. HTTP and HTTPS are both supported.
 servers:
   - url: http://127.0.0.1:3090/api/v1
@@ -24,7 +24,7 @@ paths:
                 properties:
                   ok: { type: boolean, const: true }
                   version: { type: string, const: v1 }
-                  pluginVersion: { type: string, const: 2.7.0 }
+                  pluginVersion: { type: string, const: 2.7.1 }
   /debug/host-services:
     get:
       operationId: hostServices

package/lib/index.js

@@ -2899,9 +2899,23 @@ function createDsh02ApiProxy(host, options = {}) {
 			args: [sessionId, agentPreset]
 		});
 	});
-	/** Ask the host for the Agent backing a session before agent-scoped calls. */
+	/**
+	* Ask the host for the Agent backing a session before agent-scoped calls.
+	*
+	* 🔴 `sessionController.resolveAgent()` 返回的是**包装对象**，不是 Agent 本体：
+	* `{ agent }` 成功、`{ error }` 失败（内核
+	* `dsh-api-session-controller/lib/index.js:365-368` 的 `liveAgent()` 与 `:221-246`
+	* 的 `resolve()` 都是这个形状）。早先这里直接把包装对象当 Agent 返回，调用方读
+	* `agent.session.header` 就变成读 `undefined.header`，真机上表现为
+	* `DSH_TYPEERROR: Cannot read properties of undefined (reading 'header')` ——
+	* 上传附件、选 agent preset 全挂在这里，而报错信息完全指不到真正的原因。
+	*/
 	async function agentFor(sessionId) {
-		const agent = await host.sessionController.resolveAgent(sessionId);
+		const resolved = await host.sessionController.resolveAgent(sessionId);
+		const wrapped = resolved !== null && typeof resolved === "object" && ("agent" in resolved || "error" in resolved);
+		const failure = wrapped ? resolved.error : void 0;
+		if (failure !== void 0 && failure !== null) throw failure;
+		const agent = wrapped ? resolved.agent : resolved;
 		if (agent === void 0 || agent === null) throw Object.assign(/* @__PURE__ */ new Error(`no live Agent for session ${sessionId}`), { code: "session/agent-unavailable" });
 		return agent;
 	}
@@ -3211,7 +3225,7 @@ function createDsh02ApiProxy(host, options = {}) {
 }
 //#endregion
 //#region src/shared/version.ts
-const PLUGIN_VERSION = "2.7.0";
+const PLUGIN_VERSION = "2.7.1";
 //#endregion
 //#region src/host/capabilities.ts
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-remote-bridge",
-  "version": "2.7.0",
+  "version": "2.7.1",
   "description": "Versioned REST bridge for DeepSeek Harness: remote access for trusted clients (chat, files, devices) plus a Phone-settings panel inside the DSH WebUI.",
   "type": "module",
   "packageManager": "pnpm@11.19.0",