fix: declare DSH 0.1.5 peer compatibility

[prgrmrwy]

Summary

The current main / v0.9.3 already contains the runtime fixes for the DSH 0.1.5 line, but the shared DSH peer ranges still stop at ^0.1.2-alpha.1.

This PR only cleans up the compatibility declaration and documentation:

• add ^0.1.3-alpha.1 and ^0.1.5-alpha.1 to the dsh-attachment, dsh-home-paths, dsh-llm, dsh-tools, and dsh-web peer ranges;
• document the supported DSH lines in English and Chinese;
• deliberately leave 0.1.6-alpha out until it is separately verified.

The 0.1.5-alpha.1 anchor covers later 0.1.5-alpha, 0.1.5-rc, and stable 0.1.5 versions under npm semver prerelease rules, including 0.1.5-rc.2.

Rebased onto current main

This was opened against cc96a4b; the base has since moved to cf2a431 (v0.9.3), which changed the same three files, so the branch has been rebased on top of it.

That release also added a new @deepseek-ai/dsh-web peer (from the Codex web-search work) carrying the same narrow range. It is included here — otherwise the declared 0.1.5 compatibility would still be incomplete for that peer, since ^0.1.2-alpha.1 cannot match the 0.1.5-rc.2 prerelease.

Why this is metadata-only

The runtime support is already present on main:

• e8d9efa (released in v0.9.0) moved the auth calls to exact /api Fetch routes because connection.rpc.handle() cannot mount the channel on DSH 0.1.5;
• e8cdd64 / merged PR fix(client): follow the 0.1.5 command description resolver #75 changed the /fast command description to the 0.1.5 resolver shape.

This PR does not change runtime code or claim support for the unverified 0.1.6-alpha line.

Verification

Re-run on the rebased head (9b2331c):

• pnpm install --frozen-lockfile
• pnpm run build
• pnpm test — 493 tests, 486 passed, 7 skipped, 0 failed
• git diff --check
• checked with node-semver that the new ranges accept the published 0.1.5-alpha.1 / .2, 0.1.5-rc.1 / .2, and stable 0.1.5, while still accepting every previously supported version (0.1.1-rc.2, 0.1.2-alpha.1 / .3, 0.1.2-rc.1) and still excluding 0.1.6-alpha.1 / .2.

Fixes the stale peer warning without changing the package's runtime behavior.

[prgrmrwy]

@V1ki 老哥辛苦空了帮看下

[V1ki]

已合并，感谢 @prgrmrwy 的贡献！

peer 范围的改动我本地用 node-semver 核对过：0.1.3-alpha.2、0.1.5-alpha.x、0.1.5-rc.1 到 rc.3 都能匹配，0.1.6-alpha 之后仍被排除，和描述一致。rebase 到 v0.9.3 也很省心，辛苦了。

---

Merged, thanks @prgrmrwy for the contribution!

I double-checked the new peer ranges with node-semver: 0.1.3-alpha.2, 0.1.5-alpha.x and 0.1.5-rc.1 through rc.3 all match, while 0.1.6-alpha and later stay excluded, exactly as described. The rebase onto v0.9.3 made this easy to review. Much appreciated!