feat(dsh): 适配 DSH 0.2.0-rc.1（单线支持）+ v0.24.0

支持线从 ^0.1.7-rc.1 整体前移到 ^0.2.0-rc.1；0.1.7 线（含 npm latest 的
0.1.7-rc.2）停留在 v0.23.0。适配前实测确认这是纯增量，故本版无运行时兼容分支。

必改项（否则装不上/不加载）
- 14 条 DSH peer → ^0.2.0-rc.1。实测 caret 跨 minor 不成立：`^0.1.7-rc.1`
  展开为 >=0.1.7-rc.1 <0.2.0-0，对 0.2.0-rc.1 判定 false（includePrerelease
  也救不了）。判别性验证：把 peer 回退成 ^0.1.7-rc.1 后，在 0.2.0-rc.1 宿主上
  `dsh plugin add` 直接拒绝并回滚包树——
  "installation rejected: Plugin dsh-better-sidebar@0.24.0 is incompatible with
   dsh 0.2.0-rc.1: peerDependencies {…^0.1.7-rc.1…}"；恢复 ^0.2.0-rc.1 后安装通过
- 28 个 @deepseek-ai/* devDependencies 精确钉 0.2.0-rc.1（cordis 4.0.4 /
  cordis-plugin-group 1.0.4 / cordis-plugin-include 1.0.9 不变）
- 新增 @deepseek-ai/dsh-util-code-language@0.2.0-rc.1：0.2.0 的 ui-primitives
  产物裸 import 它（0.1.7 的产物同样 import，只是旧树里恰好被传递提供），
  不补则所有加载 ui-primitives 的 20 个 spec 在收集期失败

实测证据（写进 docs/plans/2026-09-28-dsh-0.2.0-rc.1-adaptation.md）
- 本插件消费的 19 个宿主包零值导出删除（对比 export {} / exports.x=）
- 类型面仅 3 处且全为增量：ui-primitives（DisclosureRow/TextShimmer/Tooltip
  新增可选 prop、overlay 顶部内距）、dsh-session（新增 ToolCallRecovery）、
  dsh-api-remotes（新增 product-analytics remote）
- 会话格式仍 v4、SUBAGENT_DESCRIPTOR_VERSION 仍 3、dsh/lib/bin.js 与
  dsh-client-modules 运行时逐字节相同、web profile 客户端 inject 列表相同、
  ui-primitives 裸 import 集合不变、agent-team 四包类型逐字相同
- 宿主 web profile：新增 desktop-only product-analytics/telemetry（web 上
  disabled）；time-context/schedule/ui-schedule（本就 disabled）移入可选
  dsh-experimental-schedule-bundle；插件不依赖宿主 schedule

其余同步
- CI 与挂载 lane 钉 @deepseek-ai/dsh@0.2.0-rc.1（scripts/e2e-common.sh 的
  DSH_NPX_SPEC/DSH_EXPECT_VERSION、ci.yml），注释记下「0.2.0 首个候选版只挂
  next」与「caret 跨 minor 必失效」两条教训
- tests/market-manifest.spec.ts 的 peer 形状断言钉当前基线 tuple
- dsh.plugin.json engines.dsh → >=0.2.0-rc.1；SIDEBAR_SERVICE_VERSION → 0.24.0
- README/README_EN、CHANGELOG/CHANGELOG_EN、AGENTS.md（§2 钉版句 + §3 改为
  「DSH 版本适配要点」并新增 §3.0 当前基线，0.1.7 内容降为历史分节）、
  docs/external-plugin-guide.md 全部同步

验证：pnpm peers check 仅剩上游 better-locale 的 5 条 unmet（非本插件 peer）；
typecheck / lint / test（136 文件 1484 通过 9 跳过）/ build 全绿；
DSH_CMD='npx -y --package @deepseek-ai/dsh@0.2.0-rc.1 dsh' pnpm test:mount = 7/7；
pnpm test:mount:aggregate 通过（聚合双挂载退让）

tests/market-manifest.spec.ts

@@ -123,15 +123,25 @@ describe('DSH community-market manifest compatibility', () => {
     // and DISABLES the whole profile row when it fails — one stderr line in a
     // log nobody reads, no dialog, and `peerDependenciesMeta.optional` grants
     // no exemption. An exact pin (the style devDependencies use) or a
-    // comparator carrying no prerelease (`^0.1.7`) would therefore make the
+    // comparator carrying no prerelease (`^0.2.0`) would therefore make the
     // plugin silently stop loading, so the published ranges must stay carets
     // on the baseline tuple. `pnpm peers check` cannot see this: it validates
     // the resolved dev tree, not the range shape a host will read.
+    //
+    // A caret NEVER spans a minor bump, even with `includePrerelease` on:
+    // `^0.1.7-rc.1` expands to `>=0.1.7-rc.1 <0.2.0-0`, so it rejects
+    // `0.2.0-rc.1` (measured: false) and a 0.2.0 host would disable the row
+    // instead of loading the plugin. The support line therefore moves WITH the
+    // baseline and is never widened to "cover both lines". (An explicit
+    // comparator behaves differently — `>=0.1.1-rc.2 <0.2.0` does admit
+    // `0.2.0-rc.1`, because only carets get the `-0` upper bound — which is why
+    // the assertion below pins the baseline tuple instead of accepting any
+    // caret that looks plausible.)
     const peers = pkg.peerDependencies ?? {}
     const dshPeers = Object.keys(peers).filter(name => name === '@deepseek-ai/dsh' || name.startsWith('@deepseek-ai/dsh-'))
     expect(dshPeers.length).toBeGreaterThan(10)
     for (const name of dshPeers) {
-      expect(peers[name], name).toMatch(/^\^0\.1\.7-[a-z0-9.]+$/)
+      expect(peers[name], name).toMatch(/^\^0\.2\.0-[a-z0-9.]+$/)
     }
   })
 })