Skip to content

v0.11.1 — 收紧 DSH 版本范围 / Narrow the DSH range

Choose a tag to compare

View all tags
@Dclef Dclef released this 17 Oct 15:57
· 13 commits to main since this release
v0.11.1
070441a

中文

0.11.1 收紧 DSH 版本声明，并修正文档里对两种运行形态的描述。

  • engines.dsh：^0.2.0-rc.1 → >=0.2.1-rc.2 <0.3.0-0。0.11 采用的外部子智能体契约（startActivation、子会话 id 必须未被宿主占用、External 行由宿主写入）只在 DSH 0.2.1 中存在，声明现在只覆盖实际实现并验证过的范围。
  • 为什么上界是 <0.3.0-0：DSH 以 includePrerelease: true 判定兼容性，普通的 <0.3.0 仍会匹配 0.3.0-rc.1；-0 让 0.3.0 的所有预发布一起被排除。
  • 安装源：npm 公共源上的 dsh-cursor-dev@0.11.1，或 Git 来源 git+https://github.com/Dclef/dsh-cursor-dev.git。
  • 文档：README / INSTALL 与包描述现在明确区分 cursor_code（创建可点开的镜像子会话）与 cursor_subagent（显示为宿主写入的 External 记录）。
  • 市场卡片：dshmarket 从 npm manifest 读取版本与 engines.dsh；awesome 目录下一次 nightly 探测后，卡片会显示 0.11.1 与 DSH >=0.2.1-rc.2 <0.3.0-0。

English

0.11.1 narrows the declared DSH range and fixes the docs describing the two run shapes.

  • engines.dsh: ^0.2.0-rc.1 → >=0.2.1-rc.2 <0.3.0-0. The external-subagent contract used by 0.11 (startActivation, a child id the host has not registered yet, the External row written by the host) only exists in DSH 0.2.1, so the declaration now covers exactly the range this code implements and tests.
  • Why the upper bound is <0.3.0-0: DSH evaluates compatibility with includePrerelease: true, so a plain <0.3.0 still matches 0.3.0-rc.1; -0 excludes every 0.3.0 prerelease as well.
  • Install sources: dsh-cursor-dev@0.11.1 from the public npm registry, or the Git source git+https://github.com/Dclef/dsh-cursor-dev.git.
  • Docs: README / INSTALL and the package description now spell out cursor_code (creates the clickable mirrored child) versus cursor_subagent (appears as the host-written External row).
  • Market card: dshmarket reads the version and engines.dsh from the npm manifest; after the awesome catalog's next nightly probe the card shows 0.11.1 and DSH >=0.2.1-rc.2 <0.3.0-0.
Assets 3
Loading