dsh-plugin-dshm 0.0.0-stage → 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+## 0.1.0 — 2026-10-28
+
+Initial DSHM bridge release for DeepSeek Harness 0.2.1-rc.3.
+
+- Pair an iPhone or iPad using a short-lived code and pinned TLS; authenticate
+  paired devices and revoke access from the DSH settings card.
+- Follow sessions, send prompts, answer approvals/questions and transfer files
+  over a reachable private network or the user's own VPN.
+- English and Simplified Chinese settings card with optional Tailscale setup
+  guidance under “Not on the same Wi-Fi / 不在同一 Wi-Fi”.
+- Optional encrypted push sender; proxy deployment and real-device notification
+  delivery are separate from this package's local verification.
+- MIT license and a separate plugin-only public source repository. The iOS app,
+  private development history and push-proxy source are not part of this release.
+
+Fresh-install and remote-phone acceptance of the new Tailscale setup helper
+remain pending. Earlier Windows LAN/remote tests used the previous package.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 DSHM contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,229 @@
-# Temporary Holding Version
+# DSHM bridge
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+[简体中文](README.zh-CN.md)
+
+Control DeepSeek Harness sessions on your computer from the DSHM app on your
+iPhone or iPad. The agent keeps running on your computer; the bridge connects
+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.
+- 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
+  local TLS certificate.
+- Both devices on a network that permits direct communication, or on your own
+  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
+the local test-client and Simulator results. Mainland China is outside the v1
+release scope; mainland network reachability is not claimed.
+
+## Install in DSH
+
+1. Open the **Plugins** page in the DSH instance you want to control.
+2. Install this package spec using the page's package installation control:
+
+   ```text
+   dsh-plugin-dshm
+   ```
+
+3. Let DSH's plugin manager install the bundle and dependencies. Restart DSH
+   when requested, then open **Settings → DSHM**.
+
+Use DSH's plugin manager rather than editing its profile files or copying files
+into the installed application. The plugin is installed into the selected DSH
+profile; installing it into one profile does not enable every other profile.
+
+DSH 0.2.1 installs packages by name from npm; there is no central DSH plugin
+market. No DSHM custom plugin index is published for this release.
+
+## Pair your device
+
+### Guided remote setup
+
+Phone not on the same Wi-Fi as this computer? Use Tailscale. On the same Wi-Fi,
+nothing else is needed. Open **Settings → DSHM → Not on the same Wi-Fi**.
+The optional helper checks the official Tailscale app on Windows/macOS, links
+to its official installer instructions, and can open the installed app on the
+DSH host. Complete installation, system approvals and browser sign-in yourself.
+If viewing DSH from another computer, install Tailscale on the **DSH host**.
+The plugin does not embed a VPN, install software automatically, or change
+Tailscale accounts, DNS, routes, exit nodes, firewall or proxy settings.
+
+Install Tailscale on your iPhone/iPad, sign in to the same personal account,
+and connect both ends. For organization accounts, both devices must belong to
+the same permitted tailnet; account sign-in does not override access policy.
+Then select **Pair for remote access** and scan the fresh QR in DSHM. An older
+LAN-only pairing does not automatically acquire the new VPN address: forget
+the old computer in DSHM, revoke its old device entry on the host, and pair again.
+An active earlier QR is replaced when you explicitly create the fresh one.
+
+The card distinguishes PC readiness from **Phone connected over Tailscale**.
+Test with your phone on cellular or a different Wi-Fi.
+**Pair a device** remains available for ordinary LAN use without Tailscale.
+Missing software, canceled installation, sign-out and unavailable status checks
+do not disable local pairing. Removing this plugin leaves Tailscale installed.
+Fresh-install and remote-phone acceptance of this helper remain pending.
+Earlier Windows LAN/remote tests used the previous package.
+
+The helper reads local Tailscale state only while setup is open or when you
+request remote pairing. It returns connection state and local VPN addresses,
+not account identities, login links or peer inventories. Tailscale is a separate
+service with its own account and privacy terms; DSHM's pinned TLS remains in use
+over that VPN.
+
+### Local pairing
+
+1. Keep DSH running. On the computer, open **Settings → DSHM → Pair a device**.
+2. In DSHM on your iPhone or iPad, add a computer and scan the displayed QR code.
+3. Allow local-network access when prompted. The computer's DSHM card should
+   show your device as **Connected**.
+
+The QR code is private, single use and valid for five minutes. Do not share it
+or include it in screenshots or support reports. **Cancel pairing** closes the
+window; if it expires, start a new one. Pair only devices you trust: paired
+devices can view sessions and files, send prompts and answer tool approvals.
+
+To disconnect a lost or unwanted device, use **Settings → DSHM → Revoke**, then
+confirm **Revoke device**. This closes its active connection and prevents that
+pairing from reconnecting. Pair again if you later want to restore access.
+
+## Network setup
+
+- **macOS:** allow **DeepSeek Harness** in **System Settings → Privacy & Security
+  → Local Network**. If you run `dsh web` in Terminal or another terminal app,
+  allow that app too. DSHM on iOS also needs Local Network permission.
+- **Windows:** if Windows Firewall asks about the DSH host process, allow it on
+  your trusted **Private networks**. Keep **Public networks** disabled. The
+  bridge does not change firewall rules for you; Windows runtime verification
+  remains pending.
+- **Wi-Fi:** start with the same trusted home/work Wi-Fi. Guest networks,
+  hotspots and router client isolation may prevent devices from reaching each
+  other even when both have internet access.
+- **Proxies and VPNs:** enable **bypass LAN/local networks** on both devices, or
+  temporarily turn the interfering proxy off to check the route. Keep LAN and
+  the chosen VPN's device addresses reachable; a rule that routes all traffic
+  through a proxy can prevent pairing.
+- **Not on the same Wi-Fi:** connect both devices to the same Tailscale network (or
+  another VPN you control) and permit traffic between them. Keep the computer
+  awake and DSH running. DSHM does not provide a cloud relay for session traffic. Bonjour may
+  not cross a VPN; pair while both devices can reach an address included by the
+  computer.
+
+The bridge normally listens on TCP **47390** on private/LAN and Tailscale
+addresses. It uses a separate listener from DSH's Web UI. Do not expose that
+port by router port forwarding or change DSH's Web server to a public bind.
+Bonjour discovery uses the local network. If discovery sees your computer but
+connection fails, check permissions, VPN/proxy bypass and client isolation first.
+
+## What is sent, and where
+
+The bridge sends session messages, tool results, approvals, selected files and
+declared deliverables to your authenticated, paired device over pinned TLS.
+Prompts, answers and attachments from that device go back to DSH on your
+computer. The bridge runs no cloud agent and has no analytics service or relay
+for session traffic. It does not read or forward DSH's provider-credential store.
+DSH itself still contacts the model providers and tools you configured, under
+their own settings.
+
+On the LAN, Bonjour announces the bridge's host identity/version and private
+addresses for discovery. Local bridge identity and pairing records stay under
+`$DSH_HOME/dshm/` (`~/.dsh/dshm/` with the default DSH home); private files should
+never be pasted into issues. Installing a package or using a remote plugin
+index makes DSH contact the package registry/index host.
+
+**Optional push notifications use a separate proxy and Apple Push Notification
+service (APNs).** Without a configured `pushProxyUrl`, the bridge makes no push
+network requests and does not advertise push support. Configuring a URL enables
+periodic health checks; push support is advertised only while the proxy is
+reachable and the bridge's session observer is working. This package includes the bridge sender; the proxy and app are separate. iOS push registration,
+the Notification Service Extension and real locked-phone delivery remain
+separate work; they have not been verified by the local backend tests.
+
+For push registration, the app sends its APNs device token and sandbox/production
+environment to the selected HTTPS proxy. The proxy stores that routing mapping
+and encrypts its authentication secret under a separate wrapping key. The app
+shares the returned registration and a separate notification-content key with
+the paired bridge over DMP. The bridge stores these keys and preferences in its
+private `$DSH_HOME/dshm/push.json` file (mode 0600). The APNs provider key stays
+only in the proxy's secret configuration; it is never supplied to the bridge.
+
+When notifications are configured and registered, the bridge sends the proxy
+an encrypted session title and short event summary, plus an opaque push ID,
+event category, grouping ID and request signature. The proxy forwards the
+ciphertext and a generic fallback alert to APNs. The proxy and APNs do not
+receive the notification-content key or decrypted title/summary; routing
+metadata, timing and payload size remain visible, and the proxy receives the
+client IP at the network layer. The application logs counters only and stores
+hashed IP quota buckets. Push does not upload files or full transcripts, and
+an authenticated live connection suppresses sends to that device.
+
+Unregistering notifications or revoking a device removes its local push
+registration before a best-effort request to delete the proxy mapping. If the
+proxy is unreachable, remote deletion is not confirmed; uninstalling the
+package alone does not delete a remote mapping. Alerts already accepted by
+APNs cannot be recalled. Terminal output remains read-only; the bridge does
+not provide an interactive remote terminal.
+
+## Remove the bridge
+
+1. In **Settings → DSHM**, revoke devices you no longer want to authorize.
+2. Open **Plugins**, find `dsh-plugin-dshm`, and remove it from the active
+   profile through DSH's plugin manager. Repeat for any other profile where you
+   installed it, including an optional `dshm` CLI profile.
+3. Restart the affected DSH host when requested. The DSHM settings card and its
+   listener should be gone from that host.
+
+Uninstalling the package is separate from deleting its private identity and
+pairing state. Preserve `$DSH_HOME/dshm/` if you intend to reinstall. If you
+deliberately choose a full reset, stop every DSH host using that home first and
+remove only the bridge's `dshm` state directory; existing devices will need to
+forget the old host and pair again. Do not delete the whole DSH home or its
+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.
+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`
+   as part of the compatibility change; changing package metadata alone does
+   not enable a new runtime. Adapt the test carrier path if needed; do not
+   bypass a failure or test against the old runtime while claiming the new one. Record the
+   actual DSH version and results. Complete the Windows checklist before
+   claiming a newly supported Windows combination.
+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
+   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.
+   Regenerate and validate the plugin index from `bridge/package.json`, keeping
+   its compatibility field identical.
+5. Bump the bridge version, update these READMEs, inspect `npm pack --dry-run`,
+   and install/boot the exact tarball through the isolated plugin manager.
+6. Audit the exact release tarball and record its SHA-256 before publication.
+   The owner signs in to npm and publishes that audited tarball with lifecycle
+   scripts disabled. Verify installation by name through DSH's plugin manager
+   in an isolated profile. Never publish a replacement over an existing version.
+
+The public repository is a plugin-only source snapshot. Shared protocol source,
+fixtures and integration tools remain in the private development repository;
+monorepo build/test commands above require that maintainer checkout. The npm
+package includes its protocol runtime and dependency license notices, so users
+do not need those development sources. No private monorepo history, iOS app or
+push-proxy source is included in the public repository.
+
+Licensed under [MIT](LICENSE). See [CHANGELOG](CHANGELOG.md) for release changes.
+
+[Source](https://github.com/JeremyCruzFang/dsh-plugin-dshm) ·
+[Issues](https://github.com/JeremyCruzFang/dsh-plugin-dshm/issues)

package/README.zh-CN.md

@@ -0,0 +1,190 @@
+# DSHM 桥接插件
+
+[English](README.md)
+
+通过 iPhone 或 iPad 上的 DSHM，查看和控制电脑里的 DeepSeek Harness 会话。
+智能体仍在你的电脑上运行；手机通过局域网或你自己的 VPN 连接桥接插件。
+
+## 环境与兼容性
+
+- DeepSeek Harness **0.2.1-rc.3**，这是当前 `engines.dsh` 声明的精确版本。
+  DSH 仍处于 Developer Preview 阶段，不能假定新版本自动兼容。
+- 电脑正在运行 DSH 桌面应用或 `dsh web`，手机或平板已安装兼容的 DSHM
+  构建版本。这个 npm 包不会安装 iOS 应用。
+- DSH 运行环境使用 Node 24 或更新版本，且 PATH 中有 `openssl`，供首次
+  创建本地 TLS 证书使用。
+- 两台设备之间能够直接通信，或已连接到你自己的 Tailscale 等 VPN。
+
+目前已在 macOS 上使用 DSH 0.2.1-rc.3 验证桌面应用及隔离的 `dsh web`。
+Windows 是计划支持的平台，但原生运行和防火墙验证清单尚未完成；macOS
+通过的测试不能代替 Windows 验证。真实手机的网络测试也与本地测试客户端、
+Simulator 的结果分别记录。v1 不包含中国大陆市场，也不声明已验证大陆网络可达性。
+
+## 在 DSH 中安装
+
+1. 在需要远程控制的 DSH 实例中打开 **Plugins（插件）** 页面。
+2. 使用页面上的包安装入口，输入以下包名：
+
+   ```text
+   dsh-plugin-dshm
+   ```
+
+3. 让 DSH 插件管理器安装插件及依赖。按提示重启 DSH，然后打开
+   **Settings（设置）→ DSHM**。
+
+请使用 DSH 插件管理器，不要手动修改配置文件，也不要把文件复制进已安装的
+DSH 应用目录。安装只作用于所选的 DSH profile，不会自动启用其他 profile。
+
+DSH 0.2.1 通过包名从 npm 安装插件，没有中央插件市场。本版本未发布 DSHM
+自定义插件索引。
+
+## 配对手机或平板
+
+1. 保持 DSH 运行。在电脑上打开 **Settings → DSHM → Pair a device（配对设备）**。
+2. 在 iPhone 或 iPad 的 DSHM 中添加电脑，扫描显示的二维码。
+3. 出现提示时允许本地网络访问。电脑上的 DSHM 设置卡片应显示该设备为
+   **Connected（已连接）**。
+
+二维码只能使用一次，五分钟后过期。它包含临时配对凭据，请勿转发，也不要
+放进截图或问题报告。点击 **Cancel pairing（取消配对）** 可以提前关闭；过期
+后重新开始配对即可。只配对你信任的设备：已配对设备可以查看会话和文件、
+发送提示词、回答工具审批。
+
+手机丢失或不再需要访问时，在 **Settings → DSHM** 中点击该设备的
+**Revoke（撤销）**，再确认 **Revoke device（撤销设备）**。插件会关闭其当前
+连接，并阻止旧配对重新连接。以后需要恢复访问时，可以重新配对。
+
+## 网络设置
+
+### 引导设置远程连接
+
+手机和这台电脑不在同一 Wi-Fi？使用 Tailscale。在同一 Wi-Fi 下无需其他设置。
+打开 **Settings → DSHM → 不在同一 Wi-Fi**。这个可选向导检查 Windows／
+macOS 上的官方 Tailscale 程序，提供官方安装说明，并可打开 DSH 宿主电脑上的
+Tailscale。安装、系统授权和浏览器登录由你亲自完成。如果从另一台电脑打开
+DSH Web UI，请把 Tailscale 安装在 **运行 DSH 的电脑** 上。
+
+手机安装 Tailscale，使用同一个个人账号登录，并连接两端。组织账号需确保
+两台设备处于同一且允许通信的 tailnet；登录相同账号不会绕过组织访问策略。
+连接后点 **Pair for remote access**，在 DSHM 扫描新二维码。旧的仅局域网配对
+不会自动获得新 VPN 地址：先在 DSHM 忘记旧电脑，在宿主撤销旧设备条目，再
+重新配对。主动生成新二维码会替换尚未使用的旧二维码。
+
+向导区分“电脑已就绪”和“设备已通过 Tailscale 连接”。请让手机使用蜂窝网络
+或其他 Wi-Fi 进行测试。**Pair a device** 始终保留局域网配对入口，无须
+安装 Tailscale。取消安装、未登录或状态检查失败都不会关闭局域网配对。
+
+插件不会自动安装 VPN，不修改 Tailscale 账号、DNS、路由、出口节点、防火墙
+或代理设置，也不收集登录凭据。卸载插件会保留已安装的 Tailscale。新向导的全新安装及
+远程手机验收尚未完成；此前 Windows 局域网／远程测试使用旧版包，不能代替
+新向导验收。
+
+- **macOS：** 在 **系统设置 → 隐私与安全性 → 本地网络** 中允许
+  **DeepSeek Harness**。如果通过终端运行 `dsh web`，也要允许相应的终端
+  应用。iOS 上的 DSHM 同样需要“本地网络”权限。
+- **Windows：** Windows 防火墙询问 DSH 宿主程序的联网权限时，允许你信任的
+  **专用网络（Private networks）**，保持 **公用网络（Public networks）**
+  禁用。桥接插件不会替你修改防火墙规则；Windows 的运行验证仍待完成。
+- **Wi-Fi：** 建议先让两台设备连接同一个可信的家庭或办公 Wi-Fi。访客网络、
+  手机热点或路由器的客户端隔离功能，可能让设备都能上网却无法互相连接。
+- **代理和 VPN：** 在两台设备上开启 **绕过局域网／本地网络（bypass LAN）**，
+  或暂时关闭影响连接的代理以检查路由。局域网地址和所用 VPN 的设备地址都
+  必须可达；把全部流量送入代理的规则可能阻止配对。
+- **不在同一 Wi-Fi：** 让电脑和手机加入同一个 Tailscale 网络或你管理的其他 VPN，
+  并允许两台设备之间通信。电脑需要保持唤醒，DSH 需要保持运行。DSHM 没有
+  自营会话流量中继。Bonjour 发现通常不会穿过 VPN；配对时应确保手机能够
+  连接电脑提供的某个地址。
+
+桥接插件默认在局域网／私有地址及 Tailscale 地址的 TCP **47390** 端口监听，
+与 DSH Web UI 使用不同的监听端口。不要为它设置路由器公网端口转发，也不要
+把 DSH Web 服务改成公网监听。Bonjour 使用本地网络；如果能够发现电脑却
+连接不上，先检查权限、代理／VPN 绕过设置及客户端隔离。
+
+## 数据会发送到哪里
+
+只有打开远程设置或请求远程配对时，向导才读取本机 Tailscale 状态；返回连接
+状态和本机 VPN 地址，不返回账号身份、登录链接或其他设备清单。Tailscale 是
+独立服务，有自己的账号和隐私条款；DSHM 在 VPN 上仍使用固定证书的 TLS。
+
+桥接插件通过固定证书的 TLS 连接，把会话消息、工具结果、审批、所选文件及
+已声明的交付文件发送给经过认证的已配对设备。手机发送的提示词、回答和附件
+会交给电脑上的 DSH。桥接插件不运行云端智能体，也不使用分析服务或 DSHM
+会话流量中继；它不会读取或转发 DSH 的模型服务凭据存储。DSH 本身仍会按照你
+自己的配置连接模型服务和工具，遵循这些服务的设置。
+
+Bonjour 会在局域网内公布桥接宿主的标识、协议版本和私有网络地址，供发现
+使用。本地桥接身份和配对记录保存在 `$DSH_HOME/dshm/`，使用默认 DSH home
+时为 `~/.dsh/dshm/`。请勿把其中的私有文件粘贴到问题报告。安装插件或使用
+远程索引时，DSH 会访问相应的包仓库和索引服务器。
+
+**可选的推送通知经过独立代理及 Apple 推送通知服务（APNs）。** 未配置
+`pushProxyUrl` 时，桥接插件不会发起推送网络请求，也不会声明支持推送。
+配置地址后会定期检查代理健康状态；只有代理可达且会话观察功能正常时，才
+声明支持推送。本软件包包含桥接发送端，代理及应用另行提供。iOS 推送注册、
+通知服务扩展及真实锁屏手机的通知送达仍是独立工作，本地后端测试不代表
+这些环节已经验证。
+
+注册推送时，应用将 APNs 设备令牌及沙盒／生产环境标识发送给所选的 HTTPS
+代理。代理保存这份路由映射，以及用独立包装密钥加密的认证密钥。应用通过
+DMP 将返回的注册信息和另一把通知内容密钥交给已配对的桥接插件。桥接插件
+把这些密钥和偏好保存在私有的 `$DSH_HOME/dshm/push.json`（权限 0600）中。
+APNs 提供方密钥只存在代理的密钥配置中，不会交给桥接插件。
+
+配置并完成注册后，桥接插件会把加密的会话标题、简短事件摘要，以及不透明
+推送 ID、事件类别、分组 ID 和请求签名发送给代理。代理将密文和通用备用
+提示转交 APNs。代理及 APNs 都不会收到通知内容密钥，也无法直接读取解密后
+的标题／摘要；路由元数据、时间和载荷大小仍然可见，代理在网络层也会收到
+客户端 IP。应用仅记录计数，并保存用于限流的 IP 哈希。推送不会上传文件或
+完整会话记录；设备保持已认证的实时连接时，不会向该设备发送推送。
+
+取消推送注册或撤销设备会先删除本地推送注册，再尽力请求代理删除相应映射。
+代理不可达时，无法确认远端删除成功；仅卸载软件包不会删除远端映射。
+APNs 已经接收的通知无法撤回。终端输出仍仅供查看；桥接插件不提供可交互的
+远程终端。
+
+## 卸载
+
+1. 在 **Settings → DSHM** 中撤销不再需要授权的设备。
+2. 打开 **Plugins**，找到 `dsh-plugin-dshm`，通过 DSH 插件管理器从当前
+   profile 中移除。如果其他 profile 也安装过，包括可选的 `dshm` CLI
+   profile，请分别移除。
+3. 按提示重启受影响的 DSH 宿主。该宿主的 DSHM 设置卡片和监听端口应已消失。
+
+卸载软件包与删除私有身份、配对记录是两件事。如果打算重新安装，请保留
+`$DSH_HOME/dshm/`。如果你明确选择完整重置，应先停止所有使用该 home 的 DSH
+宿主，然后仅删除桥接插件的 `dshm` 状态目录；已有设备需要忘记旧电脑并重新
+配对。不要删除整个 DSH home，也不要删除模型服务凭据或会话目录。卸载桥接
+插件不会删除 DSH 会话。
+
+## 新 DSH 版本发布检查清单（维护者）
+
+1. 测试期间保持当前已验证的 `engines.dsh` 值不变，先阅读上游改动，尤其是
+   projection 接口和插件加载器的变化。
+2. 通过 DSH 的正常发布渠道安装候选运行时，在隔离的 `.dsh-test` home 中对
+   **该候选版本**运行 `pnpm -C bridge test:integration`。兼容性改动必须同时
+   审查 `bridge/src/projection/native.ts` 中的显式运行时版本保护；只改包元数据
+   不会启用新运行时。必要时调整测试宿主路径，但不要跳过失败，也不要用旧
+   运行时的结果冒充新版本验证。
+   记录实际版本和结果；声明新的 Windows 组合已支持前，完成 Windows 清单。
+3. 运行 `pnpm -C bridge test`、`pnpm -C protocol validate` 和
+   `pnpm -C protocol gen:check`。在正确的架构边界内修复兼容性问题并审查结果。
+4. **只有真实 DSH 集成测试通过后**，才把 `engines.dsh` 扩大到明确验证过的
+   版本或范围。不要假定未来整个小版本都兼容。根据实际验证记录，更新
+   `tools/release-plugin/check-release.mjs` 中的已测试范围，并与运行时版本保护
+   保持一致。从 `bridge/package.json`
+   重新生成并验证插件索引，保证两处兼容性字段一致。
+5. 提升插件版本，更新中英文 README，检查 `npm pack --dry-run`，并通过隔离
+   profile 的插件管理器安装和启动准备发布的同一个 tarball。
+6. 发布前审计准备发布的同一个 tarball，记录 SHA-256。所有者亲自登录 npm，
+   禁用生命周期脚本后发布该文件。通过隔离 profile 的 DSH 插件管理器验证按名
+   安装。已经发布的版本不能通过覆盖来修复。
+
+公开仓库仅保存插件源码快照。共用协议源码、fixtures 及集成工具保留在私有
+开发仓库中；上述 monorepo 构建和测试命令需要维护者的开发检出。npm 包已包含
+协议运行时和依赖许可证，用户不需要这些开发源码。公开仓库不包含私有仓库
+历史、iOS 应用或推送代理源码。
+
+采用 [MIT 许可证](LICENSE)。版本改动见 [CHANGELOG](CHANGELOG.md)。
+
+[项目源码](https://github.com/JeremyCruzFang/dsh-plugin-dshm) ·
+[问题反馈](https://github.com/JeremyCruzFang/dsh-plugin-dshm/issues)

package/cordis.patch.yml

@@ -0,0 +1,7 @@
+- insert:
+    - id: dshm-bridge
+      name: dsh-plugin-dshm
+      disabled: !!js "ctx.get('profileContext')?.name === 'dshm'"
+    - id: dshm-cli
+      name: dsh-plugin-dshm/cli
+      disabled: !!js "ctx.get('profileContext')?.name !== 'dshm'"

package/lib/auth/signature.d.ts

@@ -0,0 +1,4 @@
+import crypto from 'node:crypto';
+export declare const authMessage: (nonce: string, hostId: string, fingerprint: string) => Buffer;
+export declare function publicKeyFromSpki(value: string): crypto.KeyObject;
+export declare function verifySignature(publicKey: string, nonce: string, hostId: string, fingerprint: string, signature: string): boolean;

package/lib/auth/signature.js

@@ -0,0 +1,24 @@
+import crypto from 'node:crypto';
+export const authMessage = (nonce, hostId, fingerprint) => Buffer.concat([
+    Buffer.from('dshm-auth-v1'), Buffer.from(nonce, 'base64url'), Buffer.from(hostId), Buffer.from(fingerprint),
+]);
+export function publicKeyFromSpki(value) {
+    const bytes = Buffer.from(value, 'base64');
+    if (bytes.toString('base64') !== value || bytes.length > 256)
+        throw new Error('Invalid public key encoding');
+    const key = crypto.createPublicKey({ key: bytes, type: 'spki', format: 'der' });
+    if (key.asymmetricKeyType !== 'ec' || key.asymmetricKeyDetails?.namedCurve !== 'prime256v1')
+        throw new Error('P-256 key required');
+    return key;
+}
+export function verifySignature(publicKey, nonce, hostId, fingerprint, signature) {
+    try {
+        const bytes = Buffer.from(signature, 'base64');
+        if (bytes.toString('base64') !== signature || bytes.length > 80)
+            return false;
+        return crypto.verify('sha256', authMessage(nonce, hostId, fingerprint), { key: publicKeyFromSpki(publicKey), dsaEncoding: 'der' }, bytes);
+    }
+    catch {
+        return false;
+    }
+}

package/lib/cli/index.d.ts

@@ -0,0 +1,4 @@
+export declare const name = "dshm-cli";
+export declare const inject: string[];
+export declare function run(args: readonly string[]): Promise<number>;
+export declare function apply(context: unknown): void;

package/lib/cli/index.js

@@ -0,0 +1,41 @@
+import QRCode from 'qrcode';
+import { parseConfig } from '../config.js';
+import { localRequest } from '../host/local.js';
+import { installCli, cliInject } from '../projection/host.js';
+export const name = 'dshm-cli';
+export const inject = cliInject;
+export async function run(args) {
+    const directory = parseConfig(undefined).stateDir;
+    const [command, id, ...extra] = args;
+    if (extra.length || !['pair', 'devices', 'revoke', 'status'].includes(command ?? '') || (command === 'revoke' ? !id : id !== undefined)) {
+        console.error('Usage: dsh dshm pair | devices | revoke <id> | status');
+        return 2;
+    }
+    try {
+        if (command === 'pair') {
+            const value = await localRequest(directory, 'POST', '/pair', {});
+            console.log(await QRCode.toString(value.url, { type: 'terminal', small: true }));
+            console.log(`Pairing expires at ${value.expiresAt}. One use. Keep this QR private.`);
+        }
+        else if (command === 'devices') {
+            const { devices } = await localRequest(directory, 'GET', '/devices');
+            console.log(JSON.stringify(devices, null, 2));
+        }
+        else if (command === 'revoke') {
+            const result = await localRequest(directory, 'POST', '/revoke', { deviceId: id });
+            if (!result.revoked) {
+                console.error('Device not found');
+                return 1;
+            }
+            console.log('Device revoked');
+        }
+        else
+            console.log(JSON.stringify(await localRequest(directory, 'GET', '/status'), null, 2));
+        return 0;
+    }
+    catch {
+        console.error('DSHM bridge is unavailable in this DSH_HOME. Start the host profile first.');
+        return 1;
+    }
+}
+export function apply(context) { installCli(context, run); }