# AgentTeams v0.1.16-rc.1 — release candidate

This candidate restores team execution across the exact Harness targets `0.1.2-rc.1`, `0.1.2-alpha.5`, and `0.1.2-alpha.2`. Its release channel is npm `next`; install the exact plugin version with `dsh plugin --profile web add --save-exact @nanmicoder/dsh-agent-teams@0.1.16-rc.1` after checking that the running host is one of those targets. This is a prerelease, and older Desktop cores require their own compatible pair.

## Compatibility and correctness

- Centralize old and new host contracts: receiver-bound legacy setup, synchronous modern session setup, own session events, FIFO continuation, and retired-member delivery guards. Preserve model selection, reasoning effort, fallback, failure notification, and cleanup on both host generations.
- Persist fallback settings when adding members manually; restore the active fallback route after a cold restart. Real-host testing exposed the missing persisted setting even when mocked tests passed.
- Require the captain to use safe reassignment instead of claiming tasks on behalf of members. Preserve idempotent reads of an already active captain takeover.
- Align the status tool and captain instructions around member notifications, removing the instruction to repeatedly poll for progress.
- Bound both plan and halt JSON requests by bytes, reject malformed/non-object bodies, and keep the host Connection authentication gate.

## Contributions

The host adapter incorporates the migration analysis and reproduction cases from [Adol1111's #119](https://github.com/NanmiCoder/dsh-agent-teams/pull/119), [Zn-Dk's #124](https://github.com/NanmiCoder/dsh-agent-teams/pull/124), and [chenkai2's #130](https://github.com/NanmiCoder/dsh-agent-teams/pull/130). Their proposals were integrated at one compatibility boundary, with additional receiver, lifecycle, FIFO and failure coverage.

Separately merged contributions retain their original authors and commits: [#26](https://github.com/NanmiCoder/dsh-agent-teams/pull/26), [#63](https://github.com/NanmiCoder/dsh-agent-teams/pull/63), [#74](https://github.com/NanmiCoder/dsh-agent-teams/pull/74), [#82](https://github.com/NanmiCoder/dsh-agent-teams/pull/82), [#83](https://github.com/NanmiCoder/dsh-agent-teams/pull/83), [#84](https://github.com/NanmiCoder/dsh-agent-teams/pull/84), [#86](https://github.com/NanmiCoder/dsh-agent-teams/pull/86), [#90](https://github.com/NanmiCoder/dsh-agent-teams/pull/90), and [#93](https://github.com/NanmiCoder/dsh-agent-teams/pull/93). These cover argument validation, wording, parked-attempt recovery, panel resizing, working indicators, model badges, Windows build paths, and client service declarations.

## Maintenance and release policy

- Use `compatibility.json` for exact support targets, development dependency validation and the CI matrix. Freeze the complete DSH development dependency cohort; an exact CLI version alone does not freeze its transitive packages.
- Add a read-only installation doctor for version mixing, missing packages, duplicate runtime identities and profile/plugin mismatches.
- Vendor the community upgrade, audit, benchmark, testing and release skills with a pinned source revision and license. Keep local rules separate from upstream guidance.
- Require Ubuntu and Windows static checks plus real packaged-plugin execution on all three hosts before publication. Every host verifies the same tgz, and the publish job verifies its digest before publishing that artifact.
- Use `next` for plugin prereleases. A stable `latest` requires the recommended host and complete matrix; Alpha-only validation is insufficient.

## Verification scope

The runtime runner installs actual npm host packages and the candidate artifact in isolated directories, then exercises the CLI, profile, plugin tools, member sessions, messages, reasoning, fallback, failure handling and cold restoration. The external model adapter supplies deterministic responses so the suite can run without credentials. It is not a real-provider benchmark or a claim about every Desktop/OS/version combination.

Separate real DeepSeek API acceptance using `deepseek-v4-flash` passed on all three hosts from `/tmp`, plus a real-model rc.1 Web workflow. Ubuntu/Windows typecheck, build and full verify, and the three Ubuntu host cohorts passed in CI. These checks do not establish native Desktop compatibility or resolve the independent OOM investigation.

See the repository's [maintenance workflow](../docs/maintenance-workflow.md) and the dated implementation/acceptance record for the exact outcomes and remaining limits. Older `0.1.0-*` and `0.1.1-*` hosts are outside this candidate's support matrix; retain a known compatible exact pair or migrate both sides.