@michengai/dsh-agency-agents 1.0.12 → 1.0.14

package/CHANGELOG.md

@@ -6,6 +6,18 @@ This file records features and upgrade boundaries. npm and GitHub Releases remai
 
 ## Unreleased
 
+## 1.0.14 - 2026-10-12
+
+- When you name an expert, the assistant calls that expert immediately instead of analyzing the task first.
+- Expert and team requests should be a short brief: the goal, constraints, and file paths. Do not paste source code into the request.
+- A single expert task can be up to 2,000 characters. A team task can be up to 20,000 characters. Longer text is rejected with a prompt to summarize and retry.
+- A running expert is labeled with the expert name.
+
+## 1.0.13 - 2026-10-10
+
+- When building a team, Add member starts with enabled experts so you can pick from the ones you already use.
+- Disabled experts can still join a team. If you do not want to use an expert on its own, switch status to All or Disabled.
+
 ## 1.0.12 - 2026-10-10
 
 - After saving an expert team, you can keep editing an enabled custom expert. You no longer need to disable it first.

package/CHANGELOG.zh-CN.md

@@ -6,6 +6,18 @@
 
 ## 未发布
 
+## 1.0.14 - 2026-10-12
+
+- 点名专家后，助手会立刻召唤该专家，不再先自己分析任务。
+- 专家和专家团的任务应只写目标、约束和文件路径，不要把源码写进召唤请求。
+- 单个专家任务最多 2000 字，专家团任务最多 20000 字。超出后会提示压缩为摘要再重试。
+- 正在运行的专家会显示专家名称。
+
+## 1.0.13 - 2026-10-10
+
+- 组建专家团时，添加成员默认只显示已启用的专家，方便从常用专家里选择。
+- 停用的专家也可以加入专家团。不想在对话里单独使用专家、只想用专家团时，把状态改为「全部」或「已停用」。
+
 ## 1.0.12 - 2026-10-10
 
 - 保存专家团后，可以继续修改已启用的自定义专家，不必先停用。

package/README.md

@@ -44,7 +44,7 @@ Manage teams in **Settings → Experts → Expert teams**, sharing the header, s
 ### Configure and use
 
 1. Use a built-in team, copy it to customize, or create a team of 2–8 distinct experts. Up to 100 custom teams can be saved.
-2. Set the name, description, tags, member duties, shared goal, constraints, delivery requirements, and 1–3 examples. Use, customize, or restore the coordinator template.
+2. Set the name, description, tags, member duties, shared goal, constraints, delivery requirements, and 1–3 examples. Add member starts with enabled experts; disabled experts can still join if you switch status to All or Disabled. Use, customize, or restore the coordinator template.
 3. Confirm enabling required experts when enabling a team. Switch to Expert teams in the composer picker or select through `@`, then write the task. Selecting or adding an example never sends the message.
 4. The current main conversation delegates, verifies evidence, handles disagreements, and delivers one result; no additional leader subagent is created. Ordinary mode runs up to four experts concurrently and preserves completed results if others fail.
 
@@ -69,7 +69,7 @@ Retain `list_experts`, `summon_expert`, and `summon_experts`. Add `list_expert_t
 - Team configuration lives in the host `agency-agents` settings namespace. Keep drafts on edit conflicts and review the latest configuration. Disabling or deleting teams does not disable experts or delete historical conversations.
 - Experts cannot summon further experts or automatically add analysis rounds. Cancellation prevents queued starts; completed results and failures are reported separately.
 
-> This README describes version 1.0.12; npm and GitHub Releases determine publication status. See the [changelog](CHANGELOG.md) for the full changes and [release notes](RELEASE_NOTES.md) for the bilingual release description. Upgrades retain expert settings. Back up settings before downgrading because older versions do not support teams.
+> This README describes version 1.0.14; npm and GitHub Releases determine publication status. See the [changelog](CHANGELOG.md) for the full changes and [release notes](RELEASE_NOTES.md) for the bilingual release description. Upgrades retain expert settings. Back up settings before downgrading because older versions do not support teams.
 ## Screenshots
 
 The screenshots below show the 1.0.0 interface in Chinese. Experts and expert teams share the same settings page.

package/README.zh-CN.md

@@ -44,7 +44,7 @@
 ### 配置与使用
 
 1. 直接使用内置团，或复制后修改；也可新建 2～8 位成员的自定义团，最多保存 100 个。
-2. 设置名称、简介、标签、成员职责、共同目标、约束、交付要求和 1～3 条任务示例。主理人提示词可使用团队模板、自定义或恢复模板。
+2. 设置名称、简介、标签、成员职责、共同目标、约束、交付要求和 1～3 条任务示例。添加成员时默认只看已启用专家；停用的专家也可以加入，把状态改为「全部」或「已停用」。主理人提示词可使用团队模板、自定义或恢复模板。
 3. 启用团队时确认同步启用所需专家。聊天工具栏切到「专家团」，或通过 `@` 选择团队，再填写任务；选择与示例均不会自动发送。
 4. 当前主会话分工、核验证据、处理分歧并统一交付，不额外创建团长。普通模式最多四位专家并发；部分失败会保留已完成结果。
 
@@ -69,7 +69,7 @@
 - 团队配置保存在宿主 `agency-agents` 命名空间。编辑冲突保留草稿并提示核对最新配置；停用或删除团队不会停用专家，也不会删除历史会话。
 - 专家不得继续召唤专家或自动追加分析轮次。取消会停止未启动任务；已有结果和失败原因分别报告。
 
-> 本 README 描述 1.0.12，正式发行以 npm 和 GitHub Releases 为准。完整改动见[更新日志](CHANGELOG.zh-CN.md)，双语版本说明见[发行说明](RELEASE_NOTES.md)。升级保留已有专家配置；回退旧版前先备份设置，旧版不具备团队功能。
+> 本 README 描述 1.0.14，正式发行以 npm 和 GitHub Releases 为准。完整改动见[更新日志](CHANGELOG.zh-CN.md)，双语版本说明见[发行说明](RELEASE_NOTES.md)。升级保留已有专家配置；回退旧版前先备份设置，旧版不具备团队功能。
 ## 界面预览
 
 以下为 1.0.0 中文界面截图，专家与专家团共用同一个设置页面。

package/RELEASE_NOTES.md

@@ -1,11 +1,16 @@
 ## 中文说明
 
-- 已安装插件列表显示「Agency Agents」和中文简介，不再只用包名。远程入口显示「Agency Agents 接口」。显示名来自 `locale/zh.json`、`locale/en.json` 和 `locale/remote/` 的 `meta.title`、`meta.description`。
-- 从 GitHub 安装时已包含运行文件，不必再手动构建。
+- 点名专家后，助手会立刻召唤该专家，不再先自己分析任务。
+- 专家和专家团的任务应只写目标、约束和文件路径，不要把源码写进召唤请求。
+- 单个专家任务最多 2000 字，专家团任务最多 20000 字。超出后会提示压缩为摘要再重试。
+- 正在运行的专家会显示专家名称。
 
 ---
 
 ## English
 
-- The installed-plugin list shows “Agency Agents” and a localized description instead of the package name. The remote entry shows “Agency Agents remote”. Titles and descriptions come from `meta.title` and `meta.description` in `locale/zh.json`, `locale/en.json`, and `locale/remote/`.
-- Installing from GitHub now includes the compiled runtime, so no manual build is required.
+- When you name an expert, the assistant calls that expert immediately instead of analyzing the task first.
+- Expert and team requests should be a short brief: the goal, constraints, and file paths. Do not paste source code into the request.
+- A single expert task can be up to 2,000 characters. A team task can be up to 20,000 characters. Longer text is rejected with a prompt to summarize and retry.
+- A running expert is labeled with the expert name.
+