Profile Bundle install docs resolve to 0.0.1-rc.1 while the actual bundle is tagged next (0.1.0-rc.8)

[Jokasa7]

Thanks for the recent rc.8 release. During an end-to-end Windows smoke test of the Codex Profile Bundle, I found a prerelease distribution mismatch.

Environment

• Windows
• DeepSeek Harness dsh-v0.1.0-rc.8
• Web Profile
• Package: @deepseek-ai/dsh-subagent-codex

Reproduction

npm view @deepseek-ai/dsh-subagent-codex dist-tags --json
dsh plugin --profile web add @deepseek-ai/dsh-subagent-codex
dsh --profile web --dump-config

Observed dist-tags:

{
  "latest": "0.0.1-rc.1",
  "next": "0.1.0-rc.8"
}

Expected

The install command documented for the prerelease should install a package that declares dsh.bundle, or the prerelease documentation should explicitly use @next or an exact version.

After installation, the Profile bundle list and dump-config should contain the Codex Provider row.

Actual

The untagged command installed @deepseek-ai/dsh-subagent-codex@0.0.1-rc.1.

The CLI reported:

declares no dsh.bundle — installed as a plain dependency, not a profile layer

The Codex Provider was therefore not mounted. Installing 0.1.0-rc.8 explicitly added the Bundle and the subagent-codex Provider appeared after a Profile restart.

Workaround

dsh plugin --profile web add @deepseek-ai/dsh-subagent-codex@next

or:

dsh plugin --profile web add @deepseek-ai/dsh-subagent-codex@0.1.0-rc.8

Suggested resolution

• Promote the compatible release to latest, or use @next in prerelease docs.
• Add a release test that executes the exact documented command against npm dist-tags.
• Before installation, show the resolved version and whether it declares dsh.bundle.
• When a known Bundle package lacks dsh.bundle, provide an actionable @next hint.