# AgentTeams v0.1.16-rc.3

This prerelease keeps the original 13 business tools directly available, shortens the fixed team instructions, guides captains to continue existing work, and notifies the captain when a Web plan is approved. It also includes the team-lock cleanup from [#143](https://github.com/NanmiCoder/dsh-agent-teams/pull/143).

The npm channel remains `next`. Supported Harness versions remain `0.1.2-rc.1` (recommended), `0.1.2-alpha.5`, and `0.1.2-alpha.2`. This release does not change `latest` or extend support to older embedded Desktop cores.

## Changes

- **Existing-team reuse ([#146](https://github.com/NanmiCoder/dsh-agent-teams/issues/146)).** Continue the current team and inspect state only when needed. A duplicate create error directs the captain back to the existing team instead of instructing it to end or leave first. Existing work, approval requirements and creation guards remain intact.
- **Fixed instruction overhead ([#138](https://github.com/NanmiCoder/dsh-agent-teams/issues/138)).** Keep a concise core protocol and configured profile directory in the fixed system prompt. Captains use the original 13 business tools; members see four team tools plus their ordinary coding/research tools. Team activation, approval and archive do not rewrite the plugin's system/tools prefix. No `agent_teams_open` tool or progressive-loading step is shipped.
- **Rules survive history changes.** Slash commands, natural-language requests, original tool allowlists, PTC code execution, result pruning, history compaction and cold restoration can use the business tools directly. Core rules do not depend on retaining a helper's result.
- **Web approval wakes the captain.** Approve & Run sends a control message after committing approval and starting scheduling. The captain can yield while waiting and be woken again by member reports. Repeated or failed approvals do not send a success notification.
- **Settled team locks are released.** Drop a settled queue entry only after its last waiter finishes, including rejection paths, while preserving serialization. Thanks to [spacexun2](https://github.com/spacexun2) for #143. This focused cleanup does not resolve the broader OOM investigation.

## Verification

The rc.2 tag was blocked by a Windows-only ESM path error in the new tests; no rc.2 package was published. This release uses file URLs for dynamic imports in the capability tests and real-model benchmark runner. The lifecycle test also waits for actual downstream delivery instead of assuming scheduling finishes within 20 ms, with an intentionally delayed host delivery as regression coverage. Runtime code and assets are unchanged from the locally accepted candidate.

The release workflow requires Ubuntu and Windows typecheck/build/repository verification, then installs one packed candidate through the published CLI/Loader on all three exact Harness cohorts. Nine scenarios per host cover lifecycle, two cold restores, fallback, failure, idle wakeup, six entry paths after ordinary conversation, authenticated Web approval, and protocol/compaction compatibility. The publish job verifies and publishes that same candidate file.

Pre-release source acceptance also used the real `deepseek-official / deepseek-v4.1-flash-expires-on-0910` model with `max` reasoning. A three-member review and a follow-up from an older session containing `open` history both passed external report/task/source checks; neither called the removed tool. The follow-up retained the same team and all three member identities. See the [source acceptance record](https://github.com/NanmiCoder/dsh-agent-teams/blob/v0.1.16-rc.3/docs/no-open-verification.json) for exact artifacts and limitations.

This is not a claim of lower total model cost or identical success rates across all work. The fresh real-model trial made some unnecessary dispatch/status calls. Stable plugin prefixes avoid this plugin's lifecycle-driven prefix changes; provider cache behavior, other host context, deployment changes and cache expiry remain separate.

## Install

Confirm that the actual running Harness belongs to the supported version matrix, then install into the profile you use:

```sh
dsh plugin --profile web add --save-exact @nanmicoder/dsh-agent-teams@0.1.16-rc.3
```

Restart the actual Harness process and refresh Web after upgrading. Updating a global CLI does not replace a Desktop application's embedded core.