# v0.1.28 — Install on new Harness releases

This stable plugin release fixes installation on Harness `0.2.1-rc.4`, `0.2.1-rc.5` (the current npm `latest`) and later releases. Earlier plugin versions listed every tested host in their peer dependencies, so the Harness plugin manager rejected each newly published host as incompatible. The recommended host remains `0.2.1-rc.2`.

- Declare one minimum host instead of a list: `engines.dsh` is `>=0.1.2-alpha.2`, and every DSH peer is `*`. The official installer accepts later RC, alpha and stable hosts; npm also accepts tested hosts when the plugin and Harness packages share one dependency tree.
- Keep `compatibility.json` as the CI-tested matrix only. Adding a tested host no longer changes what can be installed, and the release gate rejects version lists and upper bounds.
- `dsh-agent-teams-doctor` reports a newer host outside the tested matrix as `untested` instead of failing. `pnpm check:upstream` reports host channels that the published plugin blocks (`blockedChannels`).

If you are still on `0.1.27` with Harness `0.2.1-rc.4` or later, update the plugin using one of the commands below. Exact-version exemptions granted with `dsh plugin allow-version` for `0.1.27` are no longer needed.

## Install or update the latest version

**Use the exact version.** Desktop's pnpm 11 waits 24 hours before installing a new release: during that window a bare package name or `@latest` still installs `0.1.27`, which Harness `0.2.1-rc.4` and later reject. In **Plugins → Add plugin**, enter `@nanmicoder/dsh-agent-teams@0.1.28`, or `github:NanmiCoder/dsh-agent-teams` if GitHub is reachable. Changing npm mirrors does not remove the waiting period.

**请写明版本号安装：** 桌面端 pnpm 11 对新版本有 24 小时等待期，期间不带版本号或使用 `@latest` 仍会装到 `0.1.27`，而它在 Harness `0.2.1-rc.4` 及之后版本上会被拒绝。请在「添加插件」输入 `@nanmicoder/dsh-agent-teams@0.1.28`；能访问 GitHub 时也可以输入 `github:NanmiCoder/dsh-agent-teams`。更换镜像源不能消除等待期。

For a CLI-managed profile:

```sh
dsh plugin --profile web add --save-exact @nanmicoder/dsh-agent-teams@0.1.28
```

Or use the GitHub default branch, without a tag or commit suffix:

```sh
dsh plugin --profile web add github:NanmiCoder/dsh-agent-teams
```

A bare package name can retain an already installed exact version, so update with the version written out. If a mirror has not synced, append `--registry=https://registry.npmjs.org`. Run the selected command again when updating, then restart that profile's Harness process and refresh the browser.

## 中文

修复插件在 Harness `0.2.1-rc.4`、`0.2.1-rc.5`（当前 npm `latest`）及之后版本上无法安装的问题。此前插件把每个已测宿主逐个写进 peer 依赖，Harness 每发布一个新版本，插件管理器都会判定插件不兼容。

- 改为只声明最低宿主版本：`engines.dsh` 为 `>=0.1.2-alpha.2`，DSH peer 统一为 `*`。官方安装器接受之后发布的 RC、Alpha 和正式版；插件与 Harness 分包装在同一依赖树时，npm 也能正常安装已测宿主。
- `compatibility.json` 只作为 CI 测试矩阵，新增测试宿主不再改变可安装范围；发布门禁会拒绝版本列表和上限。
- doctor 把测试矩阵之外的新宿主标为 `untested`，不再判失败；`pnpm check:upstream` 会报告已发布插件挡住的宿主渠道。

仍在使用 `0.1.27` 且宿主为 `0.2.1-rc.4` 或更新版本的用户，请用上面的命令更新插件；之前为 `0.1.27` 设置的 `dsh plugin allow-version` 兼容性豁免不再需要。

## Validation scope

The release pipeline verifies one candidate package across the 11 hosts in the tested matrix on Ubuntu, plus rc.2/rc.3 on Windows, using the real Harness CLI, plugin, tools, sessions and subagents with a deterministic model fixture. Harness `0.2.1-rc.5` is not in the CI matrix: the release candidate passed all runtime scenarios there locally on macOS, including installation through the Harness plugin manager, while `0.1.27` failed every scenario because the plugin was rejected before loading. npm installation alongside Harness packages was checked for `0.2.1-rc.3` and `0.2.1-rc.5`. This does not establish real-provider behavior, native Desktop interaction, Windows behavior on rc.4/rc.5, or migration of existing user data.

See [compatibility.json](../compatibility.json) and the [maintenance guide](../docs/maintenance-workflow.md).