dsh-local-link 1.2.0 → 1.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +12 -0
- package/README.md +2 -16
- package/README.zh.md +1 -15
- package/docs/ARCHITECTURE.md +1 -1
- package/docs/DIAGNOSTICS.md +1 -1
- package/package.json +4 -3
- package/docs/COMPATIBILITY.md +0 -75
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,18 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project are documented here.
|
|
4
4
|
|
|
5
|
+
## 1.2.1 — 2026-09-21
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
|
|
9
|
+
- Declared the supported DeepSeek Harness range through the official `engines.dsh` package metadata and added manifest format version `1`, allowing plugin clients to evaluate Host compatibility directly.
|
|
10
|
+
- Removed the duplicated compatibility matrices and standalone compatibility document; the package manifest is now the single source of truth, while historical validation remains recorded in this changelog.
|
|
11
|
+
- Updated the release contract to keep `engines.dsh` aligned with the Harness Host peer dependency.
|
|
12
|
+
|
|
13
|
+
### Validated
|
|
14
|
+
|
|
15
|
+
- Passed TypeScript checking, all 102 automated tests across 16 files, the production build, and package dry-run.
|
|
16
|
+
|
|
5
17
|
## 1.2.0 — 2026-09-18
|
|
6
18
|
|
|
7
19
|
`1.2.0` moves the development baseline to DeepSeek Harness `0.1.5-rc.2` and
|
package/README.md
CHANGED
|
@@ -56,7 +56,7 @@ dsh web
|
|
|
56
56
|
|
|
57
57
|
### Git clone — development checkout
|
|
58
58
|
|
|
59
|
-
Requirements: Git, Node.js 22.19+ or 24+, Corepack, and a global `dsh` installation
|
|
59
|
+
Requirements: Git, Node.js 22.19+ or 24+, Corepack, and a global `dsh` installation compatible with the package's declared `engines.dsh` range.
|
|
60
60
|
|
|
61
61
|
```shell
|
|
62
62
|
git clone https://github.com/donoteatme/dsh-local-link.git
|
|
@@ -71,20 +71,7 @@ The profile points at the checkout, so rebuild after changing client code and re
|
|
|
71
71
|
|
|
72
72
|
## Compatibility
|
|
73
73
|
|
|
74
|
-
Compatibility is checked against exact
|
|
75
|
-
|
|
76
|
-
| DeepSeek Harness | Local Link status |
|
|
77
|
-
| --- | --- |
|
|
78
|
-
| `0.1.5-rc.2` | **Supported release** |
|
|
79
|
-
| `0.1.5-rc.1` | **Verified** |
|
|
80
|
-
| `0.1.2-rc.1` | **Verified** |
|
|
81
|
-
| `0.1.1-rc.2` | **Verified** |
|
|
82
|
-
| `0.1.1-rc.1` | **Verified** |
|
|
83
|
-
| `0.1.0-rc.8` | **Verified** |
|
|
84
|
-
|
|
85
|
-
All six rows passed the installed-runtime gateway and revoke gate with packed `1.1.1` source. For `1.2.0`, the current `0.1.5-rc.2` release was additionally rebuilt against the exact package contracts and exercised in the real browser client at `430 × 932` and `320 × 568`. Historical RC evidence remains recorded separately and the moving `next` tag itself is never a compatibility promise.
|
|
86
|
-
|
|
87
|
-
Only the exact versions listed above carry a compatibility claim. Alpha builds—including the removed `0.1.2-alpha.1` row—versions older than `0.1.0-rc.8`, and whatever package a moving `next` tag points to later are unsupported until checked independently. See [Compatibility](docs/COMPATIBILITY.md) for the evidence and remaining real-device boundary.
|
|
74
|
+
The installable DeepSeek Harness range is declared in `package.json` through `engines.dsh`. Compatibility is checked against exact releases—not inferred from a successful installation or a moving dist-tag.
|
|
88
75
|
|
|
89
76
|
## Use
|
|
90
77
|
|
|
@@ -249,7 +236,6 @@ npm run verify
|
|
|
249
236
|
Project documentation:
|
|
250
237
|
|
|
251
238
|
- [Architecture and compatibility boundaries](docs/ARCHITECTURE.md)
|
|
252
|
-
- [Verified DeepSeek Harness compatibility](docs/COMPATIBILITY.md)
|
|
253
239
|
- [Mobile View behavior and release matrix](docs/MOBILE_VIEW.md)
|
|
254
240
|
- [Local diagnostics and event codes](docs/DIAGNOSTICS.md)
|
|
255
241
|
- [Security model](docs/SECURITY.md)
|
package/README.zh.md
CHANGED
|
@@ -69,20 +69,7 @@ profile 会指向当前 checkout。修改客户端代码后需要重新构建;
|
|
|
69
69
|
|
|
70
70
|
## 兼容性
|
|
71
71
|
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
| DeepSeek Harness | Local Link 状态 |
|
|
75
|
-
| --- | --- |
|
|
76
|
-
| `0.1.5-rc.2` | **支持的发布版本** |
|
|
77
|
-
| `0.1.5-rc.1` | **已验证** |
|
|
78
|
-
| `0.1.2-rc.1` | **已验证** |
|
|
79
|
-
| `0.1.1-rc.2` | **已验证** |
|
|
80
|
-
| `0.1.1-rc.1` | **已验证** |
|
|
81
|
-
| `0.1.0-rc.8` | **已验证** |
|
|
82
|
-
|
|
83
|
-
以上六个版本都使用打包后的 `1.1.1` 源码通过了已安装运行时的网关和撤销测试。对于 `1.2.0`,当前发布版本 `0.1.5-rc.2` 还使用精确依赖重新构建,并在真实浏览器客户端中完成了 `430 × 932` 与 `320 × 568` 检查。历史 RC 的验证证据继续保留;移动的 `next` 标签本身不代表兼容性承诺。
|
|
84
|
-
|
|
85
|
-
只有表格中的精确版本包含兼容性承诺。已移除的 alpha 版本、早于 `0.1.0-rc.8` 的版本,以及未来移动的 `next` 标签都必须单独验证。完整证据与边界见[兼容性说明](docs/COMPATIBILITY.md)。
|
|
72
|
+
可安装的 DeepSeek Harness 版本范围通过 `package.json` 中的 `engines.dsh` 声明。兼容性按精确发布版本验证,不会因为安装成功或可变的 dist-tag 就推断为兼容。
|
|
86
73
|
|
|
87
74
|
## 使用方法
|
|
88
75
|
|
|
@@ -198,7 +185,6 @@ npm run verify
|
|
|
198
185
|
项目文档:
|
|
199
186
|
|
|
200
187
|
- [架构与兼容性边界](docs/ARCHITECTURE.md)
|
|
201
|
-
- [已验证的 Harness 兼容性](docs/COMPATIBILITY.md)
|
|
202
188
|
- [移动视图行为与发布矩阵](docs/MOBILE_VIEW.md)
|
|
203
189
|
- [本地诊断与事件代码](docs/DIAGNOSTICS.md)
|
|
204
190
|
- [安全模型](docs/SECURITY.md)
|
package/docs/ARCHITECTURE.md
CHANGED
|
@@ -175,7 +175,7 @@ No service discovery, certificate generator, tunnel client, native application,
|
|
|
175
175
|
|
|
176
176
|
## Compatibility strategy
|
|
177
177
|
|
|
178
|
-
The plugin develops against the exact DeepSeek Harness `0.1.5-rc.2` contracts
|
|
178
|
+
The plugin develops against the exact DeepSeek Harness `0.1.5-rc.2` contracts. The installable Host range is declared by `engines.dsh`; most integration uses declared package contracts, but several adapters are intentionally version-sensitive:
|
|
179
179
|
|
|
180
180
|
| Adapter | Why it exists | Failure behavior | Removal condition |
|
|
181
181
|
| --- | --- | --- | --- |
|
package/docs/DIAGNOSTICS.md
CHANGED
|
@@ -83,7 +83,7 @@ The copied report wraps the retained events with a schema version and export tim
|
|
|
83
83
|
| `AUTH_REQUIRED` | An unpaired browser opened a protected gateway page. | Pair that browser with a fresh QR/link; direct `:3088` access is intentionally rejected. |
|
|
84
84
|
| `HTTP_UPSTREAM_ERROR` | The gateway could not reach Harness on `127.0.0.1:3080`. | Confirm `dsh web` is running and `upstreamOrigin` matches its port. |
|
|
85
85
|
| `BROWSER_AUTH_HANDOFF_FAILED` | Harness returned an invalid browser-authentication handoff target. | Confirm the installed Harness version is supported and restart `dsh web`. |
|
|
86
|
-
| `INDEX_REWRITE_ERROR` | The returned Harness index did not match the supported boot contract. | Confirm the installed Harness version
|
|
86
|
+
| `INDEX_REWRITE_ERROR` | The returned Harness index did not match the supported boot contract. | Confirm the installed Harness version satisfies `engines.dsh` and restart `dsh web`. |
|
|
87
87
|
| `WS_REJECTED` | A WebSocket upgrade failed trust, authorization, or path validation. | Re-pair the browser and verify no proxy rewrites the URL. |
|
|
88
88
|
| `WS_UPSTREAM_ERROR` | The gateway could not open the loopback Harness event socket. | Confirm the desktop Harness process is still running and reload the paired browser. |
|
|
89
89
|
| `CLIPBOARD_COPY_FAILED` | The browser refused or failed to copy the one-time link. | Grant clipboard permission or select and copy the displayed link manually. |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-local-link",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.1",
|
|
4
4
|
"description": "DeepSeek Harness plugin for lightweight LAN access to the current Web UI from phones, tablets, and other computers.",
|
|
5
5
|
"publishConfig": {
|
|
6
6
|
"access": "public"
|
|
@@ -27,7 +27,6 @@
|
|
|
27
27
|
"docs/images/*.jpg",
|
|
28
28
|
"docs/images/*.png",
|
|
29
29
|
"docs/ARCHITECTURE.md",
|
|
30
|
-
"docs/COMPATIBILITY.md",
|
|
31
30
|
"docs/DIAGNOSTICS.md",
|
|
32
31
|
"docs/MOBILE_VIEW.md",
|
|
33
32
|
"docs/SECURITY.md",
|
|
@@ -38,6 +37,7 @@
|
|
|
38
37
|
"LICENSE"
|
|
39
38
|
],
|
|
40
39
|
"dsh": {
|
|
40
|
+
"manifestVersion": 1,
|
|
41
41
|
"bundle": {
|
|
42
42
|
"patch": "./cordis.patch.yml"
|
|
43
43
|
},
|
|
@@ -64,7 +64,8 @@
|
|
|
64
64
|
"verify": "npm run typecheck && npm run test && npm pack --dry-run"
|
|
65
65
|
},
|
|
66
66
|
"engines": {
|
|
67
|
-
"node": "^22.19.0 || >=24.0.0"
|
|
67
|
+
"node": "^22.19.0 || >=24.0.0",
|
|
68
|
+
"dsh": "0.1.0-rc.8 || 0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2"
|
|
68
69
|
},
|
|
69
70
|
"keywords": [
|
|
70
71
|
"deepseek",
|
package/docs/COMPATIBILITY.md
DELETED
|
@@ -1,75 +0,0 @@
|
|
|
1
|
-
# DeepSeek Harness compatibility
|
|
2
|
-
|
|
3
|
-
Local Link touches version-sensitive Harness Host, slot, theme, layout, session,
|
|
4
|
-
and Settings contracts. Each supported version is therefore checked directly.
|
|
5
|
-
|
|
6
|
-
## Compatibility matrix
|
|
7
|
-
|
|
8
|
-
Last checked on 2026-09-18 with Node.js 22 and Windows. The current release row
|
|
9
|
-
uses the `dsh-local-link@1.2.0` candidate; historical rows retain their packed
|
|
10
|
-
`1.1.1` installed-runtime evidence. Versions are newest first.
|
|
11
|
-
|
|
12
|
-
| DeepSeek Harness | Status | Local Link source | Last checked |
|
|
13
|
-
| --- | --- | --- | --- |
|
|
14
|
-
| `0.1.5-rc.2` | **Supported release** | `1.2.0` | 2026-09-18 |
|
|
15
|
-
| `0.1.5-rc.1` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
16
|
-
| `0.1.2-rc.1` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
17
|
-
| `0.1.1-rc.2` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
18
|
-
| `0.1.1-rc.1` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
19
|
-
| `0.1.0-rc.8` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
20
|
-
|
|
21
|
-
Only the exact versions in the matrix are supported or verified. Alpha builds,
|
|
22
|
-
including the previously tested `0.1.2-alpha.1`, versions older than
|
|
23
|
-
`0.1.0-rc.8`, and future versions reached through a moving dist-tag are
|
|
24
|
-
unsupported until they pass a new check.
|
|
25
|
-
|
|
26
|
-
### Status meanings
|
|
27
|
-
|
|
28
|
-
- **Supported release** is the current development target and receives the
|
|
29
|
-
complete repository and installed-runtime gate.
|
|
30
|
-
- **Verified** means the recorded packed Local Link artifact passed the
|
|
31
|
-
historical RC gate on that exact version.
|
|
32
|
-
- **Untested** means no compatibility claim is made.
|
|
33
|
-
|
|
34
|
-
Every newer Harness version still requires an independent check; support for
|
|
35
|
-
`0.1.5-rc.2` does not imply support for a moving `next` tag or later alpha.
|
|
36
|
-
|
|
37
|
-
## Verification policy
|
|
38
|
-
|
|
39
|
-
The historical RC gate starts from a fresh isolated installation. The packed
|
|
40
|
-
release must compose into the Web profile, boot in the real client, render Local
|
|
41
|
-
Access, preserve the private-LAN and loopback-admin boundaries, complete one-use
|
|
42
|
-
pairing, proxy authenticated HTTP and a supported WebSocket, close that socket
|
|
43
|
-
on revoke, reject the revoked device, and activate the responsive shell at
|
|
44
|
-
`390 × 844`. Automated tests cover Current session, subagent, locale, slot, and
|
|
45
|
-
composition contracts.
|
|
46
|
-
|
|
47
|
-
All six exact Harness versions installed the packed `1.1.1` artifact without a
|
|
48
|
-
peer conflict and passed an isolated installed-runtime gate: profile composition
|
|
49
|
-
and boot, Local Link pairing, the version-appropriate browser-authentication
|
|
50
|
-
handoff, authenticated root access, an authenticated supported WebSocket,
|
|
51
|
-
immediate socket closure on revoke, and a `401` response when the revoked device
|
|
52
|
-
retried. `0.1.0-rc.8`, `0.1.1-rc.1`, and `0.1.1-rc.2` used `/api/events.mux`;
|
|
53
|
-
`0.1.2-rc.1` and the `0.1.5` builds used the current `/api/remote.mux` path.
|
|
54
|
-
|
|
55
|
-
The `0.1.5` rows compose and boot with the new `main`/`rightbar` AppFrame while
|
|
56
|
-
retaining the session header, composer, sidebar, Settings, and overlay slots
|
|
57
|
-
used by Local Link. Both exact RCs additionally passed typecheck, all 98
|
|
58
|
-
automated tests, production build/package verification, desktop Local Access
|
|
59
|
-
rendering, and the responsive shell at `390 × 844` without client exceptions.
|
|
60
|
-
The historical versions retain their earlier real-client responsive evidence;
|
|
61
|
-
the `1.1.1` patch changes package compatibility contracts and documentation, not
|
|
62
|
-
the shipped client or gateway implementation. The `1.2.0` candidate was then
|
|
63
|
-
rebuilt against the exact `0.1.5-rc.2` contracts and booted in an isolated Web
|
|
64
|
-
profile with synthetic parent and subagent sessions. Its real browser client
|
|
65
|
-
passed Navigation, Current session, Subagents, and Conversation checks at
|
|
66
|
-
`430 × 932`, plus the non-shrinking information action and one-row composer at
|
|
67
|
-
`320 × 568`.
|
|
68
|
-
|
|
69
|
-
Historical RC runs used empty profiles, so they did not create provider-backed
|
|
70
|
-
conversations. Physical-phone portrait and landscape acceptance also remains a
|
|
71
|
-
separate release check.
|
|
72
|
-
|
|
73
|
-
A successful package installation alone is not compatibility proof. Harness
|
|
74
|
-
may change authentication, DOM semantics, client slots, exported primitives,
|
|
75
|
-
theme storage, or responsive geometry while the plugin still appears to boot.
|