dsh-zen-remote 1.1.11 → 1.1.12

package/AGENTS.md

@@ -40,6 +40,30 @@ release 徽章和 profile 依赖示例由 `scripts/sync-doc-version.mjs` 按 `pa
 把测试挂掉。文档里的锚点变了就更新那个脚本：找不到标记它直接非零退出，不会
 默默通过。
 
+**发版**：全部由 tag 驱动，本地只做一步。
+
+```sh
+npm version patch      # 改 package.json + 同步两份 README + 建 commit 和 v* tag
+git push --follow-tags # 推 tag 才是真正的触发器
+```
+
+推上去之后 `.github/workflows/publish.yml` 依次做：装依赖 → `pnpm build` →
+**`git diff --exit-code -- lib`**（入库产物必须与重新构建的结果一致，挡住
+「改了 src 忘了 build 就打 tag」）→ `pnpm verify` → `pnpm test` →
+tag 名与 `package.json` 版本一致性 → `pnpm publish`（npm Trusted Publishing，
+OIDC 无令牌，provenance 自动生成）→ **建 GitHub Release**。
+
+Release 那步刻意排在 npm 之后：它宣告的是「这个版本已经发出去了」，npm 失败就
+不该留下一个指向不存在版本的发布页。发布说明用 `--generate-notes` 按上一个 tag
+以来的提交自动生成，所以**提交信息就是 changelog**，不另外维护文件。这一步可重入
+（先 `gh release view` 查在不在，在就跳过），重跑失败的 workflow 不会因为
+Release 已存在而挂掉。
+
+需要人工配置的只有一处：npmjs.com 的包设置里登记可信发布者
+`KyoMio/dsh-zen-remote` + 文件名 `publish.yml`。GitHub Release 那步用的是
+workflow 自带的 `GITHUB_TOKEN`，不需要额外密钥——但 job 的 `permissions` 里
+`contents` 必须是 `write`（原来是 `read`）。
+
 ## 深度文档
 
 | 文件 | 内容 |

package/README.md

@@ -3,7 +3,7 @@
 
 <p align="center">
 <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-0B7285?style=flat-square" alt="MIT"></a>
-<img src="https://img.shields.io/badge/release-v1.1.11-5B4CF0?style=flat-square" alt="v1.1.11">
+<img src="https://img.shields.io/badge/release-v1.1.12-5B4CF0?style=flat-square" alt="v1.1.12">
 <img src="https://img.shields.io/badge/DSH-Web%20Profile-5B4CF0?style=flat-square" alt="DSH Web Profile">
 </p>
 
@@ -29,7 +29,11 @@ dsh plugin add dsh-zen-remote
 
 Restart `dsh web` afterwards. The mobile UI and the gateway both come up — there is no config line to hand-write.
 
-> Compatibility: developed and tested against DSH `0.1.1-rc.2` (web profile); last verified 2026-08-22.
+> **Compatibility — one build, both runtimes.** Verified live on DSH `0.1.1-rc.2` and `0.1.2-rc.1` (web profile), 2026-09-04.
+>
+> 0.1.2 removed `@deepseek-ai/dsh-client-runtime` and put the web UI behind a signed cookie, which would have broken the mobile UI and locked the phone out of the gateway. The plugin carries its own store engine instead of importing that package, probes for the services 0.1.2 moved (`uiWorkspace`, `uiSession`) and falls back to the 0.1.1 shapes when they are absent, reads a turn's events through either `session.events` or `session.snapshotEvents()`, and lets the gateway do the browser-token handshake on the phone's behalf — all of it inert on 0.1.1, where the token endpoint does not exist.
+>
+> One thing to know on 0.1.2: the web UI now rejects requests whose `Host` is not trusted. Reaching DSH through this plugin's gateway is unaffected (the gateway presents every request as `127.0.0.1`), but pointing a browser straight at `http://<LAN-IP>:3080` returns 403 unless you start `dsh web --trusted-host <host>`.
 
 To uninstall: `dsh plugin remove dsh-zen-remote` (or delete the two lines from your profile's `dependencies` and `bundles`) and restart `dsh web`. To also wipe the pairing data, delete `~/.dsh/lan-gate-state.json` and `~/.dsh/lan-gate.config.json`.
 
@@ -41,7 +45,7 @@ Edit `~/.dsh/profiles/web/package.json` by hand — one line under `dependencies
 ```jsonc
 {
   "dependencies": {
-    "dsh-zen-remote": "^1.1.11"        // for local development: "link:/path/to/dsh-zen-remote"
+    "dsh-zen-remote": "^1.1.12"        // for local development: "link:/path/to/dsh-zen-remote"
   },
   "dsh": { "profile": { "bundles": [
     "@deepseek-ai/dsh-base",

package/README.zh-CN.md

@@ -3,7 +3,7 @@
 
 <p align="center">
 <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-0B7285?style=flat-square" alt="MIT"></a>
-<img src="https://img.shields.io/badge/release-v1.1.11-5B4CF0?style=flat-square" alt="v1.1.11">
+<img src="https://img.shields.io/badge/release-v1.1.12-5B4CF0?style=flat-square" alt="v1.1.12">
 <img src="https://img.shields.io/badge/DSH-Web%20Profile-5B4CF0?style=flat-square" alt="DSH Web Profile">
 </p>
 
@@ -29,7 +29,11 @@ dsh plugin add dsh-zen-remote
 
 装完重启 `dsh web`，手机界面与网关一起生效，不需要再手写任何配置行。
 
-> 兼容性：在 DSH `0.1.1-rc.2`（web profile）上开发并实测，最后验证 2026-08-22。
+> **兼容性——同一份产物，两个运行时。** 在 DSH `0.1.1-rc.2` 与 `0.1.2-rc.1`（web profile）上均实机验证，2026-09-04。
+>
+> 0.1.2 删掉了 `@deepseek-ai/dsh-client-runtime`，并把网页界面挪到签名 cookie 之后——照原样会让手机界面加载失败、手机经网关也进不来。本插件改为自带 store 实现而不 import 那个包；对 0.1.2 搬了家的服务（`uiWorkspace`、`uiSession`）按存在探测、取不到就走 0.1.1 的老路；回合事件 `session.events` 和 `session.snapshotEvents()` 两种读法都认；浏览器 token 交换由网关代手机完成——这些在 0.1.1 上全部惰性，因为那边根本没有 token 端点。
+>
+> 0.1.2 上有一点要知道：网页界面现在会拒绝 `Host` 不受信的请求。经本插件网关访问不受影响（网关把每个请求都以 `127.0.0.1` 的身份递上去），但拿浏览器直接开 `http://<局域网IP>:3080` 会得到 403，除非启动时加 `dsh web --trusted-host <host>`。
 
 卸载：`dsh plugin remove dsh-zen-remote`（或从 profile 的 `dependencies` 与 `bundles` 里删掉那两行），重启 `dsh web` 即恢复原状；要清掉配对数据再删 `~/.dsh/lan-gate-state.json` 与 `~/.dsh/lan-gate.config.json`。
 
@@ -41,7 +45,7 @@ dsh plugin add dsh-zen-remote
 ```jsonc
 {
   "dependencies": {
-    "dsh-zen-remote": "^1.1.11"        // 本地开发换成 "link:/path/to/dsh-zen-remote"
+    "dsh-zen-remote": "^1.1.12"        // 本地开发换成 "link:/path/to/dsh-zen-remote"
   },
   "dsh": { "profile": { "bundles": [
     "@deepseek-ai/dsh-base",

package/docs/interface.md

@@ -119,7 +119,7 @@ composer 最左的回形针打开的是**手机本地**的文件选择器（iOS
 
 **修复**
 
-- 适配 dsh-vision-router(2.0.1):composer 识图开关在手机端压成 28px 圆形
+- 适配 dsh-vision-router(2.0.1 / 2.1.1):composer 识图开关在手机端压成 28px 圆形
   图标钮(眼睛为 CSS mask 图标,aria-label / aria-pressed 照旧),不再把
   模型名挤出 composer 行;桌面端保持插件原样(见兼容插件清单)。
 - 适配 DSH `0.1.1`：活动 chip 点击失效（点了退回信息卡）。三处上游变化同时命中
@@ -248,7 +248,7 @@ composer 最左的回形针打开的是**手机本地**的文件选择器（iOS
 - [@opendsh/dsh-plugin-scheduled-tasks](https://github.com/Ceelog/dsh-plugins)(定时任务,主屏 chips 行自动收割入口)——本机实测 **0.2.3**
 - dsh-at-file(@文件引用;它和本插件的附件 chip 读的是同一份草稿 token,手机端会为一个上传文件同时画出缩略图和文件名两条,故隐藏它 `.dsh-uploads/` 下那几行,其余 @ 引用不动;桌面端不隐藏——那边本插件的 chip 是关掉的,它是唯一的呈现)——本机实测 **0.6.7**
 - [@ace-zone/dsh-market](https://www.npmjs.com/package/@ace-zone/dsh-market)(插件市场;它的弹窗顶栏在手机上放不下,关闭的 × 被挤出面板外,故隐藏标语/版本号/官网链接三个装饰位并让标题省略号收缩,语言切换和 × 保留;认插件自己渲染的 `.dshm-ver[title="@ace-zone/dsh-market"]` 版本片,同名的其他"市场"插件不会被误伤)——本机实测 **0.1.66**
-- [dsh-vision-router](https://github.com/ysr666/dsh-vision-router)(视觉桥,composer 行内的识图开关胶囊;手机端压成 28px 圆形图标钮——原胶囊 👁+文字+激活 ✓ 约 90px 定宽,而手机 composer 行不换行、模型座位是唯一可收缩项,会被它挤没;三条文字 span 全部隐藏,改由 CSS mask 画一只 currentColor 眼睛,开合状态仍走插件自己的品牌描边/着色与 `aria-pressed`,可访问名走按钮自带的 aria-label)——本机实测 **2.0.1**
+- [dsh-vision-router](https://github.com/ysr666/dsh-vision-router)(视觉桥,composer 行内的识图开关胶囊;手机端压成 28px 圆形图标钮——原胶囊 👁+文字+激活 ✓ 约 90px 定宽,而手机 composer 行不换行、模型座位是唯一可收缩项,会被它挤没;按钮里只留一只 16px 眼睛:span 一律隐藏;2.1.x 起插件自带 svg 图标,只保留第一个 svg、用兄弟选择器隐掉其后的(当前是激活态的对钩),我们自己的 `::before` mask 眼睛降级为 `:has(svg)` 兜底、只给 2.0.x 的文字写法用;开合状态仍走插件自己的品牌描边/着色与 `aria-pressed`,可访问名走按钮自带的 aria-label)——本机实测 **2.0.1** 与 **2.1.1**。2.1.1 把 👁/✓ 从文字 span 换成 svg,只按 2.0.x 写的规则会渲染出**两只眼**且对钩无人隐藏(2026-09-04 用户报);回归由 `test/vision-router-compat-css.test.cjs` 守着
 - [dsh-web-ui 全家桶](https://www.npmjs.com/package/@linxin666/dsh-web-ui-all)(文件树 / 预览 / 任务看板 / SSH / 宠物 / 会话统计 / 远程配对 / 设置)——沿用上游兼容规则,本次未扩展
 
 ## 安装

package/dsh-push.mjs

@@ -180,6 +180,30 @@ export function pendingQuestionText(rawArguments) {
   } catch { return '' }
 }
 
+/**
+ * Session event log, read compatibly across both DSH versions: 0.1.1 exposes
+ * `session.events` as an array getter; 0.1.2 replaced it with the
+ * `session.snapshotEvents()` method. When neither is available, return [] so
+ * turnSummary walks its own "not an array → ''" path.
+ * @param session - the session object, possibly undefined.
+ * @returns the event array.
+ */
+export function sessionEvents(session) {
+  if (session && Array.isArray(session.events)) return session.events
+  if (session && typeof session.snapshotEvents === 'function') {
+    // ponytail: snapshotEvents() with no argument copies the WHOLE event log
+    // on every call. That is acceptable here — this branch only runs when
+    // INCLUDE_SUMMARY is on (dsh-push.mjs:53, off by default) and at most once
+    // per turn end. Slicing would need the turn's start seq, and the
+    // agent/turn-stopping payload carries none: its emitter (0.1.2
+    // dsh-agent-loop) sends only `{ turn, signal }` plus the injected
+    // `agent` — a turn NUMBER, not an event-log seq, and the two are not the
+    // same thing. If a future payload adds a start seq, pass it as fromSeq.
+    return session.snapshotEvents()
+  }
+  return []
+}
+
 const skip = (reason) => ({ shouldNotify: false, title: '', body: '', reason })
 
 /**
@@ -420,7 +444,7 @@ export function apply(ctx) {
     fire({
       kind: 'turn-end',
       delegationDepth: header && header.delegationDepth,
-      summary: INCLUDE_SUMMARY ? turnSummary(session && session.events, payload && payload.turn) : ''
+      summary: INCLUDE_SUMMARY ? turnSummary(sessionEvents(session), payload && payload.turn) : ''
     })
   }
   for (const event of EVENTS) {

package/lan-gate.mjs

@@ -9,7 +9,10 @@ import { fileURLToPath } from 'node:url'
 import { dirname, join } from 'node:path'
 
 export const name = 'dsh-zen-remote-gateway'
-export const inject = ['subprocess']
+// `connection` (both DSH versions provide it — unlike 0.1.2-only services such
+// as uiWorkspace) lets the host side read the browser-auth token URL, so
+// adding it here does not stop the plugin activating on 0.1.1.
+export const inject = ['subprocess', 'connection']
 
 const here = dirname(fileURLToPath(import.meta.url))
 const serverFile = join(here, 'lib', 'lan-gate-server.cjs')
@@ -39,10 +42,22 @@ export function apply(ctx, config) {
 
   const start = async () => {
     try {
+      // 0.1.2 起浏览器要签名 cookie 才能进；token 只有 `GET /?token=` 一处收。
+      // authenticatedUrl 是 connection 服务的公开方法，0.1.1 没有它——用它是不是
+      // 函数来判断跑在哪一版，比看版本号可靠。只把这个 URL 交给子进程，密钥一律
+      // 不传。目标端口与网关子进程的解析一致：显式 env > cordis config > 3080。
+      const targetPort = Number(process.env.LAN_GATE_TARGET_PORT || 3080)
+      const tokenUrl = ctx.connection && typeof ctx.connection.authenticatedUrl === 'function'
+        ? ctx.connection.authenticatedUrl('http://127.0.0.1:' + targetPort)
+        : undefined
       const nodePath = await ctx.subprocess.resolveExecutable('node')
+      const env = { ...process.env }
+      if (tokenUrl !== undefined) env['LAN_GATE_UPSTREAM_TOKEN_URL'] = tokenUrl
+      else delete env['LAN_GATE_UPSTREAM_TOKEN_URL'] // 0.1.1 模式：变量不能残留
       handle = ctx.subprocess.spawn({
         argv: [nodePath, serverFile],
         cwd: here,
+        env,
         stdio: {
           stdin: 'ignore',
           stdout: { maxBytes: 131072 },