dsh-plugin-t-expert 0.3.72 → 0.3.88

package/lib/command.js

@@ -133,6 +133,13 @@ function relayRouteDirective(input, list) {
     `【T专家 · 未指定小队】用户敲的是：\`/t ${input}\`，其中没有能匹配到小队名的词。`,
     `请把「${input}」当作目标，从下面的小队里挑最合适的一个，然后**直接调用 t_team_create 并带上 profile="<key>"** 建队（approval=\"required\" 先 staged，等用户在面板 review）；`,
     "不要反问用户该用哪个小队，也不要自己手搭成员——profile 已带好成员与人格。",
+    // profile 描述的是「这类目标通常涉及哪些角色」，不是「这次必须全员上场」。不写清这一条，
+    // 队长会把它读成「roster 不可动」，于是为了不让人闲着而给边缘角色硬造任务：实测一份单文件
+    // HTML 简历被派给了 5 个人 —— 后端架构师去写「信息架构」、数据库性能工程师去查「A4 分页」。
+    // 那次的队长思考里两处原话正是「有点牵强」「这有点为凑人头造工作」，但它仍然照派了。
+    "但 profile 是「编制清单」，不等于这次全员都得上场：挑定小队后先逐人自问「这次真的需要这个角色的独有产出吗」，用不上的在 staged 阶段用 t_team_edit_plan 的 remove_member 裁掉。",
+    "顺序必须是**先裁人、后建任务**——任务一旦引用了成员，再删人就得先改依赖引用。拿不准的一律保留，且至少留 2 人（一个产出者 + 一个独立验证者，否则独立验证无从谈起）。",
+    "无论裁没裁，都要在给用户的计划说明里写明留了谁、裁了谁、为什么。",
     "若确实没有合适的小队，就用中文说明原因并列出可用小队。",
     "",
     list,

package/lib/index.js

@@ -1991,11 +1991,9 @@ export function apply(ctx, config) {
     },
   });
 
-  // ---- 随包 skill（运维入口 + DeepSeek Harness 项目知识）----
-  // 都只对特定任务有用，所以不占常驻提示段，改成按需加载的 skill：
+  // ---- 随包 skill（运维入口）----
+  // 它只对特定任务有用，所以不占常驻提示段，改成按需加载的 skill：
   //   · t-expert-manager      维护这个插件的人：名册 / 小队 / 装机 / 发布
-  //   · dsh-harness-project   在 deepseek-harness 检出里读写代码：架构、启动模型、扩展点、门禁
-  //   · dsh-harness-languages 同一个仓库里的各语言面规则与工具链
   // 可选依赖：宿主没有 skill 注册表时静默跳过，不影响上面任何功能。
   installBundledSkills(ctx, config);
 }

package/lib/remote.js

@@ -58,7 +58,7 @@ function descriptor(method, parameters, typeSymbol, schema) {
     method,
     invocation: { kind: "direct" },
     parameters,
-    result: { mode: "strict", typeSymbol, schema },
+    result: { mode: "strict", typeSymbol, schema, create: () => schema },
   };
 }
 
@@ -72,7 +72,7 @@ const DESCRIPTORS = [
       name: "patch",
       wire: "patch",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "TTeamUiPrefsPatch", schema: uiPrefsPatchSchema },
+      codec: { mode: "strict", typeSymbol: "TTeamUiPrefsPatch", schema: uiPrefsPatchSchema, create: () => uiPrefsPatchSchema },
     },
   ], "TTeamUiPrefs", uiPrefsSchema),
   // 定时事项：全部写操作都回传刷新后的整份快照，面板拿到就能直接重绘（与名册/小队同一口径）。
@@ -82,7 +82,7 @@ const DESCRIPTORS = [
       name: "input",
       wire: "input",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "TTeamScheduleInput", schema: scheduleInputSchema },
+      codec: { mode: "strict", typeSymbol: "TTeamScheduleInput", schema: scheduleInputSchema, create: () => scheduleInputSchema },
     },
   ], "TTeamSchedule", scheduleSnapshotSchema),
   descriptor("updateScheduleItem", [
@@ -90,13 +90,13 @@ const DESCRIPTORS = [
       name: "id",
       wire: "id",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "patch",
       wire: "patch",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "TTeamSchedulePatch", schema: schedulePatchSchema },
+      codec: { mode: "strict", typeSymbol: "TTeamSchedulePatch", schema: schedulePatchSchema, create: () => schedulePatchSchema },
     },
   ], "TTeamSchedule", scheduleSnapshotSchema),
   descriptor("deleteScheduleItem", [
@@ -104,7 +104,7 @@ const DESCRIPTORS = [
       name: "id",
       wire: "id",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
   ], "TTeamSchedule", scheduleSnapshotSchema),
   descriptor("runScheduleItem", [
@@ -112,7 +112,7 @@ const DESCRIPTORS = [
       name: "id",
       wire: "id",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
   ], "TTeamSchedule", scheduleSnapshotSchema),
   descriptor("previewSchedule", [
@@ -120,7 +120,7 @@ const DESCRIPTORS = [
       name: "cron",
       wire: "cron",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(120) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(120), create: () => z.string().min(1).max(120) },
     },
   ], "TTeamSchedulePreview", schedulePreviewSchema),
   descriptor("ensureScheduleWorkspace", [
@@ -128,7 +128,7 @@ const DESCRIPTORS = [
       name: "path",
       wire: "path",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(1024) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(1024), create: () => z.string().max(1024) },
     },
   ], "TTeamScheduleWorkspace", scheduleWorkspaceSchema),
   descriptor("setEnabled", [
@@ -136,13 +136,13 @@ const DESCRIPTORS = [
       name: "enabled",
       wire: "enabled",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string[]", schema: z.array(z.string()) },
+      codec: { mode: "strict", typeSymbol: "string[]", schema: z.array(z.string()), create: () => z.array(z.string()) },
     },
     {
       name: "expectedRevision",
       wire: "expectedRevision",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "number", schema: z.number().int().min(0) },
+      codec: { mode: "strict", typeSymbol: "number", schema: z.number().int().min(0), create: () => z.number().int().min(0) },
     },
   ], "TTeamEnabledState", enabledStateSchema),
   descriptor("getPrompt", [
@@ -150,13 +150,13 @@ const DESCRIPTORS = [
       name: "slug",
       wire: "slug",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "division",
       wire: "division",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(64) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(64), create: () => z.string().min(1).max(64) },
     },
   ], "TTeamPrompt", promptSchema),
   descriptor("getSquads", [], "TTeamSquads", squadsSnapshotSchema),
@@ -165,13 +165,13 @@ const DESCRIPTORS = [
       name: "squads",
       wire: "squads",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "TTeamSquadInput[]", schema: z.array(squadInputSchema).min(1).max(48) },
+      codec: { mode: "strict", typeSymbol: "TTeamSquadInput[]", schema: z.array(squadInputSchema).min(1).max(48), create: () => z.array(squadInputSchema).min(1).max(48) },
     },
     {
       name: "expectedRevision",
       wire: "expectedRevision",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(64) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(64), create: () => z.string().max(64) },
     },
   ], "TTeamSquads", squadsSnapshotSchema),
   descriptor("startSquad", [
@@ -179,13 +179,13 @@ const DESCRIPTORS = [
       name: "profileKey",
       wire: "profileKey",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(64) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(64), create: () => z.string().min(1).max(64) },
     },
     {
       name: "sessionId",
       wire: "sessionId",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(128), create: () => z.string().max(128) },
     },
   ], "TTeamStartResult", startResultSchema),
   descriptor("getTeams", [
@@ -193,7 +193,7 @@ const DESCRIPTORS = [
       name: "archived",
       wire: "archived",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "boolean", schema: z.boolean() },
+      codec: { mode: "strict", typeSymbol: "boolean", schema: z.boolean(), create: () => z.boolean() },
     },
   ], "TTeamTeams", teamsSnapshotSchema),
   // teamId 是**团队名 slug 化**的产物，跨工作区会重名；workspacePath 让宿主精确定位到
@@ -207,14 +207,14 @@ const DESCRIPTORS = [
       name: "teamId",
       wire: "teamId",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "workspacePath",
       wire: "workspacePath",
       source: "json",
       acceptsUndefined: true,
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(1024) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(1024), create: () => z.string().max(1024) },
     },
   ], "TTeamStopResult", stopResultSchema),
   // 彻底删除一支团队（运行中的与已归档的都收）：设置页「运行中的团队」那一行的「删除」按钮。
@@ -223,14 +223,14 @@ const DESCRIPTORS = [
       name: "teamId",
       wire: "teamId",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "workspacePath",
       wire: "workspacePath",
       source: "json",
       acceptsUndefined: true,
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(1024) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(1024), create: () => z.string().max(1024) },
     },
   ], "TTeamDeleteResult", deleteTeamResultSchema),
   // 自建专家的增删改：都回传刷新后的整份名册快照，面板拿到就能直接重绘。
@@ -239,7 +239,7 @@ const DESCRIPTORS = [
       name: "expert",
       wire: "expert",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "TTeamCustomExpertInput", schema: customExpertInputSchema },
+      codec: { mode: "strict", typeSymbol: "TTeamCustomExpertInput", schema: customExpertInputSchema, create: () => customExpertInputSchema },
     },
   ], "TTeamCatalog", catalogSnapshotSchema),
   descriptor("updateExpert", [
@@ -247,19 +247,19 @@ const DESCRIPTORS = [
       name: "slug",
       wire: "slug",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "expert",
       wire: "expert",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "TTeamCustomExpertInput", schema: customExpertInputSchema },
+      codec: { mode: "strict", typeSymbol: "TTeamCustomExpertInput", schema: customExpertInputSchema, create: () => customExpertInputSchema },
     },
     {
       name: "expectedHash",
       wire: "expectedHash",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(64) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(64), create: () => z.string().max(64) },
     },
   ], "TTeamCatalog", catalogSnapshotSchema),
   descriptor("deleteExpert", [
@@ -267,13 +267,13 @@ const DESCRIPTORS = [
       name: "slug",
       wire: "slug",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "expectedHash",
       wire: "expectedHash",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(64) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(64), create: () => z.string().max(64) },
     },
   ], "TTeamCatalog", catalogSnapshotSchema),
   // 分类管理：都回传刷新后的整份名册快照（面板拿到就能直接重绘）。
@@ -282,13 +282,13 @@ const DESCRIPTORS = [
       name: "key",
       wire: "key",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "label",
       wire: "label",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(40) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(40), create: () => z.string().max(40) },
     },
   ], "TTeamCatalog", catalogSnapshotSchema),
   descriptor("updateCategory", [
@@ -296,13 +296,13 @@ const DESCRIPTORS = [
       name: "key",
       wire: "key",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
     {
       name: "label",
       wire: "label",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(40) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().max(40), create: () => z.string().max(40) },
     },
   ], "TTeamCatalog", catalogSnapshotSchema),
   descriptor("deleteCategory", [
@@ -310,7 +310,7 @@ const DESCRIPTORS = [
       name: "key",
       wire: "key",
       source: "json",
-      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128) },
+      codec: { mode: "strict", typeSymbol: "string", schema: z.string().min(1).max(128), create: () => z.string().min(1).max(128) },
     },
   ], "TTeamCatalog", catalogSnapshotSchema),
 ];

package/lib/schedule.js

@@ -5,8 +5,8 @@
  * 为什么自建而不是直接依赖 `@weibaohui/dsh-tasks`：用户明确要求两个插件可以同时安装、
  * 同时可用。所以这里与它**零共享**——
  *   · 数据不落它的 `dsh_tasks` 存储域，而是 T专家 自己的数据目录（`<root 同级>/schedule.json`）；
- *   · 服务名 `tTeamSchedule`、错误码前缀 `tTeam/schedule-*`、消息来源 `plugin: dsh-plugin-t-expert`
- *     全部独立，两个插件的任务互不可见、互不干扰。
+ *   · 服务名 `tTeamSchedule`、错误码前缀 `tTeam/schedule-*` 全部独立，两个插件的任务互不可见、互不干扰。
+ *     提交给会话的提示词用 `source.kind: "user"`（聊天右侧才渲染用户气泡；`plugin` 源会被收成 inject）。
  *
  * 三件事在这里闭环：
  *   1. 持久化：一个 JSON 文件，原子写（与 `teams.json` 同级、同风格）；
@@ -284,11 +284,14 @@ export function createScheduleEngine(options) {
       } catch (error) {
         logger?.warn?.(`[t-team] 定时任务「${item.title}」的提示词改写失败，按原文提交：${error instanceof Error ? error.message : String(error)}`);
       }
+      // 必须用 source.kind: "user"：DSH 聊天把非 user 的 user/message 收成左侧
+      // inject/context（plugin 源只显示插件名，正文不进右侧气泡）。定时任务的指令
+      // 本身就是用户写的提示词，应当像手打那条一样出现在对话右侧。
       handle.agent.followup({
         id: randomUUID(),
         role: "user",
         content: [{ type: "text", text: promptText }],
-        source: { kind: "plugin", plugin: PLUGIN_ID },
+        source: { kind: "user" },
       });
       return withRun(item, { at: startedAt, ok: true, sessionId });
     } catch (error) {

package/lib/skill.js

@@ -1,18 +1,14 @@
 // @ts-check
 /**
- * 随包发布的 skill：把「T专家 运维」与「DeepSeek Harness 项目知识」做成**随 npm 包分发**的 skill。
+ * 随包发布的 skill：把「T专家 运维」做成**随 npm 包分发**的 skill。
  *
- * 为什么是 skill 而不是再加一段 systemPrompt：这些内容只在特定任务里需要（改名册/小队/装机/发布，
- * 或在一个 deepseek-harness 检出里读写代码），常驻提示段是纯浪费 token；skill 的 description 本来就是路由面。
+ * 为什么是 skill 而不是再加一段 systemPrompt：这些内容只在特定任务里需要（改名册/小队/装机/发布），
+ * 常驻提示段是纯浪费 token；skill 的 description 本来就是路由面。
  *
  * 形态：`<包根>/skills/<name>/SKILL.md` 是标准 skill 文件（任何 skill 扫描器都能直接发现），
  * 这里额外把它们注册进宿主的 skill 注册表，这样 npm 安装（插件在 node_modules 里、没有运维台）也能用。
  *
- * 三个 skill 的来源：
- *   - `t-expert-manager`：本仓运维入口，正文带占位符，注册时按本机布局渲染。
- *   - `dsh-harness-project` / `dsh-harness-languages`：`dsh-project-expert` agent preset 里那两个
- *     项目知识 skill 的**逐字节拷贝**（preset 是源，这里是随插件发布的副本），
- *     所以插件用户在任何仓库里都能加载这套 harness 项目知识。
+ * 唯一的 skill 是 `t-expert-manager`：本仓运维入口，正文带占位符，注册时按本机布局渲染。
  *
  * 两条刻意的设计：
  *   1. **可选依赖**：走 `ctx.inject(["skills"], …)`，而不是把 `skills` 加进插件的静态 `inject`。
@@ -33,9 +29,9 @@ export const SKILLS_ROOT = resolve(dirname(fileURLToPath(import.meta.url)), ".."
  * 随包发布的 skill 清单（目录名 = 宿主路由用的 skill 名）。
  *
  * 顺序即注册顺序。缺文件的条目会被跳过并逐条告警，而不是让整段注册失败 ——
- * 一个 skill 文件缺失不该带走另外两个（见 {@link LOCAL_ONLY_SKILL_NAMES} 的例外）。
+ * 一个 skill 文件缺失不该带走其余（见 {@link LOCAL_ONLY_SKILL_NAMES} 的例外）。
  */
-export const BUNDLED_SKILL_NAMES = ["t-expert-manager", "dsh-harness-project", "dsh-harness-languages"];
+export const BUNDLED_SKILL_NAMES = ["t-expert-manager"];
 
 /**
  * **只在本机布局里存在**的 skill：不进 npm 包（见 `package.json` 的 `files`）。
@@ -204,7 +200,7 @@ export function buildBundledSkills(config = {}) {
 /**
  * 把随包 skill 注册进宿主。`skills` 服务缺席时什么都不做（可选依赖，见文件头注释）。
  *
- * 缺失条目**逐条 warn**（一个 skill 文件缺失不该带走另外两个，但也不能悄悄消失）；
+ * 缺失条目**逐条 warn**（一个 skill 文件缺失不该带走其余，但也不能悄悄消失）；
  * 全军覆没时额外再给一条汇总 warn，保持既有的「都读不到」信号。
  * @param ctx - 插件上下文。
  * @param config - 插件配置。
@@ -217,7 +213,10 @@ export function installBundledSkills(ctx, config) {
     ctx.logger?.warn?.(`[t-team] 随包 skill「${item.name}」未注册：${item.reason}（其余 skill 照常注册）`);
   }
   if (skills.length === 0) {
-    ctx.logger?.warn?.(`[t-team] 随包 skill 未注册：读不到 ${join(SKILLS_ROOT, "<name>", "SKILL.md")}`);
+    /* 没有 `missing` 就说明缺席的全是 LOCAL_ONLY：那是 npm 安装的预期状态，出声反而是噪音。 */
+    if (missing.length > 0) {
+      ctx.logger?.warn?.(`[t-team] 随包 skill 未注册：读不到 ${join(SKILLS_ROOT, "<name>", "SKILL.md")}`);
+    }
     return 0;
   }
   ctx.inject(["skills"], (scoped) => {

package/lib/teams/command.js

@@ -60,10 +60,14 @@ export function buildActivationDirective(goal, profile, taskPlanning = 'seed') {
     if (profile !== undefined) {
         lines.push(`Use profile="${profile}" when creating a new team.`);
         if (taskPlanning === 'captain') {
-            lines.push('This profile supplies the roster and guardrails. After create, do not recreate members.', 'Derive the smallest useful task graph from the goal while the team is staged; do not ask the user whether to split, merge, serialize, or parallelize.', 'Independent supplemental work must become separate ready tasks so idle members can run in parallel. Add dependencies only for genuine prerequisites and later synthesis.');
+            // 编制授权：profile 是「这类目标通常涉及哪些角色」，不是「这次必须全员上场」。
+            // 缺了这句，队长会把上面那句 "do not recreate members" 读成「roster 不可动」，转而给
+            // 边缘角色硬造任务；而下面那句原文（idle members can run in parallel）更是在明示
+            // 「给闲着的成员找活」—— 实测一份单文件 HTML 简历就是这样被派给 5 个人的。
+            lines.push('This profile supplies the roster and guardrails. After create, do not recreate members.', 'The roster is a staffing list, not a mandate to field everyone: drop any role whose distinct output this goal does not need (t_team_edit_plan remove_member while staged), and trim BEFORE creating tasks — once a task references a member, removing that member means fixing references first. When unsure, keep the role. Keep at least two members (a producer plus an independent verifier). State in the plan whom you kept, whom you trimmed, and why.', 'Derive the smallest useful task graph from the goal while the team is staged; do not ask the user whether to split, merge, serialize, or parallelize.', 'An idle member is not a reason to invent work: add a task only when the goal itself needs that output, and say why. When work genuinely is independent, make it a separate ready task so it can run in parallel instead of serializing it. Add dependencies only for genuine prerequisites and later synthesis.');
         }
         else {
-            lines.push('Do not recreate the same members or seed tasks manually.');
+            lines.push('Do not recreate the same members or seed tasks manually.', 'You may still drop a role this goal does not need (t_team_edit_plan remove_member while the team is staged); state in the plan whom you kept, whom you trimmed, and why.');
         }
     }
     lines.push(goal === '' ? 'The goal was not given — ask the user what the team should accomplish.' : `Goal: ${goal}`);

package/lib/teams/index.js

@@ -92,10 +92,10 @@ export function usageSectionText(toolNames, profilesText = '') {
 2. Add each needed role once; members inherit your model route unless another is requested/needed. A requested profile goes to create({profile}); it supplies its roster. Seed profiles also supply tasks; captain-planning profiles require your DAG. Do not duplicate either.
 3. Build the complete smallest useful DAG while staged. Every task needs a subject; dependencies represent prerequisites. Give every required contributor a task or explicit message. Present the plan and end your turn for review; never approve in that planning turn. Approve only after a later explicit user approval or the Web action.
 4. Respect Web approve/return/discard control messages. On return, ask what to change before editing; after the answer, use one atomic t_team_edit_plan batch (edit downstream references before removals), summarize and await review again. Never inspect or edit the T Team state directory in the workspace or the plugin source code to revise plans. Discard does not authorize a replacement.
-5. The scheduler dispatches ready tasks after approval. Delegate; do not duplicate slow work or send messages merely to start a stage. Handle reports/user work, then yield when waiting is all that remains: reports wake you automatically. Use status after a delivery or user request, never busy-poll or wait for unassigned members.
+5. The scheduler dispatches ready tasks after approval. Delegate; do not duplicate slow work or send messages merely to start a stage. Handle reports/user work, then yield when waiting is all that remains: reports wake you automatically. Use status after a delivery or user request, never busy-poll or wait for unassigned members. A member report already states what changed, so do not call status again merely to confirm it; call it when you need the parts the report does not cover (the current graph, other members' state).
 6. Tasks carry attempt_id capabilities. Use the current attempt_id; stale means ownership changed. Pause members only on explicit request; later guidance via send_message continues that same attempt. Retry, transfer or take over through reassign_task first; it revokes the old attempt and waits for quiescence. Prefer a member. Captain implementation/review takeover requires a user request. Every takeover is one ready task at a time, finished in this turn; never yield with captain-owned work open.
 7. Quality kinds (requirements, implementation, verification, review, repair, integration) require objective + acceptance; implementation/repair also require inScope + verify. Derive paths/commands from the workspace/profile, never assume src/ or pnpm test. Review/requirements complete only with verdict=pass; needs_revision/reject fail with findings. Never approve your own implementation or ask for a deliberate failure.
-8. When full quality mode is requested: requirements → implementation → verification → review → integration. Plan the entire DAG while staged, including implementation before requirements finishes and integration depending on review round 1. Failed review automatically adds repair + next review and rewires pending downstream gates. Do not recreate this loop, omit integration or depend on a failed task. Review acceptance judges the latest implementation. Do not put smoke-test scripts into task instructions.
+8. When full quality mode is requested: requirements → implementation → verification → review → integration. Plan the entire DAG while staged, including implementation before requirements finishes and integration depending on review round 1. Failed review automatically adds repair + next review and rewires pending downstream gates. Do not recreate this loop, omit integration or depend on a failed task. The automatic repair task already carries the review findings and is already assigned to the implementer, so do NOT relay those findings through send_message: the implementer has them, and the relay only makes it stop and explain that the repair is already done. Review acceptance judges the latest implementation. Do not put smoke-test scripts into task instructions.
 9. Halted means the user stopped work (including the captain turn). Resume only on a later explicit user request with a reason, via t_team_resume or create_task({resume:true,resumeReason}); creating tasks alone never resumes. Escalated means the review loop hit its limit, not a halt. Deployment requires explicit user confirmation.
 10. Wait for all required tasks to be terminal and members idle/ready, present results, then delete/archive unless the user wants to continue. Never discard unfinished work without authorization.
 Tools: ${toolNames}${profilesText === '' ? '' : `\n\n${profilesText}`}`;

package/lib/teams/members.js

@@ -447,8 +447,8 @@ Working rules:
    - include a concise output in either case;
    - a stale-attempt rejection means the captain reassigned or took over the task; stop touching that task and wait for new work.
    claimed cannot jump to completed. Mark in_progress first, then completed or failed.
-   Include attempt_id on every update. Then send_message to captain and become idle.
-4. Send a short report to the captain with t_team_send_message (to=captain) when you complete a task or hit a blocker.
+   Include attempt_id on every update, then become idle.
+4. Write the report exactly once. t_team_update_task IS your report: the captain and every downstream task read output/summary/tried from it. Then send_message (to=captain) a ONE-LINE notice ("<the task id> completed — result in the task output") — that line is what wakes the captain, it must not restate the report — and keep your closing turn message to ONE line as well, because it is delivered to the captain in full. A completion written out three times costs three times the context and says nothing new. Use a longer send_message only for what the task record cannot carry: a blocker, or a decision only the captain can make.
 5. To ask a teammate something, use t_team_send_message with to=<teammate name>; the message lands in their mailbox and wakes them directly — teammates talk to each other without the captain in the loop. The same applies to the captain (to=captain).
 6. After your turn becomes idle, the shared task scheduler may assign your next ready task automatically. Never claim a second task while you still own unfinished work.
 7. If you already own an open attempt (claimed or in_progress) and receive mail, treat it as guidance for that same attempt_id unless the mail explicitly tells you to stop or fail. Do not claim a new task in that turn.

package/lib/teams/quality-gates.js

@@ -682,7 +682,7 @@ export function isCommandResult(value) {
 // optional tool parameters as "" instead of omitting them (e.g. GPT-5.6
 // sending reviewedTaskId:"" or profile:""), which would otherwise be written
 // to team.json and then brick the whole team state on reload.
-const BLANK_SENSITIVE_STRING_FIELDS = ['objective', 'reviewedTaskId', 'sourceTaskId'];
+const BLANK_SENSITIVE_STRING_FIELDS = ['objective', 'reviewedTaskId', 'sourceTaskId', 'summary'];
 const BLANK_SENSITIVE_STRING_LIST_FIELDS = [
     'inScope',
     'outOfScope',
@@ -693,6 +693,7 @@ const BLANK_SENSITIVE_STRING_LIST_FIELDS = [
     'changedPaths',
     'sourceFindingIds',
     'coverageOf',
+    'tried',
 ];
 /**
  * Normalize blank optional task fields to omitted ("blank means absent").
@@ -735,10 +736,15 @@ export function hasValidQualityTaskFields(value) {
         return false;
     if (value['sourceTaskId'] !== undefined && !nonemptyString(value['sourceTaskId']))
         return false;
+    // 交接契约（2026-09-20）：`summary` 是给下游看的压缩结论，`tried` 是走过的死路。
+    // 只校验形状、**不限长度** —— 过长的摘要在渲染时截断即可，绝不能因为写多了就让一次
+    // 已完成的工作被判成非法状态（那会连带整份 team.json 在重载时失效）。
+    if (value['summary'] !== undefined && !nonemptyString(value['summary']))
+        return false;
     if (value['reviewedAttempt'] !== undefined && !(Number.isSafeInteger(value['reviewedAttempt']) && value['reviewedAttempt'] >= 0)) {
         return false;
     }
-    const stringLists = ['inScope', 'outOfScope', 'acceptance', 'verify', 'deliverables', 'nonGoals', 'changedPaths', 'sourceFindingIds', 'coverageOf'];
+    const stringLists = ['inScope', 'outOfScope', 'acceptance', 'verify', 'deliverables', 'nonGoals', 'changedPaths', 'sourceFindingIds', 'coverageOf', 'tried'];
     for (const key of stringLists) {
         if (value[key] === undefined)
             continue;