docs(dsh): clarify optional question service compatibility

Signed-off-by: XiaoSeS <87064762+XiaoSeS@users.noreply.github.com>
This commit is contained in:
XiaoSeS 2026-10-20 17:54:34 +08:00
parent 16a2b28861
commit 53cb1c3910
3 changed files with 3 additions and 3 deletions

View file

@ -213,7 +213,7 @@ Client 通过官方槽位声明生命周期与 layout/configForms 服务依赖
The candidate branch adds `0.2.1-rc.2` alongside retained `0.2.0-rc.2`; this supersedes the single-release candidate wording above, without changing published plugin `0.3.0` or creating a release. Peers enumerate these exact prereleases with `||`, never a future-version range. Core Host modules, DSH/app-boot and every injected Client owning manifest must share one release. Every write re-reads disk manifests and verifies the Host anchors' resolution; mixed, unknown, unreadable and stale graphs fail closed. Node remains `>=24.2.0 <25`.
`0.2.0-rc.2` retains both documented Cordis families. The new official Host requires the complete `4.0.5 / loader 1.0.6 / include 1.0.10 / timer 1.1.7` family. Optional user questions keep the same published `ask` signature in both RCs and use the matching release. Absence preserves the existing plugin confirmation fallback.
`0.2.0-rc.2` retains both documented Cordis families. The new official Host requires the complete `4.0.5 / loader 1.0.6 / include 1.0.10 / timer 1.1.7` family. Optional user questions keep the same published `ask` signature in both enumerated RCs. They are selected by Host service availability and are not part of the mandatory runtime-version gate; their peer declaration permits either listed RC without enforcing same-release identity. This does not extend support to other question-service versions. Absence preserves the existing plugin confirmation fallback.
Upstream npm artifacts for the two releases were compared: user-questions declarations/implementation are unchanged; Gateway now requires an explicit Peer for direct in-process calls, while the plugin uses generated Remote bindings. The integration observers must use the official Connection Peer API on the new release. The retained generator emits the shared RPC contract while source checks use current Host/Client declarations. Both generators enforce registered workspace boundaries for merged declarations. The new generator also emits an import from `@deepseek-ai/dsh-typert-protocol/remote-info`, a subpath absent from the retained RC. Keeping the retained compiler preserves the common generated format; it has no runtime protocol dependency and does not downgrade the current protocol module.

View file

@ -24,7 +24,7 @@ This version uses the independent `dsh-v0.2.1` release tag and retains the DSH d
Windows browser acceptance does not establish complete native Windows Host filesystem support. CI results do not replace desktop, model, or target-instance acceptance. See the repository's [compatibility design](../../openspec/changes/add-dsh-native-plugin/compatibility-design.md) and [acceptance criteria](../../openspec/changes/add-dsh-native-plugin/acceptance.md).
This branch contains the unreleased compatibility fix for Issue #981. Published plugin `0.3.0` does not include it. Unknown releases and mixed Host/Client graphs reject new writes. Optional `userQuestions` must match the Host release; absent service falls back to the plugin confirmation dialog. New-RC native Host/browser and cross-platform acceptance remain pending until recorded.
This branch contains the unreleased compatibility fix for Issue #981. Published plugin `0.3.0` does not include it. Unknown releases and mixed Host/Client graphs reject new writes. Optional `userQuestions` is enabled by Host service availability; it is not part of the mandatory write-version gate. Its API is identical in the two enumerated RCs, both of which the peer declaration permits. An absent service falls back to the plugin confirmation dialog. New-RC native Host/browser and cross-platform acceptance remain pending until recorded.
## Build and package

View file

@ -24,7 +24,7 @@ SkillHub 的 DSH 原生插件。在 DSH 侧栏打开 **技能中心**,匿名
Windows 浏览器验证不等于 Windows 原生 Host 的全部文件操作已经验证。CI 的平台矩阵也不替代真实桌面、模型及目标实例验收。完整支持边界见仓库内的 [兼容设计](../../openspec/changes/add-dsh-native-plugin/compatibility-design.md) 和 [验收标准](../../openspec/changes/add-dsh-native-plugin/acceptance.md)。
本分支包含 Issue #981 的候选兼容修复,尚未发布;已发布的插件 `0.3.0` 不包含此修复。其他 RC、未来发行版、混装模块和 Host/Client 版本不一致均拒绝新写入。可选 `userQuestions` 使用与宿主对应的精确 RC,缺失时仍回退插件确认框。
本分支包含 Issue #981 的候选兼容修复,尚未发布;已发布的插件 `0.3.0` 不包含此修复。其他 RC、未来发行版、混装模块和 Host/Client 版本不一致均拒绝新写入。可选 `userQuestions` 按宿主服务是否可用启用,缺失时仍回退插件确认框;其版本不属于必需写入门禁。两个已列 RC 的问答 API 一致,peer 声明允许二者,不据此承诺其他版本兼容。
## 构建与打包