dsh-cindy-host 0.1.41 → 0.1.43
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 +10 -0
- package/README.md +5 -3
- package/package.json +4 -4
- package/src/host-version.js +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.43 — 2026-11-14
|
|
4
|
+
|
|
5
|
+
- Accept the exact DSH `0.2.2-rc.3` Agent/Session/Settings carrier alongside all previously supported versions, without bundling DSH core packages or accepting future prereleases.
|
|
6
|
+
- Preserve runtime behavior and Cindy handshake identity; update release identity, lockfile and compatibility regression coverage. The packed candidate passed 1,239 tests on an isolated real rc3 SDK (4 skipped), core contracts 7/7, clean native installation and Web runtime smoke 30/30; channel audit has 0 unclassified channels. Live handset, relay, OAuth and model calls remain separate acceptance requirements; publication does not reload an installed Host.
|
|
7
|
+
|
|
8
|
+
## 0.1.42 — 2026-11-13
|
|
9
|
+
|
|
10
|
+
- Accept the reviewed DSH `0.2.2-rc.2` Agent/Session/Settings carrier without bundling a DSH runtime or enabling unreviewed prereleases. Preserve the existing supported carriers and Cindy handshake identity.
|
|
11
|
+
- Revalidate native Session observers and controller/subagent reads against the RC.2 carrier; batched appends still publish the existing per-event observation API. Real handset, relay, OAuth and model calls remain separate acceptance requirements.
|
|
12
|
+
|
|
3
13
|
## 0.1.41 — 2026-11-08
|
|
4
14
|
|
|
5
15
|
- Accept the exact DSH `0.2.2-rc.1` Agent/Session/Settings carrier alongside the existing 0.2.1 RC and 0.2.2-alpha.2 peers. Keep DSH packages host-provided and preserve 0.1.40's complete feature set, including credentials without keytar.
|
package/README.md
CHANGED
|
@@ -4,12 +4,14 @@ A Host-side adapter connecting current Cindy clients to DeepSeek Harness.
|
|
|
4
4
|
|
|
5
5
|
## Requirements and installation
|
|
6
6
|
|
|
7
|
-
Version **0.1.
|
|
7
|
+
Version **0.1.43** adds exact DSH `0.2.2-rc.3` compatibility while preserving the existing features and supported carriers. Cindy's handshake identity is unchanged. Handset re-entry, rendering and white-screen acceptance remain separate.
|
|
8
8
|
|
|
9
|
-
It supports the exact **DSH 0.2.2-rc.1**
|
|
9
|
+
It supports the exact **DSH 0.2.2-rc.1, 0.2.2-rc.2 and 0.2.2-rc.3** carriers, while retaining `0.2.2-alpha.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.1-rc.5`. DSH 0.2.2 requires **Node.js >=24.9**; older carriers retain this plugin's Node.js >=22.16 minimum. Agent/session/settings peers are explicitly allowed, not a blanket promise for future prereleases. The packed candidate passed 1,239 tests on an isolated real rc3 SDK (4 skipped), core contracts 7/7 and clean-install Web runtime smoke 30/30. No real account or handset was used; installation, UI, relay and handset acceptance are distinct checks. See [release verification](<doc/releases/0.1.43.md>) for scope.
|
|
10
|
+
|
|
11
|
+
Install `dsh-cindy-host@0.1.43` through the Desktop plugin manager; CLI-managed profiles can use:
|
|
10
12
|
|
|
11
13
|
```sh
|
|
12
|
-
dsh plugin --profile <profile> add dsh-cindy-host@0.1.
|
|
14
|
+
dsh plugin --profile <profile> add dsh-cindy-host@0.1.43
|
|
13
15
|
```
|
|
14
16
|
|
|
15
17
|
Reload the Host plugin after installation. A full DSH restart is separate. Keep existing Cindy sign-in, device identity and settings; do not run two Host processes with the same identity.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-cindy-host",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.43",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "Cindy 手机客户端连接 DSH 的 Host 侧插件:会话/消息/审批/todo/goal 的手机通道,以及配套的设置卡片",
|
|
6
6
|
"license": "MIT",
|
|
@@ -68,9 +68,9 @@
|
|
|
68
68
|
},
|
|
69
69
|
"//peerDependencies": "DSH 自己的包必须由宿主提供,绝不能声明成 dependency/optionalDependency:pnpm 会把它们**连同整代依赖图**装进 profile,宿主再组合这个混合体就起不来(实测:`^0.1.1-rc.2` 会把 28 个 0.1.1-rc.2 的包装进一个 0.1.5-rc.2 的宿主,profile 启动失败于 dsh-client-file-upload / dsh-session)。区间必须覆盖宿主那一代(semver 的预发布规则:`^0.1.1-rc.2` 匹配不到 `0.1.5-rc.2`),与生态里 dsh-codex / dsh-cost-meter 的写法一致;`0.2.0-rc.2` 需要 `>=0.2.0-rc.1 <0.3.0-0`。",
|
|
70
70
|
"peerDependencies": {
|
|
71
|
-
"@deepseek-ai/dsh-agent": "0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5 || 0.2.2-alpha.2 || 0.2.2-rc.1",
|
|
72
|
-
"@deepseek-ai/dsh-session": "0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5 || 0.2.2-alpha.2 || 0.2.2-rc.1",
|
|
73
|
-
"@deepseek-ai/dsh-settings": "0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5 || 0.2.2-alpha.2 || 0.2.2-rc.1",
|
|
71
|
+
"@deepseek-ai/dsh-agent": "0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5 || 0.2.2-alpha.2 || 0.2.2-rc.1 || 0.2.2-rc.2 || 0.2.2-rc.3",
|
|
72
|
+
"@deepseek-ai/dsh-session": "0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5 || 0.2.2-alpha.2 || 0.2.2-rc.1 || 0.2.2-rc.2 || 0.2.2-rc.3",
|
|
73
|
+
"@deepseek-ai/dsh-settings": "0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5 || 0.2.2-alpha.2 || 0.2.2-rc.1 || 0.2.2-rc.2 || 0.2.2-rc.3",
|
|
74
74
|
"@deepseek-ai/schemastery": "^3.18.1 || 3.18.6-alpha.1"
|
|
75
75
|
},
|
|
76
76
|
"//peerDependenciesMeta": "**故意没有这个字段。** `@deepseek-ai/dsh-host-apiproxy` 曾经在这里标 optional,但 0.2 已经删掉了这个包,而 `evaluatePluginCompatibility` 会遍历 `peerDependencies` 的**每一个键且不查 `peerDependenciesMeta`**,所以只要它出现在 peers 里,`dsh plugin add` 就会直接拒绝安装(`installation rejected`),启动时 bundle 也会被静默跳过、`dsh-cindy-host` 行根本不会出现。该适配器本来就走惰性 `require` + 失败降级(见 src/dsh-plugin.js 的 apiProxy 分支),从 peers 里移除不改变任何运行时行为,只是让两道门禁都能正确判定。",
|
package/src/host-version.js
CHANGED