dsh-deeppilot 0.6.0-alpha.2 → 0.6.0-alpha.3

package/COMPATIBILITY.md

@@ -7,7 +7,7 @@ This file separates tested evidence from intended behavior. Passing unit tests d
 | Component | Baseline | Evidence |
 |---|---|---|
 | Node.js | 22 or newer | package engine and CI |
-| DSH CLI and Host API | `0.1.2-alpha.2` minimum | published alpha.2 type/build checks, profile install and Host-start smoke test, plus 0.1.2 history and `/phone` protocol tests |
+| DSH CLI and Host API | `0.1.2-alpha.3` minimum; `0.1.2-alpha.4` verified | clean alpha.3 install and Host-start smoke; isolated alpha.4 type/build plus 167 unit tests; alpha.4 Host-start smoke; `/phone` protocol tests |
 | Host OS | macOS on Apple silicon | embedded helper artifact and local integration testing |
 | Remote access | Tailscale Funnel, ports 443/8443/10000 | helper and supervisor tests |
 | iOS | native DeepPilot client, protocol v2 | simulator build and v2 pairing/challenge evidence |
@@ -18,12 +18,16 @@ This file separates tested evidence from intended behavior. Passing unit tests d
 - Bearer authentication, URL credentials, and first-frame shared tokens are rejected. A supported client registers a P-256 public key through `/phone/pair` and signs each WebSocket challenge.
 - Without a compatible embedded helper, the core bridge and trusted-LAN mode can still run; remote Funnel reports `unavailable`.
 - If a DSH Host API is missing, only the dependent capability should be disabled. The plugin must not crash the Host.
-- DSH versions older than `0.1.2-alpha.2` are unsupported: they do not expose
-  the controller and client package family required by this plugin.
-- On the tested `0.1.2-alpha.2` Host, the compatibility facade converts the
+- DSH versions older than `0.1.2-alpha.3` are unsupported: they do not expose
+  the Gateway multi-client Remote Events routing required by this plugin.
+- DSH `0.1.2-alpha.4` keeps the Gateway Remote Events contract used for
+  approvals and questions. Its event-sequence/log-offset refactor changes
+  session internals, but the plugin's stable history facade passes the alpha.4
+  type/build and unit-test baseline.
+- On the alpha.3 package baseline, the compatibility facade converts the
   current Session controller's raw event arrays into the stable wrapped
   history entries consumed by the phone bridge. Sessions persisted by earlier
-  Hosts can therefore be listed and opened when the alpha.2 Host's own
+  Hosts can therefore be listed and opened when the alpha.3 Host's own
   persistence reader accepts their log vocabulary. Unsupported persisted
   formats still fail closed in the Host without modifying the original log.
 
@@ -32,7 +36,7 @@ This file separates tested evidence from intended behavior. Passing unit tests d
 - Intel macOS support for the embedded helper;
 - signed/notarized helper distribution;
 - Windows or Linux host validation;
-- repair or migration of persisted history rejected by the `0.1.2-alpha.2`
+- repair or migration of persisted history rejected by the `0.1.2-alpha.3`
   Host's own session reader;
 - every DSH developer-preview revision;
 - physical-device performance and every carrier/network combination;

package/README.md

@@ -37,18 +37,23 @@ require it.
 
 | Plugin version | Required DSH | How to install |
 |---|---|---|
-| `0.6.0-alpha.x` (new, `alpha` tag) | DSH `0.1.2-alpha.2` or newer | `dsh plugin --profile web add dsh-deeppilot@alpha` |
+| `0.6.0-alpha.x` (new, `alpha` tag) | DSH `0.1.2-alpha.3` or newer | `dsh plugin --profile web add dsh-deeppilot@alpha` |
 | `0.5.x` (previous stable, `latest`) | DSH `0.1.1-rc.2`–`0.1.2-alpha.1` | `dsh plugin --profile web add dsh-deeppilot` |
 
 The `0.6.0` alpha line is built against the DSH
-[0.1.2-alpha.2](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.2-alpha.2)
-controller and client package family, so it requires DSH `0.1.2-alpha.2` or
-newer (its `alpha` npm dist-tag). Earlier DSH builds do not provide the Host
-APIs required by this plugin. Users who need a DSH release before that must
-stay on the `0.5.x` plugin.
+[0.1.2-alpha.3](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.2-alpha.3)
+Host and client package family, so it requires DSH `0.1.2-alpha.3` or newer
+(its `alpha` npm dist-tag). The alpha.3 Gateway provides the multi-client
+Remote Events routing used to keep Web and DeepPilot independently answerable.
+Earlier DSH builds do not provide that routing contract. Users who need a DSH
+release before that must stay on the `0.5.x` plugin.
+
+DSH `0.1.2-alpha.4` is also verified. It retains the same interaction-routing
+contract; see [COMPATIBILITY.md](./COMPATIBILITY.md) for the tested evidence and
+its session-history compatibility note.
 
 ```sh
-# DSH 0.1.2-alpha.2 or newer (recommended):
+# DSH 0.1.2-alpha.3 or newer (recommended):
 dsh plugin --profile web add dsh-deeppilot@alpha
 # DSH 0.1.1-rc.2 through 0.1.2-alpha.1 (previous stable):
 dsh plugin --profile web add dsh-deeppilot
@@ -73,13 +78,13 @@ DeepPilot state under `$DSH_HOME/deeppilot/`.
 
 ## Publishing (maintainers)
 
-`0.6.0-alpha.x` targets DSH `0.1.2-alpha.2`+; `0.5.x` stays compatible with
+`0.6.0-alpha.x` targets DSH `0.1.2-alpha.3`+; `0.5.x` stays compatible with
 DSH `0.1.1-rc.2`–`0.1.2-alpha.1`. Keep both published:
 
 1. Bump `version` in `package.json` and in the root `""` entry of
    `package-lock.json`, then run `npm test && npm run typecheck && npm run build`
    and inspect `npm pack --dry-run --json` (the check
-   `tests/compatibility-metadata.test.ts` enforces the `^0.1.2-alpha.2` peer
+   `tests/compatibility-metadata.test.ts` enforces the `^0.1.2-alpha.3` peer
    ranges).
 2. Commit the release and push it. `npm publish` runs `prepack` (build) and
    `prepublishOnly` (test + typecheck) automatically.
@@ -91,7 +96,7 @@ DSH `0.1.1-rc.2`–`0.1.2-alpha.1`. Keep both published:
 
    After a successful publish, `npm view dsh-deeppilot dist-tags --json` shows
    `"latest": "0.5.x"` and `"alpha": "0.6.0-alpha.x"`. Verify the published
-   package by installing it into a DSH `0.1.2-alpha.2` profile before pointing
+   package by installing it into a DSH `0.1.2-alpha.3` profile before pointing
    users at it.
 4. Tag the release commit `v0.6.0-alpha.x` and prepare a GitHub Release
    (English + 简体中文 notes) that links this README section.

package/README.zh-CN.md

@@ -34,17 +34,21 @@
 
 | 插件版本 | 所需 DSH | 安装命令 |
 |---|---|---|
-| `0.6.0-alpha.x`（新版，`alpha` tag） | DSH `0.1.2-alpha.2` 或更高 | `dsh plugin --profile web add dsh-deeppilot@alpha` |
+| `0.6.0-alpha.x`（新版，`alpha` tag） | DSH `0.1.2-alpha.3` 或更高 | `dsh plugin --profile web add dsh-deeppilot@alpha` |
 | `0.5.x`（旧版稳定版，`latest`） | DSH `0.1.1-rc.2`–`0.1.2-alpha.1` | `dsh plugin --profile web add dsh-deeppilot` |
 
 `0.6.0` alpha 系列基于 DSH
-[0.1.2-alpha.2](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.2-alpha.2)
-的 controller 与 client 包族构建，因此要求 DSH `0.1.2-alpha.2` 或更高版本
-（对应 npm `alpha` dist-tag）。更早的 DSH 版本不提供本插件依赖的 Host API；
+[0.1.2-alpha.3](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.2-alpha.3)
+的 Host 与 client 包族构建，因此要求 DSH `0.1.2-alpha.3` 或更高版本（对应
+npm `alpha` dist-tag）。alpha.3 Gateway 提供多 Client Remote Events 路由，
+使 Web 与 DeepPilot 能独立接收并处理同一交互。更早版本没有这项路由契约；
 需要更早 DSH 版本的用户请继续使用 `0.5.x` 插件。
 
+DSH `0.1.2-alpha.4` 也已验证，交互路由契约保持不变；测试证据和会话历史兼容性
+说明见 [COMPATIBILITY.md](./COMPATIBILITY.md)。
+
 ```sh
-# DSH 0.1.2-alpha.2 或更高（推荐）：
+# DSH 0.1.2-alpha.3 或更高（推荐）：
 dsh plugin --profile web add dsh-deeppilot@alpha
 # DSH 0.1.1-rc.2 至 0.1.2-alpha.1（旧版稳定）：
 dsh plugin --profile web add dsh-deeppilot
@@ -67,13 +71,13 @@ dsh plugin --profile web remove dsh-deeppilot
 
 ## 发布说明（维护者）
 
-`0.6.0-alpha.x` 面向 DSH `0.1.2-alpha.2`+；`0.5.x` 保持兼容 DSH
+`0.6.0-alpha.x` 面向 DSH `0.1.2-alpha.3`+；`0.5.x` 保持兼容 DSH
 `0.1.1-rc.2`–`0.1.2-alpha.1`，两个版本线都要保持发布：
 
 1. 同步修改 `package.json` 与 `package-lock.json` 根 `""` 条目中的
    `version`，然后运行 `npm test && npm run typecheck && npm run build`，
    并检查 `npm pack --dry-run --json`（`tests/compatibility-metadata.test.ts`
-   会强制校验 `^0.1.2-alpha.2` 的 peer 范围）。
+   会强制校验 `^0.1.2-alpha.3` 的 peer 范围）。
 2. 提交发布并推送。`npm publish` 会自动执行 `prepack`（构建）与
    `prepublishOnly`（测试 + 类型检查）。
 3. 发布 alpha 版本线，不要动 `latest`：
@@ -84,7 +88,7 @@ dsh plugin --profile web remove dsh-deeppilot
 
    发布成功后，`npm view dsh-deeppilot dist-tags --json` 应显示
    `"latest": "0.5.x"` 与 `"alpha": "0.6.0-alpha.x"`。向用户推荐前，请先在
-   DSH `0.1.2-alpha.2` profile 中安装验证发布的包。
+   DSH `0.1.2-alpha.3` profile 中安装验证发布的包。
 4. 为发布提交打 `v0.6.0-alpha.x` tag，并准备包含英文与简体中文说明的
    GitHub Release，链接本 README 的发布说明。
 5. alpha 转正时升级到 `0.6.0`，用 `npm publish --tag latest` 发布，使

package/bin/SHA256SUMS

@@ -1,6 +1,6 @@
-1f7f29e139f978a68da0bc80c5755e37aca311de06e5e2a14fb09ccb34647571  ./darwin-amd64/dsh-deeppilot-tunnel
-a7c879a104468c6ab7c782176f4ca4f1c87fbbffef298dc3a1009fa8960a801f  ./darwin-arm64/dsh-deeppilot-tunnel
-210a182ca76f09a244d8439f071b68c606157e5bdd18f383c16b2454b72d117c  ./linux-amd64/dsh-deeppilot-tunnel
-fb7d93a5edb2eeff8b867aa5c745618ef44f425bb7c4cd6aa6289116efef9fb2  ./linux-arm64/dsh-deeppilot-tunnel
-c1a23b917d4fcde70b449574b00cd4e453cd7e13d4777a7f7affaad9e0efbbac  ./windows-amd64/dsh-deeppilot-tunnel.exe
-eff7c91008f5846ccebdd8c7eb51f65ef96455c46f489de7c4d3d6b888a4f3f5  ./windows-arm64/dsh-deeppilot-tunnel.exe
+fd5187c9a2fd49de79cfa63287ef18aa46a2b6a051be9201164fd1b3e82a7994  ./darwin-amd64/dsh-deeppilot-tunnel
+c4a879e8f366421c817d3d87836db9352d6d5d2b8cf0c818ccdb228e3329a7ab  ./darwin-arm64/dsh-deeppilot-tunnel
+a937fa8ff3c9a8f6052bb0241f98dcaf0d7ea1d1694a8a5593320764c61e4b24  ./linux-amd64/dsh-deeppilot-tunnel
+6ccf147ab7886796d5932e761b573f93f44bd5644a553cb0f2f4b24749692eac  ./linux-arm64/dsh-deeppilot-tunnel
+9c574dfe6a988130b5d6d69670e6f806c378b603af6814ce0c4f152fafa94b2a  ./windows-amd64/dsh-deeppilot-tunnel.exe
+13f09ac30f71473578ab04c5ab23fc57e5bd0e69d36b782e6261acadf464940c  ./windows-arm64/dsh-deeppilot-tunnel.exe

package/lib/client.js

@@ -822,7 +822,10 @@ window.__ModuleLoader__.load({
 			".pbb-action{font:inherit;font-size:12px;color:var(--dsw-alias-label-secondary);cursor:pointer;background:none;border:1px solid var(--dsw-alias-border-l2);border-radius:7px;padding:3px 8px}",
 			".pbb-action:hover:not(:disabled){color:var(--dsw-alias-label-primary);background:var(--dsw-alias-bg-module-platform)}",
 			".pbb-action:disabled{cursor:default;opacity:.5}",
-			".pbb-actionDanger:not(:disabled){color:#fff;background:var(--dsw-alias-label-error);border-color:var(--dsw-alias-label-error)}",
+			".pbb-actionDanger{color:#fff;background:#dc2626;border-color:#dc2626;line-height:1.35;padding:4px 10px;box-shadow:0 1px 2px rgba(127,29,29,.18);transition:background-color .15s ease,border-color .15s ease,box-shadow .15s ease,transform .1s ease}",
+			".pbb-actionDanger:hover:not(:disabled){color:#fff;background:#b91c1c;border-color:#b91c1c;box-shadow:0 2px 5px rgba(127,29,29,.24)}",
+			".pbb-actionDanger:active:not(:disabled){background:#991b1b;border-color:#991b1b;box-shadow:0 1px 2px rgba(127,29,29,.2);transform:translateY(1px)}",
+			".pbb-actionDanger:focus-visible{outline:2px solid rgba(220,38,38,.32);outline-offset:2px}",
 			".pbb-qrPanel{display:flex;flex-direction:column;align-items:center;gap:9px;padding:12px 0 4px}",
 			".pbb-qrImage{width:240px;height:240px;max-width:100%;background:#fff;border-radius:10px;padding:8px;box-sizing:border-box}",
 			".pbb-pairCodeBlock{width:min(100%,420px);display:flex;flex-direction:column;gap:5px}",