release: validate DSH 0.1.1 compatibility

[lonelymoon87]

Summary

• upgrade development fixtures to DSH 0.1.1-rc.1
• test packed installs against rc.8, latest, and next
• document local index, optional embedding data flow, and v0.1.3 compatibility
• prepare the public npm package metadata

Validation

• corepack pnpm@11.7.0 run check
• clean profile installs with @deepseek-ai/dsh@0.1.0-rc.8, @latest, and @next

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f40d5b1387

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Include the tested 0.1.1 prerelease in the peer ranges

When the host provides the newly tested DSH 0.1.1-rc.1 packages, these dependencies do not satisfy the unchanged >=0.1.0-rc.6 <0.2.0 peer ranges on lines 64–68: under standard semver prerelease rules, a prerelease with the 0.1.1 tuple is excluded when the range only names a 0.1.0 prerelease. The published package therefore reports incompatible peers, causing strict peer installs to reject this supported configuration and lenient installs to warn or potentially resolve unwanted copies; explicitly include the 0.1.1 prerelease line in each affected peer range.

Useful? React with 👍 / 👎.