v0.1.1

v0.1.1 — Install fix

Fixed

npm install dsh-filesnap and dsh plugin add failed on 0.1.0 with ERESOLVE
against every harness package:

Could not resolve dependency:
peer @deepseek-ai/dsh-llm@">=0.0.1-rc.1" from dsh-filesnap@0.1.0

The ranges were written to mean "any published version". They do not. A range
anchored on a prerelease only matches prereleases of the same x.y.z — so
>=0.0.1-rc.1 admitted 0.0.1-rc.* and any stable release, but not 0.1.0-rc.8,
which is what the harness actually ships. (* and >=0.0.0-0 are no better: neither
matches a prerelease at all.)

Each peer is now >=0.0.1-rc.1 || >=0.1.0-rc.0, which names both prerelease lines
explicitly.

No functional change. If 0.1.0 installed for you, nothing here affects you.

Also

Publishing is gated on a clean typecheck, the full test suite, and a build of both
faces — lib/ is gitignored and is the entire payload, so a release cannot ship a tree
that was never built, or a package missing its browser half. Releases now go out
through npm trusted publishing (OIDC), so there is no long-lived registry token in this
repository.

---

修复

0.1.0 上 npm install dsh-filesnap 和 dsh plugin add 会对每个 harness 包报
ERESOLVE:

Could not resolve dependency:
peer @deepseek-ai/dsh-llm@">=0.0.1-rc.1" from dsh-filesnap@0.1.0

那些范围本意是"任何已发布的版本"。但一个锚定在预发布版上的范围,只匹配同一个
x.y.z 的预发布版 —— 所以 >=0.0.1-rc.1 接受 0.0.1-rc.* 和任何正式版,却不接受
0.1.0-rc.8,而后者正是 harness 实际发布的。(* 和 >=0.0.0-0 也救不了:它们根本
不匹配任何预发布版。)

现在每个 peer 都是 >=0.0.1-rc.1 || >=0.1.0-rc.0,把两条预发布线都写明。

功能没有变化。如果 0.1.0 在你那儿装得上,这个版本与你无关。

另外

发布现在被三道门卡着:类型检查、完整测试、以及两边产物的构建 —— lib/ 在
gitignore 里、又是全部载荷,所以一次发布不可能带上从没构建过的代码,也不可能少了浏览器
那一半。发布改走 npm trusted publishing(OIDC),仓库里不再有长期有效的 registry
token。
Full Changelog: https://github.com/extracurricular-ai/dsh-filesnap/commits/v0.1.1