dsh-kingdee v0.17.0

Release notes — v0.17.0

English | Chinese

Release date: 2026-11-02

A dual-line compatibility release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness. It keeps the build on 0.2.2-alpha.2 — the master preview line it has been aligned to — and additionally verifies the plugin against 0.2.1-rc.5, the latest dist-tag, the newest published release, and the runtime the desktop app ships. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Why this release exists

DeepSeek Harness publishes two lines at once: the latest tag tracks the newest point release, while alpha tracks master. At the time of writing latest is 0.2.1-rc.5 (published 2026-10-29) and alpha is 0.2.2-alpha.2 (published 2026-10-27). A user who installs DSH from the desktop app or from latest runs rc.5; the 0.16.0 release only ever exercised alpha.2. 0.17.0 closes that gap with an explicit verification matrix instead of assuming that one line implies the other.

Changed

• Two verified lines, one source tree. The rc.5 line was verified in a separate environment pinned to @deepseek-ai/dsh-*@0.2.1-rc.5, @deepseek-ai/cordis@4.0.5 and @deepseek-ai/schemastery@3.18.5. Its src/, test/, scripts/, locale/, skills/, docs/, .github/, cordis.patch.yml, tsconfig*.json and tsdown.config.ts are byte-identical to this tree (verified by per-file hash), so the result describes this package and not a variant of it.
• No dependency change; the peers already covered both lines. cordis 4.0.5 falls inside the existing ^4.0.4 range and schemastery 3.18.5 inside ^3.18.4, so the widening done in 0.16.0 (^4.0.4 || ^4.0.6-alpha.1, ^3.18.4 || ~3.18.6-alpha.1) admits the rc.5 pair unchanged. devDependencies stay pinned to 0.2.2-alpha.2, because the manifest can name only one build baseline.
• Source change: none. No file under src/, test/, scripts/, .github/, skills/, cordis.patch.yml or the build configuration changed, and no configuration field moved: the plugin behaves exactly as 0.16.0.
• Supply-chain exemption untouched. The workspace list already exempts the pinned alpha.2 set; no rc.5 entry was needed because the exemption list is derived from the lockfile, which did not move.

Checked against the 0.2.1-rc.5 line (all confirmed as no impact)

The run from the previously-aligned baseline (0.2.1-rc.2) to 0.2.1-rc.5 adds 19 commits, of which exactly two are plugin-facing upgrade guides. Both were read in full:

• Blank-Session reuse (v0.2.1-rc.2/new-session-blank-reuse) — New Session in Web and Desktop reuses the first unstarted blank Session in the Workspace instead of creating a fresh Agent per call. This is Web/Desktop Session-lifecycle behavior; it reads no tool, credential, settings-card or locale seam.
• Reasoning body slots (v0.2.1-rc.4/reasoning-body-props) — contributions to conversation.chat.reasoning.body now receive the original model output in rawText, with text carrying Chat's prepared display text. This plugin registers no reasoning renderer and no Chat slot contribution, so neither field reaches it.

Beyond the guides, the seam-by-seam comparison was done by building against rc.5 rather than by reading release prose:

• Tool registration. defineTool({ … }) plus ctx.tools.register(definition) in src/tools.ts compiles unchanged against dsh-tools@0.2.1-rc.5; DefineToolOptions and ToolDefinition keep the mandatory output.schema / render projections.
• Credential seam. credentialRef() and ctx.credentials.resolve() are used exactly as before; the resolved { value } shape is unchanged.
• Volatile config schema. Schema.string().volatile() and the whole Config object still type-check under schemastery@3.18.5 + cordis@4.0.5, so the per-operation captureConfig contract holds on this line too.
• Settings card and locale. ctx.configForms.get(), slots and remote compile against dsh-client-ui-settings@0.2.1-rc.5, and the card's single { en, zh } LocaleRuntime.register() call compiles against dsh-client-locale@0.2.1-rc.5.
• dsh.client.inject manifest. All five referenced packages (dsh-client-locale, dsh-client-ui-settings, dsh-client-ui-plugin-manager, dsh-api-remotes, dsh-client-connection) publish at 0.2.1-rc.5 with a web client bundle, so no entry had to be removed.

Update notes

• Install: dsh plugin --profile web add dsh-kingdee@0.17.0 into a DSH profile, then enable the row.
• Update: run dsh plugin --profile web update dsh-kingdee, or dsh plugin --profile web add dsh-kingdee@0.17.0 to pin the version.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer.
• Not a mandatory upgrade: the engines.dsh range is unchanged at >=0.1.7-alpha.2 <0.3.0, so dsh-kingdee@0.16.0 and 0.15.1 are still admitted on both lines.

Verification

• rc.5 line (pinned 0.2.1-rc.5 / cordis 4.0.5 / schemastery 3.18.5): npx tsc -p tsconfig.json --noEmit clean, npm run build clean, 15/15 unit tests pass.
• alpha.2 line (pinned 0.2.2-alpha.2 / cordis 4.0.6-alpha.1 / schemastery 3.18.6-alpha.1): npx tsc -p tsconfig.json --noEmit clean, npm run build clean, 15/15 unit tests pass.
• node scripts/check-docs-language.ts and the structural/typography document linter both report zero findings across all bilingual pairs.
• The rc.5 environment's src/ tree hashes match this repository file by file, so both results describe the same code.
• Not verified: a live boot into a real rc.5 or alpha.2 profile, and — as always — no live Kingdee tenant.

---

发行说明 — v0.17.0

英文 | 中文

发行日期：2026-11-02

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布 v0.17.0，这是一个双版本线兼容版本：构建仍钉定 0.2.2-alpha.2（本插件所对齐的 master 预览线），并额外针对 0.2.1-rc.5 完成验证 —— 后者是 npm 的 latest 标签、最新正式发布，也是桌面版实际内置的运行时。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

本版为何存在

DeepSeek Harness 同时维护两条线：latest 标签跟最新的节点版本发布，alpha 标签跟 master。撰写本文时 latest 是 0.2.1-rc.5（2026-10-29 发布），alpha 是 0.2.2-alpha.2（2026-10-27 发布）。从桌面版或 latest 安装 DSH 的用户实际跑的是 rc.5，而 0.16.0 只验证过 alpha.2。0.17.0 用一张明确的验证矩阵补上这个缺口，而不是假设一条线就等于另一条线。

变更

• 两条已验证版本线，同一份源码。 rc.5 线在一个独立环境中验证，钉定 @deepseek-ai/dsh-*@0.2.1-rc.5、@deepseek-ai/cordis@4.0.5 与 @deepseek-ai/schemastery@3.18.5。该环境的 src/、test/、scripts/、locale/、skills/、docs/、.github/、cordis.patch.yml、tsconfig*.json 与 tsdown.config.ts 与本仓库逐字节相同（已按文件哈希核对），因此这个结论描述的是本包本身，而不是它的某个变体。
• 依赖零改动：peer 区间本就覆盖两条线。 cordis 4.0.5 落在既有的 ^4.0.4 区间内，schemastery 3.18.5 落在 ^3.18.4 内，因此 0.16.0 所做的放宽（^4.0.4 || ^4.0.6-alpha.1、^3.18.4 || ~3.18.6-alpha.1）原封不动就容纳了 rc.5 那一对版本。devDependencies 仍钉在 0.2.2-alpha.2，因为清单只能声明一个构建基线。
• 源码改动：无。 src/、test/、scripts/、.github/、skills/、cordis.patch.yml 与构建配置下均无文件改动，配置字段也没有任何迁移：插件行为与 0.16.0 完全一致。
• 供应链豁免清单未动。 工作区名单已对钉定的 alpha.2 包集合豁免；由于该名单由锁文件推导，而锁文件未变动，因此不需要新增 rc.5 条目。

已对照 0.2.1-rc.5 线核对（均确认为无影响）

从上次对齐的基线（0.2.1-rc.2）到 0.2.1-rc.5 共 19 个提交，其中恰有两条面向插件的升级指南。两者均已完整阅读：

• 空会话复用（v0.2.1-rc.2/new-session-blank-reuse）—— Web 与桌面版的「新建会话」改为复用工作区中第一个未启动、未归档的空会话，而不是每次调用都新建 Agent。这属于 Web/桌面端的会话生命周期行为，不读取任何工具、凭据、设置卡片或 locale 接口。
• Reasoning body 槽位（v0.2.1-rc.4/reasoning-body-props）—— 向 conversation.chat.reasoning.body 的贡献现在通过新增的 rawText 字段拿到模型原始输出，text 则改为 Chat 预处理后的展示文本。本插件不注册 reasoning 渲染器，也不向 Chat 槽位投稿，因此这两个字段都触及不到它。

除升级指南外，逐接口的比对是直接以 rc.5 构建得出的，而不是读发布说明推断的：

• 工具注册。 src/tools.ts 中的 defineTool({ … }) 加 ctx.tools.register(definition) 在 dsh-tools@0.2.1-rc.5 下照常编译；DefineToolOptions 与 ToolDefinition 仍保留必需的 output.schema / render 投影。
• 凭据接口。 credentialRef() 与 ctx.credentials.resolve() 的用法与之前完全一致；解析返回的 { value } 形状未变。
• Volatile 配置 schema。 Schema.string().volatile() 与整个 Config 对象在 schemastery@3.18.5 + cordis@4.0.5 下仍通过类型检查，因此在 rc.5 线上「每次操作捕获一次配置」的契约同样成立。
• 设置卡片与 locale。 ctx.configForms.get()、slots 与 remote 在 dsh-client-ui-settings@0.2.1-rc.5 下编译通过；卡片单次调用的 { en, zh } LocaleRuntime.register() 在 dsh-client-locale@0.2.1-rc.5 下也编译通过。
• dsh.client.inject 清单。 所列五个包（dsh-client-locale、dsh-client-ui-settings、dsh-client-ui-plugin-manager、dsh-api-remotes、dsh-client-connection）在 0.2.1-rc.5 上均照常发布且带 web 客户端 bundle，因此无需删除任何条目。

更新说明

• 安装命令：dsh plugin --profile web add dsh-kingdee@0.17.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin --profile web update dsh-kingdee；或执行 dsh plugin --profile web add dsh-kingdee@0.17.0 锁定版本。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。
• 非强制升级：engines.dsh 区间保持 >=0.1.7-alpha.2 <0.3.0 不变，因此 dsh-kingdee@0.16.0 与 0.15.1 在两条线上同样被准入。

验证

• rc.5 线（钉定 0.2.1-rc.5 / cordis 4.0.5 / schemastery 3.18.5）：npx tsc -p tsconfig.json --noEmit 零错误、npm run build 构建干净、15/15 单元测试通过。
• alpha.2 线（钉定 0.2.2-alpha.2 / cordis 4.0.6-alpha.1 / schemastery 3.18.6-alpha.1）：npx tsc -p tsconfig.json --noEmit 零错误、npm run build 构建干净、15/15 单元测试通过。
• node scripts/check-docs-language.ts 与结构/文字排版检查器在全部中英文档对上均为零发现。
• rc.5 环境的 src/ 目录与本仓库逐文件哈希一致，因此两项结果描述的是同一份代码。
• 未验证项：在真实 rc.5 或 alpha.2 profile 中的实际启动；以及一如既往，未做真实金蝶账套联调。

dsh-kingdee v0.16.0

Release notes — v0.16.0

English | Chinese

Release date: 2026-10-28

A DeepSeek Harness 0.2.2-alpha.2 alignment release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness: every @deepseek-ai/dsh-* development dependency moves to 0.2.2-alpha.2, the lockfile and the pnpm supply-chain exemption are regenerated against that release, and @deepseek-ai/cordis / @deepseek-ai/schemastery move to ~4.0.6-alpha.1 / ~3.18.6-alpha.1. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Changed

• Harness alignment. Upgraded all @deepseek-ai/dsh-* development dependencies from DeepSeek Harness 0.2.1-rc.2 to 0.2.2-alpha.2, and regenerated the lockfile against 0.2.2-alpha.2. @deepseek-ai/cordis moves to ~4.0.6-alpha.1 and @deepseek-ai/schemastery to ~3.18.6-alpha.1.
• Peer ranges widened. @deepseek-ai/cordis becomes ^4.0.4 || ^4.0.6-alpha.1 and @deepseek-ai/schemastery becomes ^3.18.4 || ~3.18.6-alpha.1, so the plugin keeps accepting the 4.0.4 / 4.0.5 / 3.18.4 / 3.18.5 releases it was previously verified against while also accepting the new prereleases it is now built and tested against.
• Supply-chain exemption rebuilt. The workspace file exempts the 0.2.2-alpha.2 package set from pnpm's minimum-release-age gate, which otherwise rejects DSH's continuously published prereleases. The list stays a single lockfile-derived block.
• Source change: none. No file under src/, test/, scripts/, .github/, skills/, cordis.patch.yml or the build configuration changed, and no configuration field moved: the plugin behaves exactly as 0.15.1.

Checked against 0.2.2-alpha.2 (all confirmed as no impact)

DeepSeek Harness 0.2.2-alpha.2 announced three breaking changes that could reach a plugin. Each was checked against this repository rather than assumed harmless:

• Cordis Timer synchronized with upstream, changing return values. The plugin's only timer use is src/kd-core/transport.ts, which schedules its per-request deadline with the global setTimeout and clears it with clearTimeout. It never calls ctx.timer.timeout() / interval() / throttle() / debounce(), so the changed return values never reach it. Verified by grepping src/ for timer usage.
• dsh-tools split its declarations into Contracts / ToolExecutor / pipeline modules. src/tools.ts uses defineTool({ … }) plus ctx.tools.register(definition), and that call still type-checks. DefineToolOptions and ToolDefinition — including the mandatory output.schema and render projection — are declaration-identical between the 0.2.1-rc.2 and 0.2.2-alpha.2 lib/types/schema.d.ts / contracts.d.ts. The only change on the registration surface is additive: ToolsService.register gained an optional second parameter (ToolRegistrationOptions, for step-time activation), so the existing single-argument call remains valid.
• dsh.client manifest (platform / inject) semantics. Every package named in dsh.client.inject — dsh-client-locale, dsh-client-ui-settings, dsh-client-ui-plugin-manager, dsh-api-remotes, dsh-client-connection — still publishes at 0.2.2-alpha.2, still declares dsh.client.platform: "web", and still exports a ./client bundle, so no entry had to be removed. The bundle's only external module request, react, is unchanged.

Beyond the three announced changes, the settings-card seams were re-read as well: ctx.configForms.get(), slots and remote are declaration-identical between the two releases. The locale service changed once, by widening rather than breaking: LocaleRuntime.register()'s typed overload now also accepts extra-locale dictionaries (rc2 required exactly Record<BuiltInLocaleId, LocaleDictOf<N>>; alpha2 takes that intersected with Record<LocaleId, LocaleDictOf<N>>). The card registers { en, zh } in one call, which still satisfies the widened signature — confirmed by npx tsc -p tsconfig.json --noEmit.

Update notes

• Install: dsh plugin --profile web add dsh-kingdee@0.16.0 into a DSH profile, then enable the row.
• Update: run dsh plugin --profile web update dsh-kingdee, or dsh plugin --profile web add dsh-kingdee@0.16.0 to pin the version.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer.
• Not a mandatory upgrade: the engines.dsh range is unchanged at >=0.1.7-alpha.2 <0.3.0, so dsh-kingdee@0.15.1 is still admitted on DeepSeek Harness 0.2.2-alpha.2.

Verification

• node scripts/check-docs-language.ts passing clean with zero findings.
• npx tsc -p tsconfig.json --noEmit clean.
• npm run build clean (tsc -p tsconfig.build.json plus the tsdown client bundle).
• All 15 unit tests pass (npm test) against DeepSeek Harness 0.2.2-alpha.2.
• Not verified: a live boot into a real 0.2.2-alpha.2 profile, and — as always — no live Kingdee tenant.

---

发行说明 — v0.16.0

英文 | 中文

发行日期：2026-10-28

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布 v0.16.0，这是一个适配 DeepSeek Harness 0.2.2-alpha.2 的版本：全部 @deepseek-ai/dsh-* 开发依赖升至 0.2.2-alpha.2，锁文件与 pnpm 供应链豁免清单按该版本重新生成，@deepseek-ai/cordis 与 @deepseek-ai/schemastery 分别升至 ~4.0.6-alpha.1 与 ~3.18.6-alpha.1。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

变更

• 宿主对齐：全部 @deepseek-ai/dsh-* 开发依赖由 DeepSeek Harness 0.2.1-rc.2 升级至 0.2.2-alpha.2，锁文件按 0.2.2-alpha.2 重新生成。@deepseek-ai/cordis 升至 ~4.0.6-alpha.1，@deepseek-ai/schemastery 升至 ~3.18.6-alpha.1。
• peer 区间放宽：@deepseek-ai/cordis 改为 ^4.0.4 || ^4.0.6-alpha.1，@deepseek-ai/schemastery 改为 ^3.18.4 || ~3.18.6-alpha.1，因此本插件既继续接受此前验证过的 4.0.4 / 4.0.5 / 3.18.4 / 3.18.5，也接受当前构建与测试所用的新预发行版。
• 供应链豁免清单重建：工作区文件现对 0.2.2-alpha.2 的各包豁免 pnpm 的最小发布年龄闸门 —— 否则 DSH 持续发布的预发行版会被拦下。该名单保持单一且由锁文件推导的区块。
• 源码改动：无。 src/、test/、scripts/、.github/、skills/、cordis.patch.yml 与构建配置下均无文件改动，配置字段也没有任何迁移：插件行为与 0.15.1 完全一致。

已对照 0.2.2-alpha.2 核对（均确认为无影响）

DeepSeek Harness 0.2.2-alpha.2 公布了三项可能波及插件的破坏性变更。以下逐条对照本仓库实际代码核对，而非默认其无害：

• Cordis Timer 同步上游实现，返回值发生变化。 本插件唯一的计时器用法在 src/kd-core/transport.ts，它用全局 setTimeout 设定单次请求超时，并用 clearTimeout 清除；从不调用 ctx.timer.timeout() / interval() / throttle() / debounce()，因此变化后的返回值不会触及本插件。核对方式：在 src/ 中检索全部计时器用法。
• dsh-tools 把声明拆分为 Contracts / ToolExecutor / pipeline 等模块。 src/tools.ts 使用 defineTool({ … }) 加 ctx.tools.register(definition)，该调用仍能通过类型检查。DefineToolOptions 与 ToolDefinition —— 包括必需的 output.schema 与 render 投影 —— 在 0.2.1-rc.2 与 0.2.2-alpha.2 的 lib/types/schema.d.ts / contracts.d.ts 之间声明完全一致。注册接口上唯一的改动是纯新增：ToolsService.register 增加了一个可选第二参数（ToolRegistrationOptions，用于按步骤的条件启用），因此原有的单参数调用依然有效。
• dsh.client manifest（platform / inject）语义。 dsh.client.inject 中列出的每个包 —— dsh-client-locale、dsh-client-ui-settings、dsh-client-ui-plugin-manager、dsh-api-remotes、dsh-client-connection —— 在 0.2.2-alpha.2 上仍照常发布，仍各自声明 dsh.client.platform: "web"，也仍各自导出 ./client bundle，因此无需删除任何一项。bundle 唯一的外部模块请求 react 没有变化。

除上述三项公布变更外，设置卡片的服务缝也一并复核：ctx.configForms.get()、slots 与 remote 在两个版本之间声明完全一致。locale 服务有一处改动，属于放宽而非破坏：LocaleRuntime.register() 的带类型重载现在也接受额外语种字典（rc2 要求恰好为 Record<BuiltInLocaleId, LocaleDictOf<N>>；alpha2 则接受该类型与 Record<LocaleId, LocaleDictOf<N>> 的交叉类型）。卡片在单次调用中注册 { en, zh }，仍满足放宽后的签名 —— 已由 npx tsc -p tsconfig.json --noEmit 验证。

更新说明

• 安装命令：dsh plugin --profile web add dsh-kingdee@0.16.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin --profile web update dsh-kingdee；或执行 dsh plugin --profile web add dsh-kingdee@0.16.0 锁定版本。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。
• 非强制升级：engines.dsh 区间保持 >=0.1.7-alpha.2 <0.3.0 不变，因此 dsh-kingdee@0.15.1 在 DeepSeek Harness 0.2.2-alpha.2 上同样被准入。

验证

• node scripts/check-docs-language.ts 检查全部通过，零发现。
• npx tsc -p tsconfig.json --noEmit 零错误。
• npm run build 干净（tsc -p tsconfig.build.json 加 tsdown 客户端 bundle）。
• 15 项单元测试（npm test）在 DeepSeek Harness 0.2.2-alpha.2 上全部通过。
• 未验证项：在真实 0.2.2-alpha.2 profile 中的实际启动；以及一如既往，未做真实金蝶账套联调。

dsh-kingdee v0.15.1

Release notes — v0.15.1

English | Chinese

Release date: 2026-10-18

A DeepSeek Harness 0.2.1-rc.2 alignment release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness: every @deepseek-ai/dsh-* development dependency moves to 0.2.1-rc.2, the lockfile and the pnpm supply-chain exemption are regenerated against that release, and @deepseek-ai/cordis / @deepseek-ai/schemastery move to ^4.0.5 / ^3.18.5. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Changed

• Harness alignment. Upgraded all @deepseek-ai/dsh-* development dependencies from DeepSeek Harness 0.2.1-alpha.4 to 0.2.1-rc.2, and regenerated the lockfile against 0.2.1-rc.2. @deepseek-ai/cordis moves to ^4.0.5 and @deepseek-ai/schemastery to ^3.18.5. No seam this plugin consumes changed across 0.2.1-alpha.4 and 0.2.1-rc.2: the ctx.configForms.get() contract behind the settings card, plus the slots, locale, remote and connection contracts the card injects, are declaration-identical for this plugin's usage.
• Supply-chain exemption rebuilt. The workspace file exempts the 0.2.1-rc.2 package set from pnpm's minimum-release-age gate, which otherwise rejects DSH's continuously published prereleases. The list stays a single lockfile-derived block.
• Source change: none. No file under src/, test/, scripts/, .github/, skills/, cordis.patch.yml or the build configuration changed, and no configuration field moved: the plugin behaves exactly as 0.14.0.

Fixed

• The compatibility notes described the admission gate incorrectly in both languages. README.md, README.zh.md, INSTALL.md, INSTALL.zh.md, UPDATE.md and UPDATE.zh.md stated that the gate reads only the @deepseek-ai/dsh* peerDependencies and that "engines.dsh is not what the gate reads". Since DeepSeek Harness 0.2.1-alpha.4 an own engines.dsh range decides admission alone and the peers are ignored for that check. The notes now say so, and the admission conclusion is unchanged: the plugin declares engines.dsh: ">=0.1.7-alpha.2 <0.3.0", which admits it on 0.2.1-rc.2 without an exemption.
• The Chinese opening verification notes named the wrong runtime version. INSTALL.zh.md, USAGE.zh.md, CONFIG.zh.md, UPDATE.zh.md and UNINSTALL.zh.md said the harness's own compatibility check admitted the plugin on runtime 0.2.1-alpha.2 while the surrounding sentence named 0.2.1-alpha.4; they now name the version the release was actually verified on.

Update notes

• Install: dsh plugin --profile web add dsh-kingdee@0.15.0 into a DSH profile, then enable the row.
• Update: run dsh plugin --profile web update dsh-kingdee, or dsh plugin --profile web add dsh-kingdee@0.15.0 to pin the version.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer.
• Not a mandatory upgrade: the engines.dsh range is unchanged at >=0.1.7-alpha.2 <0.3.0, so dsh-kingdee@0.14.0 is still admitted on DeepSeek Harness 0.2.1-rc.2.

Verification

• pnpm run typecheck clean, pnpm run build clean (tsc -p tsconfig.build.json plus the tsdown client bundle), and all 15 unit tests pass (pnpm test) against DeepSeek Harness 0.2.1-rc.2.
• node scripts/check-docs-language.ts passing clean with zero findings.
• Not verified: a live boot into a real 0.2.1-rc.2 profile, and — as always — no live Kingdee tenant.

---

发行说明 — v0.15.1

英文 | 中文

发行日期：2026-10-18

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布 v0.15.0，这是一个适配 DeepSeek Harness 0.2.1-rc.2 的版本：全部 @deepseek-ai/dsh-* 开发依赖升至 0.2.1-rc.2，锁文件与 pnpm 供应链豁免清单按该版本重新生成，@deepseek-ai/cordis 与 @deepseek-ai/schemastery 分别升至 ^4.0.5 与 ^3.18.5。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

变更

• 宿主对齐：全部 @deepseek-ai/dsh-* 开发依赖由 DeepSeek Harness 0.2.1-alpha.4 升级至 0.2.1-rc.2，锁文件按 0.2.1-rc.2 重新生成。@deepseek-ai/cordis 升至 ^4.0.5，@deepseek-ai/schemastery 升至 ^3.18.5。0.2.1-alpha.4 与 0.2.1-rc.2 两个版本未改动本插件所使用的任何服务缝：设置卡片背后的 ctx.configForms.get() 契约，以及该卡片注入的 slots、locale、remote、connection 契约，就本插件的用法而言声明完全一致。
• 供应链豁免清单重建：工作区文件现对 0.2.1-rc.2 的各包豁免 pnpm 的最小发布年龄闸门 —— 否则 DSH 持续发布的预发行版会被拦下。该名单保持单一且由锁文件推导的区块。
• 源码改动：无。 src/、test/、scripts/、.github/、skills/、cordis.patch.yml 与构建配置下均无文件改动，配置字段也没有任何迁移：插件行为与 0.14.0 完全一致。

修复

• 两个语种的兼容性说明都错误描述了准入闸门。 README.md、README.zh.md、INSTALL.md、INSTALL.zh.md、UPDATE.md 与 UPDATE.zh.md 原先称闸门只读取 @deepseek-ai/dsh* 的 peerDependencies，且「闸门读取的不是 engines.dsh」。自 DeepSeek Harness 0.2.1-alpha.4 起，插件自有的 engines.dsh 区间单独决定准入，peer 在该项校验中被忽略。相关说明现已更正，且准入结论不变：本插件声明 engines.dsh: ">=0.1.7-alpha.2 <0.3.0"，因此在 0.2.1-rc.2 上无需豁免即被准入。
• 中文文档的首段验证说明写错了运行时版本。 INSTALL.zh.md、USAGE.zh.md、CONFIG.zh.md、UPDATE.zh.md 与 UNINSTALL.zh.md 曾称宿主自带的兼容性校验在运行时 0.2.1-alpha.2 上准入本插件，而同一句的其余部分写的是 0.2.1-alpha.4；现统一改为本版实际验证所用的版本。

更新说明

• 安装命令：dsh plugin --profile web add dsh-kingdee@0.15.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin --profile web update dsh-kingdee；或执行 dsh plugin --profile web add dsh-kingdee@0.15.0 锁定版本。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。
• 非强制升级：engines.dsh 区间保持 >=0.1.7-alpha.2 <0.3.0 不变，因此 dsh-kingdee@0.14.0 在 DeepSeek Harness 0.2.1-rc.2 上同样被准入。

验证

• pnpm run typecheck 零错误、pnpm run build 干净（tsc -p tsconfig.build.json 加 tsdown 客户端 bundle），15 项单元测试（pnpm test）在 DeepSeek Harness 0.2.1-rc.2 上全部通过。
• node scripts/check-docs-language.ts 检查全部通过，零发现。
• 未验证项：在真实 0.2.1-rc.2 profile 中的实际启动；以及一如既往，未做真实金蝶账套联调。

dsh-kingdee v0.15.0

Release notes — v0.15.0

English | Chinese

Release date: 2026-10-18

A DeepSeek Harness 0.2.1-rc.2 alignment release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness: every @deepseek-ai/dsh-* development dependency moves to 0.2.1-rc.2, the lockfile and the pnpm supply-chain exemption are regenerated against that release, and @deepseek-ai/cordis / @deepseek-ai/schemastery move to ^4.0.5 / ^3.18.5. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Changed

• Harness alignment. Upgraded all @deepseek-ai/dsh-* development dependencies from DeepSeek Harness 0.2.1-alpha.4 to 0.2.1-rc.2, and regenerated the lockfile against 0.2.1-rc.2. @deepseek-ai/cordis moves to ^4.0.5 and @deepseek-ai/schemastery to ^3.18.5. No seam this plugin consumes changed across 0.2.1-alpha.4 and 0.2.1-rc.2: the ctx.configForms.get() contract behind the settings card, plus the slots, locale, remote and connection contracts the card injects, are declaration-identical for this plugin's usage.
• Supply-chain exemption rebuilt. The workspace file exempts the 0.2.1-rc.2 package set from pnpm's minimum-release-age gate, which otherwise rejects DSH's continuously published prereleases. The list stays a single lockfile-derived block.
• Source change: none. No file under src/, test/, scripts/, .github/, skills/, cordis.patch.yml or the build configuration changed, and no configuration field moved: the plugin behaves exactly as 0.14.0.

Fixed

• The compatibility notes described the admission gate incorrectly in both languages. README.md, README.zh.md, INSTALL.md, INSTALL.zh.md, UPDATE.md and UPDATE.zh.md stated that the gate reads only the @deepseek-ai/dsh* peerDependencies and that "engines.dsh is not what the gate reads". Since DeepSeek Harness 0.2.1-alpha.4 an own engines.dsh range decides admission alone and the peers are ignored for that check. The notes now say so, and the admission conclusion is unchanged: the plugin declares engines.dsh: ">=0.1.7-alpha.2 <0.3.0", which admits it on 0.2.1-rc.2 without an exemption.
• The Chinese opening verification notes named the wrong runtime version. INSTALL.zh.md, USAGE.zh.md, CONFIG.zh.md, UPDATE.zh.md and UNINSTALL.zh.md said the harness's own compatibility check admitted the plugin on runtime 0.2.1-alpha.2 while the surrounding sentence named 0.2.1-alpha.4; they now name the version the release was actually verified on.

Update notes

• Install: dsh plugin --profile web add dsh-kingdee@0.15.0 into a DSH profile, then enable the row.
• Update: run dsh plugin --profile web update dsh-kingdee, or dsh plugin --profile web add dsh-kingdee@0.15.0 to pin the version.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer.
• Not a mandatory upgrade: the engines.dsh range is unchanged at >=0.1.7-alpha.2 <0.3.0, so dsh-kingdee@0.14.0 is still admitted on DeepSeek Harness 0.2.1-rc.2.

Verification

• pnpm run typecheck clean, pnpm run build clean (tsc -p tsconfig.build.json plus the tsdown client bundle), and all 15 unit tests pass (pnpm test) against DeepSeek Harness 0.2.1-rc.2.
• node scripts/check-docs-language.ts passing clean with zero findings.
• Not verified: a live boot into a real 0.2.1-rc.2 profile, and — as always — no live Kingdee tenant.

---

发行说明 — v0.15.0

英文 | 中文

发行日期：2026-10-18

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布 v0.15.0，这是一个适配 DeepSeek Harness 0.2.1-rc.2 的版本：全部 @deepseek-ai/dsh-* 开发依赖升至 0.2.1-rc.2，锁文件与 pnpm 供应链豁免清单按该版本重新生成，@deepseek-ai/cordis 与 @deepseek-ai/schemastery 分别升至 ^4.0.5 与 ^3.18.5。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

变更

• 宿主对齐：全部 @deepseek-ai/dsh-* 开发依赖由 DeepSeek Harness 0.2.1-alpha.4 升级至 0.2.1-rc.2，锁文件按 0.2.1-rc.2 重新生成。@deepseek-ai/cordis 升至 ^4.0.5，@deepseek-ai/schemastery 升至 ^3.18.5。0.2.1-alpha.4 与 0.2.1-rc.2 两个版本未改动本插件所使用的任何服务缝：设置卡片背后的 ctx.configForms.get() 契约，以及该卡片注入的 slots、locale、remote、connection 契约，就本插件的用法而言声明完全一致。
• 供应链豁免清单重建：工作区文件现对 0.2.1-rc.2 的各包豁免 pnpm 的最小发布年龄闸门 —— 否则 DSH 持续发布的预发行版会被拦下。该名单保持单一且由锁文件推导的区块。
• 源码改动：无。 src/、test/、scripts/、.github/、skills/、cordis.patch.yml 与构建配置下均无文件改动，配置字段也没有任何迁移：插件行为与 0.14.0 完全一致。

修复

• 两个语种的兼容性说明都错误描述了准入闸门。 README.md、README.zh.md、INSTALL.md、INSTALL.zh.md、UPDATE.md 与 UPDATE.zh.md 原先称闸门只读取 @deepseek-ai/dsh* 的 peerDependencies，且「闸门读取的不是 engines.dsh」。自 DeepSeek Harness 0.2.1-alpha.4 起，插件自有的 engines.dsh 区间单独决定准入，peer 在该项校验中被忽略。相关说明现已更正，且准入结论不变：本插件声明 engines.dsh: ">=0.1.7-alpha.2 <0.3.0"，因此在 0.2.1-rc.2 上无需豁免即被准入。
• 中文文档的首段验证说明写错了运行时版本。 INSTALL.zh.md、USAGE.zh.md、CONFIG.zh.md、UPDATE.zh.md 与 UNINSTALL.zh.md 曾称宿主自带的兼容性校验在运行时 0.2.1-alpha.2 上准入本插件，而同一句的其余部分写的是 0.2.1-alpha.4；现统一改为本版实际验证所用的版本。

更新说明

• 安装命令：dsh plugin --profile web add dsh-kingdee@0.15.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin --profile web update dsh-kingdee；或执行 dsh plugin --profile web add dsh-kingdee@0.15.0 锁定版本。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。
• 非强制升级：engines.dsh 区间保持 >=0.1.7-alpha.2 <0.3.0 不变，因此 dsh-kingdee@0.14.0 在 DeepSeek Harness 0.2.1-rc.2 上同样被准入。

验证

• pnpm run typecheck 零错误、pnpm run build 干净（tsc -p tsconfig.build.json 加 tsdown 客户端 bundle），15 项单元测试（pnpm test）在 DeepSeek Harness 0.2.1-rc.2 上全部通过。
• node scripts/check-docs-language.ts 检查全部通过，零发现。
• 未验证项：在真实 0.2.1-rc.2 profile 中的实际启动；以及一如既往，未做真实金蝶账套联调。

dsh-kingdee v0.14.0

Release notes — v0.14.0

English | Chinese

Release date: 2026-10-16

Twentieth release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness. It is a DeepSeek Harness 0.2.1-alpha.4 alignment and license-statement correction release: every @deepseek-ai/dsh-* development dependency moves to 0.2.1-alpha.4, the lockfile and the pnpm supply-chain exemption are regenerated against that release, and the two README files no longer claim a proprietary license that the LICENSE file has not carried since 0.5.0. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Changed

• Harness alignment. Upgraded all @deepseek-ai/dsh-* development dependencies from DeepSeek Harness 0.2.1-alpha.2 to 0.2.1-alpha.4, and regenerated the lockfile against 0.2.1-alpha.4. @deepseek-ai/cordis remains ^4.0.4 and @deepseek-ai/schemastery remains ^3.18.4. No seam this plugin consumes changed across 0.2.1-alpha.3 and 0.2.1-alpha.4: @deepseek-ai/dsh-web, @deepseek-ai/dsh-tools, @deepseek-ai/dsh-credentials and the ctx.configForms.get() contract behind the settings card are all source-identical for this plugin's usage.
• Supply-chain exemption rebuilt. The workspace file exempts the 0.2.1-alpha.4 package set from pnpm's minimum-release-age gate, which otherwise rejects DSH's continuously published prereleases. The previous list also carried a second minimumReleaseAgeExclude key whose stale 0.2.0-rc.2 entries made pnpm reject the regenerated lockfile; the list is now a single lockfile-derived block.
• Source change: none. No file under src/, test/, scripts/, .github/, skills/, cordis.patch.yml or the build configuration changed, and no configuration field moved: the plugin behaves exactly as 0.13.0.

Fixed

• The README license section contradicted the LICENSE file in both languages. README.md and README.zh.md described this repository as under a "proprietary license (all rights reserved)", while LICENSE and package.json.license have carried the MIT License since 0.5.0; GitHub and npm both report MIT for the published package. Both README files now state MIT and link the LICENSE file.
• The changelog never recorded the license revert. The 0.2.0 entry still described the proprietary grant as current. It now marks that grant as reversed, and the 0.5.0 entry records the MIT restoration, so the version history matches the shipped artifacts.

Update notes

• Install: dsh plugin --profile web add dsh-kingdee@0.14.0 into a DSH profile, then enable the row.
• Update: run dsh plugin --profile web update dsh-kingdee, or dsh plugin --profile web add dsh-kingdee@0.14.0 to pin the version.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer.
• Not a mandatory upgrade: the peer ranges are unchanged at >=0.1.7-alpha.2 <0.3.0, so dsh-kingdee@0.13.0 is still admitted on DeepSeek Harness 0.2.1-alpha.4.

Verification

• pnpm run typecheck clean, pnpm run build clean (tsc -p tsconfig.build.json plus the tsdown client bundle), and all 15 unit tests pass (pnpm test) against DeepSeek Harness 0.2.1-alpha.4.
• node scripts/check-docs-language.ts passing clean with zero findings.
• Not verified: a live boot into a real 0.2.1-alpha.4 profile, and — as always — no live Kingdee tenant.

---

发行说明 — v0.14.0

英文 | 中文

发行日期：2026-10-16

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布第二十版 v0.14.0。这是一个适配 DeepSeek Harness 0.2.1-alpha.4 并修正许可证声明的版本：全部 @deepseek-ai/dsh-* 开发依赖升至 0.2.1-alpha.4，锁文件与 pnpm 供应链豁免清单按该版本重新生成，两个语种的 README 也不再声称 LICENSE 文件自 0.5.0 起就已不再采用的专有许可。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

变更

• 宿主对齐：全部 @deepseek-ai/dsh-* 开发依赖由 DeepSeek Harness 0.2.1-alpha.2 升级至 0.2.1-alpha.4，锁文件按 0.2.1-alpha.4 重新生成。@deepseek-ai/cordis 保持 ^4.0.4，@deepseek-ai/schemastery 保持 ^3.18.4。0.2.1-alpha.3 与 0.2.1-alpha.4 两个版本未改动本插件所使用的任何服务缝：@deepseek-ai/dsh-web、@deepseek-ai/dsh-tools、@deepseek-ai/dsh-credentials，以及设置卡片背后的 ctx.configForms.get() 契约，就本插件的用法而言源码完全一致。
• 供应链豁免清单重建：工作区文件现对 0.2.1-alpha.4 的各包豁免 pnpm 的最小发布年龄闸门 —— 否则 DSH 持续发布的预发行版会被拦下。此前的名单还带有第二个 minimumReleaseAgeExclude 键，其过期的 0.2.0-rc.2 条目会让 pnpm 拒绝重新生成的锁文件；该名单现为单一且由锁文件推导的区块。
• 源码改动：无。 src/、test/、scripts/、.github/、skills/、cordis.patch.yml 与构建配置下均无文件改动，配置字段也没有任何迁移：插件行为与 0.13.0 完全一致。

修复

• 两个语种的 README 许可证章节都与 LICENSE 文件矛盾。 README.md 与 README.zh.md 把本仓库描述为采用「专有许可证（保留所有权利）」，而 LICENSE 与 package.json.license 自 0.5.0 起一直是 MIT 许可证；GitHub 与 npm 对已发布包的识别结果也都是 MIT。两个 README 现均写明 MIT 并链接 LICENSE 文件。
• 更新日志从未记录许可证回退。 0.2.0 条目仍把专有授权描述为现行状态。该条目现标注该授权已被撤销，并在 0.5.0 条目中记录 MIT 的恢复，使版本历史与实际发布物一致。

更新说明

• 安装命令：dsh plugin --profile web add dsh-kingdee@0.14.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin --profile web update dsh-kingdee；或执行 dsh plugin --profile web add dsh-kingdee@0.14.0 锁定版本。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。
• 非强制升级：peer 区间保持 >=0.1.7-alpha.2 <0.3.0 不变，因此 dsh-kingdee@0.13.0 在 DeepSeek Harness 0.2.1-alpha.4 上同样被准入。

验证

• pnpm run typecheck 零错误、pnpm run build 干净（tsc -p tsconfig.build.json 加 tsdown 客户端 bundle），15 项单元测试（pnpm test）在 DeepSeek Harness 0.2.1-alpha.4 上全部通过。
• node scripts/check-docs-language.ts 检查全部通过，零发现。
• 未验证项：在真实 0.2.1-alpha.4 profile 中的实际启动；以及一如既往，未做真实金蝶账套联调。

dsh-kingdee v0.13.0

发行说明 — v0.13.0

英文 | 中文

发行日期：2026-10-11

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布第十九版 v0.13.0。这是一个适配 DeepSeek Harness 0.2.1-alpha.2 与插件展示元数据规范的版本：包含了原生 icon.svg 矢量图标、中英双语展示资源清单（locale/en.json、locale/zh.json）、自包含的 prepare 构建脚本、纯 TypeScript 架构以及遵循最新规范的 --profile <name> 命令行选项排布。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

新增

• 展示元数据与专属图标：内置原生 icon.svg 矢量图标与中英双语展示清单（locale/en.json、locale/zh.json），完全符合 DeepSeek Harness 0.2.1-alpha.2 插件管理器规范。在 package.json 中声明顶层 icon 字段（指向 ./icon.svg），并规范导出 ./locale/*.json 与 ./icon 资源。
• 自包含构建脚本：在 package.json 中配置 prepare 脚本（执行 tsc -p tsconfig.build.json && tsdown），支持直接通过 Git 仓库安装，不依赖宿主环境是否预装全局 pnpm。

变更

• 开发依赖对齐：全部 @deepseek-ai/dsh-* 开发依赖由 0.2.0-rc.2 升级至 0.2.1-alpha.2；@deepseek-ai/cordis 保持 ^4.0.4，@deepseek-ai/schemastery 保持 ^3.18.4。
• 兼容性区间保持稳定：peer 依赖区间保持 >=0.1.7-alpha.2 <0.3.0，因此 0.12.0 与 0.11.1 在 DeepSeek Harness 0.2.1-alpha.2 上同样受支持，本版本非强制升级。
• 纯 TypeScript 架构：优化 src/config.ts 中 Config 架构导出类型声明，消除 TS2742 类型不可便携警告，全库保持 100% 纯 TypeScript。
• 规范化命令行选项：更新各文档中的 CLI 命令，遵循 DeepSeek Harness 0.2.1-alpha.1 规范，统一将 --profile <name> 参数置于 add、remove、update 等子命令之前。

更新说明

• 安装命令：dsh plugin --profile web add dsh-kingdee@0.13.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin --profile web update dsh-kingdee；或执行 dsh plugin --profile web add dsh-kingdee@0.13.0 锁定版本。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。

验证

• pnpm run typecheck 零错误、pnpm run build 干净（tsc -p tsconfig.build.json 加 tsdown 客户端 bundle），15 项单元测试（pnpm test）在 DeepSeek Harness 0.2.1-alpha.2 上全部通过。
• node scripts/check-docs-language.ts 检查全部通过，零语言混淆或链接跳转错误。

---

Release notes — v0.13.0

English | Chinese

Release date: 2026-10-11

Nineteenth release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness. It is a DeepSeek Harness 0.2.1-alpha.2 alignment and display metadata release: includes native icon.svg vector artwork, bilingual display manifest resources (locale/en.json, locale/zh.json), self-contained prepare scripts, strict 100% pure TypeScript architecture, and updated --profile <name> CLI option placement. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Added

• Display metadata and icon. Bundled native icon.svg vector artwork and bilingual manifest resources (locale/en.json, locale/zh.json) conforming to DSH 0.2.1-alpha.2 display conventions for Plugin Manager. package.json exports ./locale/*.json, ./icon and declares top-level "icon": "./icon.svg".
• Self-contained prepare script. Configured "prepare": "tsc -p tsconfig.build.json && tsdown" in package.json to enable direct git installs without requiring a global pnpm binary.

Changed

• Harness alignment. Upgraded all development dependencies to DeepSeek Harness 0.2.1-alpha.2. @deepseek-ai/cordis remains ^4.0.4 and @deepseek-ai/schemastery remains ^3.18.4.
• Peer ranges compatibility. Maintained peer dependencies range >=0.1.7-alpha.2 <0.3.0, so dsh-kingdee@0.12.0 and dsh-kingdee@0.11.1 remain admitted on DeepSeek Harness 0.2.1-alpha.2 as well without requiring manual exemptions.
• Pure TypeScript architecture. Strengthened schema export typing in src/config.ts (export const Config: Schema<Config>) to eliminate TS2742 non-portable type warnings under pnpm virtual store layouts while ensuring strict 100% pure TypeScript compliance.
• CLI syntax documentation. Updated all guides to place --profile <name> before forwarded subcommands such as add, remove, and update.

Update notes

• Install: dsh plugin --profile web add dsh-kingdee@0.13.0 into a DSH profile, then enable the row.
• Update: run dsh plugin --profile web update dsh-kingdee, or dsh plugin --profile web add dsh-kingdee@0.13.0 to pin the version.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer.

Verification

• pnpm run typecheck clean, pnpm run build clean (tsc -p tsconfig.build.json plus the tsdown client bundle), and all 15 unit tests pass (pnpm test) against DeepSeek Harness 0.2.1-alpha.2.
• node scripts/check-docs-language.ts passing clean with zero findings.

dsh-kingdee v0.12.0

Release notes — v0.12.0

English | Chinese

Release date: 2026-09-29

Eighteenth release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness. It is a DeepSeek Harness 0.2.0-rc.2 alignment release: every @deepseek-ai/dsh-* devDependency moves to 0.2.0-rc.2, the lockfile is regenerated against that release, and the workspace supply-chain exemption is refreshed to the 0.2.0-rc.2 package set. The runtime sources, the configuration fields and the tool interface are untouched, so the plugin behaves exactly as v0.11.1. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Changed

• Harness alignment. Every @deepseek-ai/dsh-* devDependency moves from 0.2.0-rc.1 to 0.2.0-rc.2, and the lockfile is regenerated against 0.2.0-rc.2. @deepseek-ai/cordis stays ^4.0.4 and @deepseek-ai/schemastery stays ^3.18.4.
• Peer ranges are unchanged. The @deepseek-ai/dsh-credentials and @deepseek-ai/dsh-tools peers stay >=0.1.7-alpha.2 <0.3.0 — the widened range 0.11.0 introduced — so dsh-kingdee@0.11.1 is admitted on DeepSeek Harness 0.2.0-rc.2 as well, and this release is not a mandatory upgrade. It is the version verified against 0.2.0-rc.2 and aligned with that release's development dependencies.
• Supply-chain gate. The workspace file now exempts the 0.2.0-rc.2 package set from pnpm's minimum-release-age gate, which otherwise rejects DSH's continuously published prereleases.
• Source change. None. No file under src/, test/, scripts/, .github/, skills/, cordis.patch.yml or the build configuration changed, and no configuration field moved: the plugin behaves exactly as 0.11.1.

Update notes

• Install: dsh plugin add dsh-kingdee@0.12.0 into a DSH profile, then enable the row.
• Update: run dsh plugin update dsh-kingdee, or dsh plugin add dsh-kingdee@0.12.0 to pin the version. Since 0.11.1 keeps loading on 0.2.0-rc.2, updating the package is all this release asks for, and it can wait.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer. On DeepSeek Harness 0.2.0-rc.2 the older 0.10.0 is still refused at load, because its @deepseek-ai/dsh-* peers (^0.1.7-alpha.2) exclude 0.2.x.
• No configuration, API or tool change. The twelve configuration fields keep their names, values and defaults, and cordis.yml and cordis.patch.yml keep working unchanged. See USAGE.md and USAGE.zh.md.

Verification

• pnpm run typecheck clean, pnpm run build clean (tsc -p tsconfig.build.json plus the tsdown client bundle), and all 15 unit tests pass (pnpm test) against DeepSeek Harness 0.2.0-rc.2.
• The harness's own published evaluatePluginCompatibility / getDshRuntimeVersion from @deepseek-ai/dsh-app-boot@0.2.0-rc.2 report runtime 0.2.0-rc.2 and admit dsh-kingdee@0.12.0 on 0.2.0-rc.2, 0.2.0-rc.1, 0.2.0, 0.1.7-rc.2 and 0.1.7-alpha.2; they refuse dsh-kingdee@0.12.0 on 0.1.6-alpha.2, and the earlier dsh-kingdee@0.10.0 (^0.1.7-alpha.2) is still refused on 0.2.0-rc.2.
• Not verified: a live boot into a real 0.2.0-rc.2 profile (no dsh CLI exists on the verification machine), and no live Kingdee tenant.

---

发行说明 — v0.12.0

英文 | 中文

发行日期：2026-09-29

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布第十八版 v0.12.0。这是一个适配 DeepSeek Harness 0.2.0-rc.2 的版本：@deepseek-ai/dsh-* 的全部开发依赖升至 0.2.0-rc.2，锁文件按该版本重新生成，工作区的供应链豁免清单也刷新为 0.2.0-rc.2 的包集合。运行时源码、配置字段与工具接口均未改动，因此插件行为与 v0.11.1 完全一致。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

变更

• 宿主对齐：@deepseek-ai/dsh-* 的全部开发依赖由 0.2.0-rc.1 升至 0.2.0-rc.2，锁文件按 0.2.0-rc.2 重新生成。@deepseek-ai/cordis 保持 ^4.0.4、@deepseek-ai/schemastery 保持 ^3.18.4。
• peer 区间不变：@deepseek-ai/dsh-credentials 与 @deepseek-ai/dsh-tools 仍为 >=0.1.7-alpha.2 <0.3.0，即 0.11.0 放宽后的区间，因此 dsh-kingdee@0.11.1 在 DeepSeek Harness 0.2.0-rc.2 上同样被准入，本版不是强制升级。它是已针对 0.2.0-rc.2 完成验证、并对齐该版本开发依赖的版本。
• 供应链闸门：工作区文件现对 0.2.0-rc.2 的各包豁免 pnpm 的最小发布年龄闸门 —— 否则 DSH 持续发布的预发行版会被拦下。
• 源码改动：无。src/、test/、scripts/、.github/、skills/、cordis.patch.yml 与构建配置下均无文件改动，配置字段也没有任何迁移：插件行为与 0.11.1 完全一致。

更新说明

• 安装命令：dsh plugin add dsh-kingdee@0.12.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin update dsh-kingdee；或执行 dsh plugin add dsh-kingdee@0.12.0 锁定版本。由于 0.11.1 在 0.2.0-rc.2 上仍能加载，本版只要求更新包本身，且可以稍后再做。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。在 DeepSeek Harness 0.2.0-rc.2 上，较旧的 0.10.0 仍会在加载阶段被拒绝，因为它的 @deepseek-ai/dsh-* peer（^0.1.7-alpha.2）不含 0.2.x。
• 无配置、接口与工具变更。 十二个配置字段的名称、取值与默认值全部不变，cordis.yml 与 cordis.patch.yml 原样继续可用。详见 USAGE.zh.md 与 USAGE.md。

验证

• pnpm run typecheck 零错误、pnpm run build 干净（tsc -p tsconfig.build.json 加 tsdown 客户端 bundle），15 项单元测试（pnpm test）在 DeepSeek Harness 0.2.0-rc.2 上全部通过。
• 宿主自带的已发布实现 evaluatePluginCompatibility / getDshRuntimeVersion（来自 @deepseek-ai/dsh-app-boot@0.2.0-rc.2）报告运行时为 0.2.0-rc.2，在 0.2.0-rc.2、0.2.0-rc.1、0.2.0、0.1.7-rc.2、0.1.7-alpha.2 上均准入 dsh-kingdee@0.12.0；对 0.1.6-alpha.2 上的 0.12.0 则拒绝，而更早的 dsh-kingdee@0.10.0（^0.1.7-alpha.2）在 0.2.0-rc.2 上仍被拒绝。
• 未验证项：在真实 0.2.0-rc.2 profile 中的实际启动（验证机器上没有 dsh CLI），以及未做真实金蝶账套联调。

dsh-kingdee v0.11.1

Release notes — v0.11.1

English | Chinese

Release date: 2026-09-28

Seventeenth release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness. It is a documentation-only release: the sources, the manifest peers and the configuration are identical to v0.11.0, so the plugin behaves exactly as before. It closes the defects a full bilingual proofread found, and it keeps the DeepSeek Harness 0.2.0-rc.1 alignment introduced in 0.11.0. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Fixed

• The English 0.7.0 changelog entry was thinner than the Chinese one. Added the third-party LoginByAppSecret login (app mode), the removal of the fabricated KDAuthentication header together with the new userNameRef requirement, and the login-response fix (parseLoginOutcome) that had made authentication fail against a real tenant.
• The Chinese 0.6.1 entry carried a category heading that did not match the English one, plus a vague item with no English counterpart; the heading now matches the English ### Removed and the filler item is gone.
• One example, two placeholder hosts. The configuration guide used https://erp.mycompany.com/K3Cloud where every other guide uses https://erp.example.com/K3Cloud; both languages now use erp.example.com.
• The Chinese configuration guide stated the credential-seam contract as prose where English lists two bullets; the Chinese side now carries the same two bullets.
• The Chinese install guide omitted 172.16.0.0/12 from the blocked private ranges listed in its prerequisites.
• Chinese guide section numbers now match the English ones. The install and uninstall guides numbered their top-level sections with Chinese numerals where English uses 1.–5.; both languages now number them the same way, so every pair lines up section for section.

Update notes

• Install: dsh plugin add dsh-kingdee@0.11.1 into a DSH profile, then enable the row.
• Update: run dsh plugin update dsh-kingdee, or dsh plugin add dsh-kingdee@0.11.1 to pin the version. No action is required beyond updating the package: nothing but documentation changed.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer. On DeepSeek Harness 0.2.0-rc.1 the older 0.10.0 is still refused at load, because its @deepseek-ai/dsh-* peers exclude 0.2.x.
• No configuration, API or tool change. The twelve configuration fields keep their names, values and defaults, and cordis.yml and cordis.patch.yml keep working unchanged. See USAGE.md and USAGE.zh.md.

Verification

• pnpm run typecheck clean, pnpm run build clean (tsc -p tsconfig.build.json plus the tsdown client bundle), and all 15 unit tests pass (pnpm test) against DeepSeek Harness 0.2.0-rc.1.
• node scripts/check-docs-language.ts green, plus two mechanical proofreading passes across every bilingual pair: structure and code-fence parity, a mojibake and control-character scan, newest-first changelog ordering with complete link references, and per-section bullet correspondence.
• The harness's own published evaluatePluginCompatibility / getDshRuntimeVersion from @deepseek-ai/dsh-app-boot@0.2.0-rc.1 reports runtime 0.2.0-rc.1 and admits dsh-kingdee@0.11.1 on 0.2.0-rc.1, 0.2.0, 0.1.7-rc.2 and 0.1.7-alpha.2; it refuses dsh-kingdee@0.10.0 on 0.2.0-rc.1 and dsh-kingdee@0.11.1 on 0.1.6-alpha.2.
• The packed 0.11.1 tarball carries the built lib/, cordis.patch.yml, the skills/kingdee-bos skill and the bilingual guides, and its manifest is the one that gate admits above.
• Not verified: a live boot into a real 0.2.0-rc.1 profile (no dsh CLI exists on the verification machine), and no live Kingdee tenant.

---

发行说明 — v0.11.1

英文 | 中文

发行日期：2026-09-28

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布第十七版 v0.11.1。这是一个纯文档修正版本：源码、清单 peer 与配置均与 v0.11.0 完全一致，插件行为不变。本版关闭了一轮完整双语校对发现的缺陷，并保留 0.11.0 引入的 DeepSeek Harness 0.2.0-rc.1 适配。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

修复

• 英文 0.7.0 条目比中文单薄。 补齐第三方 LoginByAppSecret 登录（app 模式）、取消伪造 KDAuthentication 请求头并新增 userNameRef 必填要求，以及曾导致真实账套认证失败的登录响应修复（parseLoginOutcome）。
• 中文 0.6.1 条目有一个与英文分类不一致的标题，以及一条没有对应内容的空泛条目；标题现为 移除，填充条目已删除。
• 同一示例出现两个占位域名。 配置指南用 https://erp.mycompany.com/K3Cloud，而其他指南统一用 https://erp.example.com/K3Cloud；两侧现统一为 erp.example.com。
• 中文配置指南把凭据缝契约写成散文，而英文为两条列表；中文侧现改为相同的两条列表。
• 中文安装指南漏列 172.16.0.0/12 这一被前置条件中列举的私网网段。
• 中文指南的章节编号现与英文一致。 安装与卸载指南的顶层章节原用中文数字，而英文用 1.–5.；两侧现统一编号，可逐节对齐。

更新说明

• 安装命令：dsh plugin add dsh-kingdee@0.11.1 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin update dsh-kingdee；或执行 dsh plugin add dsh-kingdee@0.11.1 锁定版本。除更新包之外无需任何操作：本次只有文档变化。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。在 DeepSeek Harness 0.2.0-rc.1 上，较旧的 0.10.0 仍会在加载阶段被拒绝，因为它的 @deepseek-ai/dsh-* peer 区间不含 0.2.x。
• 无配置、接口与工具变更。 十二个配置字段的名称、取值与默认值全部不变，cordis.yml 与 cordis.patch.yml 原样继续可用。详见 USAGE.zh.md 与 USAGE.md。

验证

• pnpm run typecheck 零错误、pnpm run build 干净（tsc -p tsconfig.build.json 加 tsdown 客户端 bundle），15 项单元测试（pnpm test）在 DeepSeek Harness 0.2.0-rc.1 上全部通过。
• node scripts/check-docs-language.ts 通过；另对全部双语文档做了两遍机械校对（结构与代码围栏对齐、乱码与控制字符扫描、更新日志由新到旧排序且链接引用完整、逐节条目对应）。
• 宿主自带的已发布实现 evaluatePluginCompatibility / getDshRuntimeVersion（来自 @deepseek-ai/dsh-app-boot@0.2.0-rc.1）报告运行时为 0.2.0-rc.1，在 0.2.0-rc.1、0.2.0、0.1.7-rc.2、0.1.7-alpha.2 上均准入 dsh-kingdee@0.11.1；并在 0.2.0-rc.1 上拒绝 dsh-kingdee@0.10.0，在 0.1.6-alpha.2 上拒绝 dsh-kingdee@0.11.1。
• 实际打包的 0.11.1 压缩包含构建产物 lib/、cordis.patch.yml、skills/kingdee-bos 技能与中英双语指南，其清单即上述闸门所准入的那一份。
• 未验证项：在真实 0.2.0-rc.1 profile 中的实际启动（验证机器上没有 dsh CLI），以及未做真实金蝶账套联调。

dsh-kingdee v0.11.0

Release notes — v0.11.0

English | Chinese

Release date: 2026-09-28

Sixteenth release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness. It adapts the plugin to DeepSeek Harness 0.2.0-rc.1 by widening its @deepseek-ai/dsh-credentials and @deepseek-ai/dsh-tools peers to >=0.1.7-alpha.2 <0.3.0, because 0.2.0-rc.1 introduced a hard peer-compatibility gate that refuses a plugin row whose DSH peers do not match the single running runtime version. The previous 0.10.0 declared ^0.1.7-alpha.2, which excludes 0.2.x, so it is refused on 0.2.0-rc.1 and must be upgraded. No runtime code, no configuration and no tool surface changed, so the plugin behaves exactly as v0.10.0. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Changed

• Harness alignment. Development dependencies move to DeepSeek Harness 0.2.0-rc.1, and this release is verified against it; @deepseek-ai/cordis stays ^4.0.4 and @deepseek-ai/schemastery stays ^3.18.4.
• Peer ranges widen to >=0.1.7-alpha.2 <0.3.0. DeepSeek Harness 0.2.0-rc.1 checks every @deepseek-ai/dsh / @deepseek-ai/dsh-* peer entry against the single running runtime version before a plugin row loads, with prereleases participating in range matching, and refuses an incompatible row (an incompatible bundle is skipped). The credential and tools peers now admit 0.1.7-alpha.2 through 0.2.x, so the plugin loads on both release lines, and it is still refused on 0.1.6-alpha.2. engines.dsh is not what the gate reads.
• Supply-chain gate. The workspace file now exempts the 0.2.0-rc.1 package set from pnpm's minimum-release-age gate, which otherwise rejects DSH's continuously published prereleases, and the lockfile was regenerated against 0.2.0-rc.1.
• Source change. None. No file under src/, test/, scripts/, .github/, skills/, cordis.patch.yml or the build configuration changed, and no configuration field moved.

Fixed

• 0.10.0 was refused at load on DeepSeek Harness 0.2.0-rc.1. Its declared @deepseek-ai/dsh-* peers excluded 0.2.x, so the new gate refused the row. Widening the ranges admits the plugin on 0.2.0-rc.1 with no exemption, so users on 0.2.0-rc.1 must upgrade to 0.11.0. dsh plugin allow-version <package@version> --dsh-version <runtime> --accept-risk (or the plugin manager) remains available only as an exact-version risk acknowledgement recorded in the profile's compatibility.json: it is not a compatibility fix, and neither a plugin upgrade nor a harness upgrade inherits the grant.

Update notes

• Install: dsh plugin add dsh-kingdee@0.11.0 into a DSH profile, then enable the row.
• Update: run dsh plugin update dsh-kingdee, or dsh plugin add dsh-kingdee@0.11.0 to pin the version. On DeepSeek Harness 0.2.0-rc.1 you must move off 0.10.0: its @deepseek-ai/dsh-* peers exclude 0.2.x, so the harness refuses that row at load.
• Requirements: harness >=0.1.7-alpha.2 <0.3.0, Node 22 or newer.
• No configuration, API or tool change. The twelve configuration fields keep their names, values and defaults, and cordis.yml and cordis.patch.yml keep working unchanged. See USAGE.md and USAGE.zh.md.

Verification

• Type check and build are clean (pnpm run typecheck, pnpm run build — tsc -p tsconfig.build.json plus the tsdown client bundle), and all 15 unit tests pass (pnpm test) against DeepSeek Harness 0.2.0-rc.1.
• pnpm install passes pnpm's supply-chain (minimum-release-age) gate.
• The harness's own published evaluatePluginCompatibility / getDshRuntimeVersion from @deepseek-ai/dsh-app-boot@0.2.0-rc.1 reports runtime 0.2.0-rc.1, admits dsh-kingdee@0.11.0 on 0.2.0-rc.1, 0.2.0, 0.1.7-rc.2 and 0.1.7-alpha.2, and refuses dsh-kingdee@0.10.0 on 0.2.0-rc.1 with unsatisfied peers @deepseek-ai/dsh-credentials and @deepseek-ai/dsh-tools (^0.1.7-alpha.2). It also refuses 0.11.0 on 0.1.6-alpha.2.
• The packed 0.11.0 tarball carries the built lib/, cordis.patch.yml, the skills/kingdee-bos skill and the bilingual guides, and its manifest is the one that gate admits above.
• Not verified: a live boot into a real 0.2.0-rc.1 profile (no dsh CLI exists on the verification machine), and no live Kingdee tenant.

---

发行说明 — v0.11.0

英文 | 中文

发行日期：2026-09-28

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布第十六版 v0.11.0。本版通过把 @deepseek-ai/dsh-credentials 与 @deepseek-ai/dsh-tools 两个 peer 区间放宽为 >=0.1.7-alpha.2 <0.3.0，完成对 DeepSeek Harness 0.2.0-rc.1 的适配：0.2.0-rc.1 引入了硬性 peer 兼容性闸门，凡 DSH peer 与唯一运行时不匹配的插件行都会被拒绝。此前的 0.10.0 声明的是 ^0.1.7-alpha.2，该区间不含 0.2.x，因此在 0.2.0-rc.1 上会被拒绝，必须升级。本版不改运行时逻辑、不改配置、不改工具接口，行为与 v0.10.0 完全一致。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

变更

• 宿主对齐：开发依赖升级到 DeepSeek Harness 0.2.0-rc.1，并已针对该版本完成验证；@deepseek-ai/cordis 保持 ^4.0.4、@deepseek-ai/schemastery 保持 ^3.18.4。
• peer 区间放宽为 >=0.1.7-alpha.2 <0.3.0：DeepSeek Harness 0.2.0-rc.1 会在插件行加载之前，用唯一的运行时版本校验每一处名为 @deepseek-ai/dsh / @deepseek-ai/dsh-* 的 peer 依赖，预发行版参与区间匹配；不兼容的行会被拒绝（不兼容的 bundle 会被跳过）。凭据与工具两个 peer 现可准入 0.1.7-alpha.2 至 0.2.x，因此插件在两条发布线上均可加载，但在 0.1.6-alpha.2 上仍会被拒绝。闸门读取的不是 engines.dsh。
• 供应链闸门：工作区文件现对 0.2.0-rc.1 的各包豁免 pnpm 的最小发布年龄闸门 —— 否则 DSH 持续发布的预发行版会被拦下；锁文件已按 0.2.0-rc.1 重新生成。
• 源码改动：无。src/、test/、scripts/、.github/、skills/、cordis.patch.yml 与构建配置下均无文件改动，配置字段也没有任何迁移。

修复

• 0.10.0 在 DeepSeek Harness 0.2.0-rc.1 上会在加载阶段被拒绝：它声明的 @deepseek-ai/dsh-* peer 区间不含 0.2.x，因此被新闸门拒绝。放宽区间后，插件无需豁免即可在 0.2.0-rc.1 上准入，因此 0.2.0-rc.1 上的用户必须升级到 0.11.0。dsh plugin allow-version <package@version> --dsh-version <runtime> --accept-risk（或插件管理器）仅作为记录在 profile compatibility.json 中的确切版本风险确认而存在：它不是兼容性修复，插件升级与宿主升级也都不会继承该授权。

更新说明

• 安装命令：dsh plugin add dsh-kingdee@0.11.0 装入 DSH profile，然后启用该行。
• 升级命令：dsh plugin update dsh-kingdee；或执行 dsh plugin add dsh-kingdee@0.11.0 锁定版本。在 DeepSeek Harness 0.2.0-rc.1 上必须离开 0.10.0：其 @deepseek-ai/dsh-* peer 区间不含 0.2.x，宿主会在加载阶段拒绝该行。
• 环境要求：harness >=0.1.7-alpha.2 <0.3.0，Node 22 或更新。
• 无配置、接口与工具变更。 十二个配置字段的名称、取值与默认值全部不变，cordis.yml 与 cordis.patch.yml 原样继续可用。详见 USAGE.zh.md 与 USAGE.md。

验证

• 类型检查与构建均干净（pnpm run typecheck、pnpm run build —— tsc -p tsconfig.build.json 加 tsdown 客户端 bundle），15 项单元测试（pnpm test）在 DeepSeek Harness 0.2.0-rc.1 上全部通过。
• pnpm install 通过 pnpm 的供应链（最小发布年龄）闸门。
• 宿主自带的已发布实现 evaluatePluginCompatibility / getDshRuntimeVersion（来自 @deepseek-ai/dsh-app-boot@0.2.0-rc.1）报告运行时为 0.2.0-rc.1，在 0.2.0-rc.1、0.2.0、0.1.7-rc.2、0.1.7-alpha.2 上均准入 dsh-kingdee@0.11.0，并在 0.2.0-rc.1 上以 @deepseek-ai/dsh-credentials、@deepseek-ai/dsh-tools（^0.1.7-alpha.2）peer 不满足为由拒绝 dsh-kingdee@0.10.0；对 0.1.6-alpha.2 上的 0.11.0 同样拒绝。
• 实际打包的 0.11.0 压缩包含构建产物 lib/、cordis.patch.yml、skills/kingdee-bos 技能与中英双语指南，其清单即上述闸门所准入的那一份。
• 未验证项：在真实 0.2.0-rc.1 profile 中的实际启动（验证机器上没有 dsh CLI），以及未做真实金蝶账套联调。

dsh-kingdee v0.10.0

Release notes — v0.10.0

English | Chinese

Release date: 2026-09-24

Fifteenth release of dsh-kingdee, the Kingdee Cloud Starry Sky secondary-development plugin for DeepSeek Harness. It aligns the plugin with DeepSeek Harness 0.1.7-rc.2 and changes no runtime code, no configuration and no tool surface, so the plugin behaves exactly as v0.9.1. Tenant compatibility is unchanged: Kingdee Cloud Starry Sky V9.1 Enterprise Edition, backward-compatible with V9.0 / V8.x, and no live-tenant verification was performed.

Changed

• Harness alignment. Development dependencies move to DeepSeek Harness 0.1.7-rc.2, and this release is verified against it.
• Peer ranges are unchanged. They stay ^0.1.7-alpha.2, the release line that introduced volatile config, so the plugin still installs on every 0.1.7 prerelease from alpha.2 through rc.2. The harness engine range and the Node engine range are unchanged.
• Seam audit. Every interface this plugin uses is identical in the rc.1 and rc.2 sources: the configuration schema the Host reads, the per-entry settings form, tool registration, the credential resolver, the configuration form the browser half reads, and the locale and slot registries.
• Source change. None. The only changed file in the packages this plugin consumes adds two optional fields to a type this plugin does not use.
• Supply-chain gate. The workspace file now exempts the rc.2 packages from pnpm's minimum-release-age gate, which otherwise rejects DSH's continuously published prereleases.

Fixed

• The Chinese 0.3.0 changelog entry now covers that release at the same depth as English, and the Chinese documentation list links CHANGELOG.zh.md rather than the English changelog. No runtime, configuration or tool-surface change.

Update notes

• Update: run dsh plugin update dsh-kingdee, or dsh plugin add dsh-kingdee@0.10.0 to pin the version.
• Requirements: harness ^0.1.7-alpha.2, Node 22 or newer.
• No configuration, API or tool change. The twelve configuration fields keep their names, values and defaults, and cordis.yml and cordis.patch.yml keep working unchanged. See USAGE.md and USAGE.zh.md.

Verification

• Type check and build are clean, and all 15 unit tests pass against DeepSeek Harness 0.1.7-rc.2.
• A frozen-lockfile install passes pnpm's supply-chain gate.
• The declared peers pass the host's own compatibility check on rc.2, rc.1 and alpha.2: admitted, no exemption required.
• The shipped 0.10.0 tarball installs into a real 0.1.7-rc.2 profile and composes as a dsh-kingdee layer under the row id kingdee, with every schema default applied.

---

发行说明 — v0.10.0

英文 | 中文

发行日期：2026-09-24

dsh-kingdee（面向 DeepSeek Harness 的金蝶云星空二次开发插件）发布第十五版 v0.10.0。本版完成与 DeepSeek Harness 0.1.7-rc.2 的对齐，不改运行时逻辑、不改配置、不改工具接口，行为与 v0.9.1 完全一致。账套兼容性保持不变：金蝶云·星空 V9.1 企业版，向下兼容 V9.0 / V8.x；未进行真实账套联调验证。

变更

• 宿主对齐：开发依赖升级到 DeepSeek Harness 0.1.7-rc.2，并已针对该版本完成验证。
• peer 区间不变：仍为 ^0.1.7-alpha.2，即引入易变配置的那条发布线，因此插件在 0.1.7-alpha.2 至 0.1.7-rc.2 的每一个预发行版上仍可安装。宿主引擎区间与 Node 引擎区间均未改动。
• 接缝核对：本插件使用的全部接口在 rc.1 与 rc.2 源码中完全一致——Host 读取的配置 schema、按条目渲染的设置表单、工具注册、凭据解析，以及浏览器半端读取的配置表单、语言与槽位注册表。
• 源码改动：无。本插件所消费的包中唯一变动的文件，只是给它并不使用的某个类型加了两个可选字段。
• 供应链闸门：工作区文件现对 rc.2 的各包豁免 pnpm 的最小发布年龄闸门，否则 DSH 持续发布的预发行版会被拦下。

修复

• 中文更新日志的 0.3.0 条目已补齐到与英文同等的详略程度，中文文档列表也改为指向 CHANGELOG.zh.md 而非英文更新日志。不涉及运行时逻辑、配置或工具接口变更。

更新说明

• 升级命令：dsh plugin update dsh-kingdee；或执行 dsh plugin add dsh-kingdee@0.10.0 锁定版本。
• 环境要求：harness ^0.1.7-alpha.2，Node 22 或更新。
• 无配置、接口与工具变更。 十二个配置字段的名称、取值与默认值全部不变，cordis.yml 与 cordis.patch.yml 原样继续可用。详见 USAGE.zh.md 与 USAGE.md。

验证

• 类型检查与构建均干净，15 项单元测试在 DeepSeek Harness 0.1.7-rc.2 上全部通过。
• 冻结锁文件安装通过 pnpm 的供应链策略校验。
• 声明的 peer 依赖经宿主自带的兼容性校验在 rc.2、rc.1、alpha.2 上均准入，无需豁免。
• 实际发布的 0.10.0 压缩包可装入真实的 0.1.7-rc.2 profile，并以行 id kingdee 组合出 dsh-kingdee 图层，各项 schema 默认值均已生效。