chore(compat): widen @deepseek-ai peer ranges for the 0.1.1 rc train

[nanami-0713]

Problem

Under strict semver, a prerelease version only satisfies a range when some comparator shares its exact major.minor.patch tuple. The current peer ranges (^0.1.0-rc.8) therefore do not match core 0.1.1-rc.1, which surfaces as unmet-peer diagnostics in marketplace/health checks even though the plugin runs fine.

Change

• Widen every @deepseek-ai/dsh-* peer/dev range to ^0.1.0-rc.8 || >=0.1.1-rc.0 <0.2.0:
  • keeps the declared API floor (rc.8)
  • matches the whole 0.1.1 rc train and every future 0.1.x stable
  • still excludes 0.2.0
• pnpm-lock.yaml regenerated (specifier lines only; resolved versions unchanged).

Verification

• semver.satisfies('0.1.1-rc.1', range) → true (strict)
• Plugin loads and renders cleanly on a live 0.1.1-rc.1 profile (all client bundles mount, zero console errors).

[taekchef]

@nanami-0713 感谢这份 PR 🙏 分析完全正确:strict semver 下 prerelease 只在范围存在相同 major.minor.patch 元组的比较子时才满足范围,^0.1.0-rc.8 确实匹配不到 0.1.1-rc.1。^0.1.0-rc.8 || >=0.1.1-rc.0 <0.2.0 这个写法同时保住了 rc.8 API 下限、整个 0.1.1-rc 列车和后续 0.1.x 稳定版,又排除 0.2.0,是干净的做法。

我代跑了两个小操作:① 你的首次 PR 触发的 CI 需要维护者批准,我已批准并跑完——双矩阵(Node 22/24)全绿,包括 lib 一致性硬门与 smoke e2e;② 按仓库惯例在 [Unreleased] 兼容性 段补了一条 CHANGELOG 说明(已推到你的分支,commit 881fcda)。

CI 重跑转绿后我就合并,感谢贡献 ✨