dsh-plugin-t-expert 0.1.1 → 0.2.2

package/lib/i18n.js

@@ -3,9 +3,9 @@
 export const NS = "t-team";
 
 const ZH = {
-  "error.rootMissing": "T专家 专家目录不存在或无法访问：\"{root}\"。请运行 ~/.t-team/sync.sh 生成，或配置正确的 root。",
+  "error.rootMissing": "T专家 专家目录不存在或无法访问：\"{root}\"。插件首次启动会自动把自带名册播种到该目录；若你手工移动过数据目录，请把 root 指到正确位置。",
   "error.rootNotDir": "T专家 专家目录 \"{root}\" 不是目录",
-  "error.catalogEmpty": "在 root \"{root}\" 下没有发现任何专家（*.md）。请确认已运行 sync.sh。",
+  "error.catalogEmpty": "在 root \"{root}\" 下没有发现任何专家（*.md）。删掉这个空目录让插件下次启动重新播种，或把 root 改到正确的名册目录。",
   "error.summonRequiresAgent": "当前上下文没有可用的 parent agent，无法召唤专家。",
   "error.providerMissing": "找不到子代理 provider：{provider}",
   "error.providerNoPersona": "provider {provider} 不支持 persona，无法注入专家人格。",
@@ -32,9 +32,9 @@ const ZH = {
 };
 
 const EN = {
-  "error.rootMissing": "T Expert expert directory is missing or unreadable: \"{root}\". Run ~/.t-team/sync.sh or configure a valid root.",
+  "error.rootMissing": "T Expert expert directory is missing or unreadable: \"{root}\". The plugin seeds its bundled roster there on first start; point root at the right place if you moved the data directory.",
   "error.rootNotDir": "T Expert expert root \"{root}\" is not a directory",
-  "error.catalogEmpty": "No experts (*.md) found under root \"{root}\". Run sync.sh first.",
+  "error.catalogEmpty": "No experts (*.md) found under root \"{root}\". Delete this empty directory so the plugin re-seeds on next start, or point root at the real roster.",
   "error.summonRequiresAgent": "No parent agent in this context; cannot summon an expert.",
   "error.providerMissing": "Subagent provider not found: {provider}",
   "error.providerNoPersona": "Provider {provider} does not support persona injection.",

package/lib/index.js

@@ -34,9 +34,10 @@ import { createSquadService } from "./squads.js";
 import { checkPlan } from "./plan-check.js";
 import { findTeamByCaptain } from "./teams/state.js";
 import { createUserMessage } from "@deepseek-ai/dsh-llm";
-// 路线 A：上游团队引擎已 vendor 进 lib/teams/（由 scripts/brand.mjs 从 vendor/dsh-agent-teams/upstream/
-// 改名生成：命令 /agent-teams → /t、工具 agent_teams_* → t_team_*），这里在 T专家 内部挂载它 ——
-// 安装 T专家 即自带团队引擎与团队面板，不再需要单独安装上游插件。
+// 内置团队引擎：随插件一起发布的品牌化产物在 lib/teams/ 下（由 scripts/brand.mjs 从
+// vendor/ 里的上游镜像改名生成），这里在 T专家 内部挂载它 ——
+// 安装 T专家 即自带团队引擎与团队面板，不再需要单独安装引擎插件。
+// 上游来源、版本与许可见 THIRD-PARTY-NOTICES 与 vendor/。
 import * as teamsEngine from "./teams/index.js";
 // 引擎自带的 /t 命令不注册（否则与 T专家 自己的 /t 撞名），但手势边界必须复用：
 // 它把 `/t --profile <小队> <目标>` 这条用户消息翻译成队长协议指令。
@@ -48,7 +49,14 @@ import { haltTeamWork } from "./teams/tools.js";
 export const name = NS;
 export const inject = ["tools", "subagents", "systemPrompt", "settings", "commands"];
 
-/** 插件配置；root 默认指向 T专家 的固定资产目录。 */
+/**
+ * 插件配置。
+ *
+ * 规范要求「部署可能取不同值的参数都必须是可被 cordis.yml 覆盖的 Config 字段」，
+ * 所以召唤上限/并发、任务长度上限、简介截断长度，以及团队引擎的
+ * stateDir / memberProvider / memberModel / maxMembers 与引擎配置路径都在这里；
+ * 模块级常量只保留协议常量与固定清单。
+ */
 export const Config = schema.object({
   root: schema.string().default(join(homedir(), ".t-team", "experts")),
   zhRoot: schema.string().default(join(homedir(), ".t-team", "zh")),
@@ -56,6 +64,24 @@ export const Config = schema.object({
   /** 留空 = 自动扫描 root 下所有含 .md 的分区目录（上游新增分区不必改配置/代码）。 */
   divisions: schema.array(schema.string()).default([]),
   maxDepth: schema.natural(),
+  /** 一次 summon_t_experts 最多召唤几位专家。 */
+  maxSummonBatch: schema.natural().min(1).default(8),
+  /** summon_t_experts 的并发度。 */
+  summonConcurrency: schema.natural().min(1).default(4),
+  /** 单个专家任务的最大字符数。 */
+  summonTaskMaxChars: schema.natural().min(1).default(8000),
+  /** list_t_experts 里简介的截断长度。 */
+  descriptionLimit: schema.natural().min(1).default(120),
+  /** 团队引擎配置（team-profiles.py 的产物）；留空则取 root 同级目录下的 t-team.config.json。 */
+  engineConfig: schema.string(),
+  /** 引擎的团队状态目录（工作区内，相对路径）。 */
+  stateDir: schema.string().default(".agent-teams"),
+  /** 队员子代理使用的 provider 名。 */
+  memberProvider: schema.string().default("spawn"),
+  /** 队员默认模型；留空 = 跟随队长。 */
+  memberModel: schema.string(),
+  /** 一支团队最多几名成员。 */
+  maxMembers: schema.natural().min(1).default(8),
 });
 
 /** 供 remote 服务读取名册的服务名。 */
@@ -67,10 +93,6 @@ export const TEAM_SERVICE = "tTeamTeams";
 /** 设置命名空间（= 插件名）。 */
 export const SETTINGS_NAMESPACE = NS;
 
-const SUMMON_EXPERTS_MAX = 8;
-const SUMMON_EXPERTS_CONCURRENCY = 4;
-const SUMMON_TASK_MAX_CHARS = 8000;
-const DESCRIPTION_LIMIT = 120;
 
 const settingsSchema = schema.object({
   enabled: schema.array(schema.string()).default([]),
@@ -84,10 +106,12 @@ export function apply(ctx, config) {
   // 必须在下面同步读取 t-team.config.json / teams.json 之前完成，否则首次安装会读到空配置。
   const seeded = seedData({ root: config.root, zhRoot: config.zhRoot });
   if (seeded.copied.length > 0) {
-    console.log(`[t-team] 已把包内名册快照播种到 ${dirname(config.root)}（${seeded.copied.join(", ")}）`);
+    ctx.logger?.info?.(`[t-team] 已把包内名册快照播种到 ${dirname(config.root)}（${seeded.copied.join(", ")}）`);
   }
   if (!seeded.ok) {
-    console.warn(`[t-team] 名册快照播种失败，将按已有数据继续：${seeded.error}`);
+    // 播种失败不当作致命：名册目录若因此缺失，第一次读名册会在 ensureReady() 里**响亮地**抛出
+    // （error.rootMissing），那才是最早可解析点。这里只保证失败一定会出现在日志里。
+    ctx.logger?.error?.(`[t-team] 名册快照播种失败，将按已有数据继续：${seeded.error}`);
   }
 
   // ---- 设置段（T专家 自己的命名空间，与其它插件不冲突）----
@@ -115,19 +139,28 @@ export function apply(ctx, config) {
   let loadError = null;
 
   /**
-   * 名册指纹：source.json 与各分区目录 + 中文侧车文件的 mtime。
-   * sync.sh / sync-zh.py 每次都会写这些文件，所以上游更新后**无需重启**即可自动重载；
-   * 目录 mtime 同时覆盖「新增/删除专家」。
+   * 名册指纹：source.json、各分区目录、以及中文侧车文件的 mtime。
+   *
+   * 要点：运行期读的中文正文路径是 `zh/<分区>/<slug>.md`（不是 `manual-bodies/`，那是
+   * 数据层的**输入**，由同步脚本合并后写进 `zh/<分区>/`）。所以 `zhRoot` 与每个
+   * `zh/<分区>/` 目录都必须进指纹 —— 否则「给某位专家**新增**一篇中文正文」这条最常见的
+   * 补译操作不会触发重载：该专家的 personaPathZh 一直是 undefined，召唤时只能读英文。
+   * （已在 verify 里用临时数据目录做过行为验证。）
    */
   async function fingerprint() {
     const mtimeOf = (path) => stat(path).then((info) => info.mtimeMs).catch(() => 0);
     const parts = await Promise.all([
       mtimeOf(config.root),
+      mtimeOf(config.zhRoot),
+      mtimeOf(join(config.zhRoot, "manual-bodies")),
       mtimeOf(join(dirname(config.root), "source.json")),
       mtimeOf(join(config.zhRoot, "names.json")),
       mtimeOf(join(config.zhRoot, "descriptions.json")),
       mtimeOf(join(config.zhRoot, "divisions.json")),
+      mtimeOf(join(config.zhRoot, "manual.json")),
       ...effectiveDivisions.map((division) => mtimeOf(join(config.root, division))),
+      ...effectiveDivisions.map((division) => mtimeOf(join(config.zhRoot, division))),
+      ...effectiveDivisions.map((division) => mtimeOf(join(config.zhRoot, "manual-bodies", division))),
     ]);
     return parts.join("|");
   }
@@ -219,8 +252,8 @@ export function apply(ctx, config) {
     const current = locale();
     const taskText = String(task ?? "").trim();
     if (taskText === "") throw new Error(t(current, "error.taskEmpty"));
-    if ([...taskText].length > SUMMON_TASK_MAX_CHARS) {
-      throw new Error(t(current, "error.taskTooLong", { limit: SUMMON_TASK_MAX_CHARS }));
+    if ([...taskText].length > config.summonTaskMaxChars) {
+      throw new Error(t(current, "error.taskTooLong", { limit: config.summonTaskMaxChars }));
     }
     if (exec.agent === undefined) throw new Error(t(current, "error.summonRequiresAgent"));
 
@@ -349,7 +382,7 @@ export function apply(ctx, config) {
               slug: expert.slug,
               name,
               emoji: expert.emoji,
-              description: truncate(description, DESCRIPTION_LIMIT),
+              description: truncate(description, config.descriptionLimit),
             };
           }),
         }));
@@ -386,7 +419,7 @@ export function apply(ctx, config) {
 
   ctx.tools.register(defineTool({
     name: "summon_t_experts",
-    description: "Summon multiple T专家 experts in parallel for one mission. At most 8 experts run with concurrency 4; successful answers are returned even when some fail.",
+    description: `Summon multiple T专家 experts in parallel for one mission. At most ${config.maxSummonBatch} experts run with concurrency ${config.summonConcurrency}; successful answers are returned even when some fail.`,
     parameters: {
       experts: {
         type: "array",
@@ -418,15 +451,15 @@ export function apply(ctx, config) {
       const current = locale();
       const specs = Array.isArray(args.experts) ? args.experts : [];
       if (specs.length === 0) throw new Error(t(current, "error.specsEmpty"));
-      if (specs.length > SUMMON_EXPERTS_MAX) {
-        throw new Error(t(current, "error.specsTooMany", { limit: SUMMON_EXPERTS_MAX }));
+      if (specs.length > config.maxSummonBatch) {
+        throw new Error(t(current, "error.specsTooMany", { limit: config.maxSummonBatch }));
       }
       specs.forEach((spec, index) => {
         if (spec === null || typeof spec !== "object" || typeof spec.expert !== "string" || typeof spec.task !== "string") {
           throw new Error(t(current, "error.specInvalid", { index }));
         }
       });
-      const results = await mapPool(specs, SUMMON_EXPERTS_CONCURRENCY, async (spec) => {
+      const results = await mapPool(specs, config.summonConcurrency, async (spec) => {
         try {
           const result = await runExpert(spec.expert, spec.task, exec);
           return { expert: result.expert, ok: true, answer: result.answer };
@@ -443,42 +476,81 @@ export function apply(ctx, config) {
     },
   }));
 
-  // ---- 内置团队引擎（vendor 自上游并品牌化；配置来自 team-profiles.py 生成的 JSON）----
-  // 配置文件名已随品牌改为 t-team.config.json，旧名 agent-teams.config.json 仍作为兜底读一次。
+  // ---- 内置团队引擎（vendor 自上游并品牌化；小队数据来自 team-profiles.py 生成的 JSON）----
+  // 配置路径与引擎标量都是 Config 字段（可从 cordis.yml 覆盖）：标量以 Config 为准，
+  // 数据文件只提供生成物本身（profiles / memberMaxDepth）——小队目录是数据，不是可调参数。
   const engineConfigDir = dirname(config.root);
-  const engineConfigPath = ["t-team.config.json", "agent-teams.config.json"]
-    .map((file) => join(engineConfigDir, file))
-    .find((candidate) => existsSync(candidate)) ?? join(engineConfigDir, "t-team.config.json");
+  const engineConfigPath = typeof config.engineConfig === "string" && config.engineConfig !== ""
+    ? config.engineConfig
+    : ["t-team.config.json", "agent-teams.config.json"]
+      .map((file) => join(engineConfigDir, file))
+      .find((candidate) => existsSync(candidate)) ?? join(engineConfigDir, "t-team.config.json");
   let engineConfig = {};
-  try {
-    const parsed = JSON.parse(readFileSync(engineConfigPath, "utf8"));
-    if (parsed !== null && typeof parsed === "object") engineConfig = parsed;
-  } catch {
-    console.warn(`[t-team] 未读到团队引擎配置 ${engineConfigPath}（跑一次 team-profiles.py 生成小队后即可用 /t 拉起团队）`);
+  let engineConfigDetail = "";
+  // 配置错误要响亮：**文件存在但内容不合法**属于自带的错配，直接让插件加载失败，
+  // 而不是带着空配置把团队功能静默降级。文件不存在是"还没生成小队"（自定义 root 时合法），
+  // 这种情况明确降级，并把原因送到所有可见面（日志 + /t + 下面的 engine-status 提示段）。
+  if (existsSync(engineConfigPath)) {
+    let parsed;
+    try {
+      parsed = JSON.parse(readFileSync(engineConfigPath, "utf8"));
+    } catch (error) {
+      throw new Error(`团队引擎配置无法解析：${engineConfigPath}（${error instanceof Error ? error.message : String(error)}）。它是 team-profiles.py 的产物，删掉后重跑一次即可重建。`);
+    }
+    if (parsed === null || typeof parsed !== "object" || Array.isArray(parsed)) {
+      throw new Error(`团队引擎配置必须是 JSON 对象：${engineConfigPath}`);
+    }
+    if (parsed.profiles !== undefined && (parsed.profiles === null || typeof parsed.profiles !== "object" || Array.isArray(parsed.profiles))) {
+      throw new Error(`团队引擎配置的 profiles 必须是对象：${engineConfigPath}`);
+    }
+    engineConfig = parsed;
+  } else {
+    engineConfigDetail = `找不到团队引擎配置 ${engineConfigPath}（跑一次 team-profiles.py 生成小队后即可用 /t 拉起团队）`;
   }
   // 引擎与名册解耦：引擎挂载失败（例如 Harness 子代理契约不匹配）时，
-  // T专家 的专家名册、@ 召唤、/t 列表仍然可用，只是团队功能不可用；失败原因会经 /t 报出来。
-  const engineState = { ok: false, detail: "" };
-  try {
-    ctx.plugin(teamsEngine, {
-      stateDir: typeof engineConfig.stateDir === "string" ? engineConfig.stateDir : ".agent-teams",
-      memberProvider: typeof engineConfig.memberProvider === "string" ? engineConfig.memberProvider : "spawn",
-      ...(engineConfig.memberModel === undefined ? {} : { memberModel: engineConfig.memberModel }),
-      ...(engineConfig.memberMaxDepth === undefined ? {} : { memberMaxDepth: engineConfig.memberMaxDepth }),
-      ...(engineConfig.maxMembers === undefined ? {} : { maxMembers: engineConfig.maxMembers }),
-      // 引擎自带命令必须关掉：T专家 自己注册 /t（带小队别名解析），否则两个同名命令相撞。
-      // 手势边界另外复用（见下），它是队长协议真正被触发的地方。
-      slashCommand: false,
-      profiles: engineConfig.profiles ?? {},
-    });
-    // 复用引擎导出的手势边界：把 `/t --profile <小队> <目标>` 这条用户消息翻成队长协议指令。
-    installTTeamGestureBoundary(ctx, () => engineConfig.profiles ?? {});
-    engineState.ok = true;
-  } catch (error) {
-    engineState.detail = error instanceof Error ? error.message : String(error);
-    console.error(`[t-team] 团队引擎挂载失败（专家名册功能不受影响）：${engineState.detail}`);
+  // T专家 的专家名册、@ 召唤、/t 列表仍然可用，只是团队功能不可用。
+  // 这是**已声明的降级**，不是静默跳过：原因会写进日志、经 /t 报出，并进系统提示段。
+  const engineState = { ok: false, detail: engineConfigDetail };
+  if (engineConfigDetail === "") {
+    try {
+      ctx.plugin(teamsEngine, {
+        stateDir: config.stateDir,
+        memberProvider: config.memberProvider,
+        ...(config.memberModel === undefined ? {} : { memberModel: config.memberModel }),
+        ...(engineConfig.memberMaxDepth === undefined ? {} : { memberMaxDepth: engineConfig.memberMaxDepth }),
+        maxMembers: config.maxMembers,
+        // 引擎自带命令必须关掉：T专家 自己注册 /t（带小队别名解析），否则两个同名命令相撞。
+        // 手势边界另外复用（见下），它是队长协议真正被触发的地方。
+        slashCommand: false,
+        profiles: engineConfig.profiles ?? {},
+      });
+      // 复用引擎导出的手势边界：把 `/t --profile <小队> <目标>` 这条用户消息翻成队长协议指令。
+      installTTeamGestureBoundary(ctx, () => engineConfig.profiles ?? {});
+      engineState.ok = true;
+    } catch (error) {
+      engineState.detail = error instanceof Error ? error.message : String(error);
+      ctx.logger?.error?.(`[t-team] 团队引擎挂载失败（专家名册功能不受影响）：${engineState.detail}`);
+    }
+  } else {
+    ctx.logger?.error?.(`[t-team] ${engineConfigDetail}`);
   }
 
+  // 已声明的降级也要**对模型可见**：否则"团队功能没了"这件事只留在日志里，
+  // 用户问起来模型只能说不知道 —— 那正是规范禁止的"静默跳过缺失的引用对象"。
+  ctx.systemPrompt.section({
+    name: "t-team:engine-status",
+    order: 120,
+    text: (context) => {
+      if (context.agent?.session?.header?.parentSession !== undefined) return "";
+      if (engineState.ok === true) return "";
+      return [
+        "## T专家 团队引擎当前不可用",
+        `团队功能（/t 建队、t_team_* 工具）现在不可用。原因：${engineState.detail}`,
+        "专家名册、@ 召唤与 summon_t_expert 不受影响。用户需要团队功能时，请原样转述上面的原因，不要假装能建队。",
+      ].join("\n");
+    },
+  });
+
   // ---- 小队定义服务（设置页「小队」标签用；写回 teams.json 后自动重跑 team-profiles.py）----
   const teamsFile = join(dirname(config.root), "teams.json");
   const squads = createSquadService({
@@ -504,6 +576,8 @@ export function apply(ctx, config) {
     teamId: team.teamId,
     name: team.name,
     workspace: team.workspace,
+    // 面板/设置页的「打开活动面板」要带 captainSessionId：活动面板是会话作用域的，
+    // 缺它就只能匹配当前会话的团队，别的会话（或历史归档）点按钮会静默无反应。
     captainSessionId: team.captainSessionId,
     phase: team.phase,
     halted: team.halted === true,

package/lib/plan-check.js

@@ -77,7 +77,9 @@ export function checkPlan(team, tasks) {
   const sim = { ...(team ?? {}), tasks: [...existing] };
   const taken = new Set(existing.map((task) => task.id));
   const labels = new Map(); // 本批 id → 模拟 id
-  let counter = existing.length;
+  // 引擎分配的是 `t${team.taskSeq + 1}` 并随后自增（不是"现有任务条数"）。两者只在
+  // taskSeq === tasks.length 时才一致 —— 有任务被删除/取消过就会分叉，所以以 taskSeq 为准。
+  let counter = Number.isSafeInteger(team?.taskSeq) ? team.taskSeq : existing.length;
   const report = [];
 
   proposed.forEach((raw, index) => {

package/lib/teams/capabilities.js

@@ -3,7 +3,7 @@ import { join } from 'node:path';
 import { readTeamSync, readRetiredMemberIdsSync } from "./state.js";
 import { MEMBER_TOOL_NAMES, TEAM_TOOL_NAMES } from "./tool-names.js";
 export const TEAM_ACTIVATION_PROMPT = 'T Team （T专家 团队） provides multi-agent team collaboration. Apply these rules when the user requests it (including /t-team) or when continuing an existing team. Mentioning, quoting, discussing, or declining T Team alone is not a request to start work.';
-export const TEAM_MEMBER_PROMPT = 'You are an T Team member. Follow your assigned member persona and task contract. Use t_team_claim_task, t_team_update_task, t_team_send_message and t_team_status for your own work. Include the current attempt_id in updates; report completion or failure to the captain. Do not create, approve, edit or resume a team. If your durable membership is unavailable, report that to the parent instead of creating a replacement.';
+export const TEAM_MEMBER_PROMPT = 'You are a T Team member. Follow your assigned member persona and task contract. Use t_team_claim_task, t_team_update_task, t_team_send_message and t_team_status for your own work. Include the current attempt_id in updates; report completion or failure to the captain. Do not create, approve, edit or resume a team. If your durable membership is unavailable, report that to the parent instead of creating a replacement.';
 function stateRoot(agent, config) {
     return join(agent.session.header.cwd ?? process.cwd(), config.stateDir);
 }

package/lib/teams/index.js

@@ -91,7 +91,7 @@ export function usageSectionText(toolNames, profilesText = '') {
 1. Inspect current team state when needed, using t_team_status. Continue existing work without duplicating its roster/tasks. Create only when no current team exists, with the user's goal as description and approval="required"; automatic approval requires an explicit request to run immediately. Staged plans never spawn or schedule work.
 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 .t-team state files or plugin source code to revise plans. Discard does not authorize a replacement.
+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.
 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.

package/lib/teams/quality-gates.js

@@ -119,7 +119,7 @@ function isDefaultExcluded(path) {
     const base = segments[segments.length - 1] ?? '';
     if (segments[0] === '.git' || segments[0] === '.dsh')
         return true;
-    if (base === '.env' || base.startsWith('.env.'))
+    if (base === '.env' || (base.startsWith('.env.') && !['.example', '.sample', '.template', '.dist'].some(suffix => base.endsWith(suffix))))
         return true;
     if (segments.includes('secrets'))
         return true;
@@ -253,9 +253,7 @@ export function validateCreateTask(team, input) {
                 continue;
             if (!OPEN_STATUSES.includes(other.status))
                 continue;
-            if (dependencies.includes(other.id) || other.dependencies.includes('pending-new'))
-                continue;
-            if (dependencies.includes(other.id))
+            if (dependencyClosureContains(team.tasks, dependencies, other.id))
                 continue;
             const overlap = inScopeOverlap(input.inScope, other.inScope);
             if (overlap.length > 0) {
@@ -280,7 +278,7 @@ export function validateCreateTask(team, input) {
         }
     }
     const nextTeam = team.halted === true && input.resume === true
-        ? { ...team, halted: false, haltedAt: undefined }
+        ? { ...team, halted: false, haltedAt: undefined, escalated: false }
         : team;
     return {
         ok: true,
@@ -571,6 +569,7 @@ export function resumeTeamState(team, reason) {
             ...team,
             halted: false,
             haltedAt: undefined,
+            escalated: false,
         },
     };
 }

package/lib/teams/tools.js

@@ -710,7 +710,7 @@ export function registerTTeamTools(ctx, config) {
     }));
     ctx.tools.register(defineTool({
         name: 't_team_edit_plan',
-        description: 'Atomically revise the current staged T Team plan without spawning members or scheduling tasks. Use this when the user continues chatting to change a plan that is waiting for approval. Submit dependent edits in order (update downstream dependencies or assignees, then remove tasks, then remove unused members). Never inspect or edit .t-team state files or plugin source code to revise a plan.',
+        description: 'Atomically revise the current staged T Team plan without spawning members or scheduling tasks. Use this when the user continues chatting to change a plan that is waiting for approval. Submit dependent edits in order (update downstream dependencies or assignees, then remove tasks, then remove unused members). Never inspect or edit the T Team state directory in the workspace or plugin source code to revise a plan.',
         parameters: {
             operations: {
                 type: 'array',
@@ -1005,7 +1005,7 @@ export function registerTTeamTools(ctx, config) {
                 const member = requireMember(fresh, args.name);
                 const requeued = [];
                 for (const task of fresh.tasks) {
-                    if (task.assignee !== member.name || task.status === 'completed')
+                    if (task.assignee !== member.name || TERMINAL_TASK_STATUSES.includes(task.status))
                         continue;
                     invalidateTaskAttempt(task);
                     task.reassigning = false;
@@ -1508,10 +1508,13 @@ export function registerTTeamTools(ctx, config) {
                     throw new Error(`task ${task.id} is owned by member "${task.assignee}"; call t_team_reassign_task with assignee="captain" before takeover`);
                 }
                 if (identity.kind === 'member') {
+                    if (task.reassigning === true) {
+                        throw new Error(`task ${task.id} is being reassigned; stop work and wait for the fresh assignment`);
+                    }
                     if (task.assignee !== identity.name) {
                         throw new Error(`task ${task.id} is assigned to "${task.assignee ?? 'nobody'}", not you`);
                     }
-                    if (task.attemptId !== undefined && args.attempt_id !== task.attemptId) {
+                    if (task.attemptId !== args.attempt_id) {
                         throw new Error(`stale attempt for task ${task.id}: expected the current attempt_id; stop work and request fresh assignment`);
                     }
                 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-t-expert",
-  "version": "0.1.1",
+  "version": "0.2.2",
   "type": "module",
   "description": "T Expert — a 279-expert, 18-division roster with full Chinese translations, as a standalone DeepSeek Harness plugin, with a built-in multi-agent team engine (T Team).",
   "license": "MIT",
@@ -45,7 +45,10 @@
     "cordis.patch.yml",
     "README.md",
     "LICENSE",
-    "THIRD-PARTY-NOTICES"
+    "THIRD-PARTY-NOTICES",
+    "vendor/dsh-agent-teams/LICENSE",
+    "vendor/dsh-agent-teams/VENDOR.md",
+    "vendor/third-party-licenses"
   ],
   "dsh": {
     "bundle": {
@@ -53,7 +56,6 @@
     },
     "client": {
       "inject": [
-        "@deepseek-ai/dsh-client-runtime",
         "@deepseek-ai/dsh-client-connection",
         "@deepseek-ai/dsh-client-locale",
         "@deepseek-ai/dsh-api-remotes",
@@ -65,11 +67,11 @@
     }
   },
   "scripts": {
-    "build": "node scripts/brand.mjs && node scripts/build-client.mjs",
-    "verify": "node scripts/verify.mjs",
-    "brand": "node scripts/brand.mjs",
-    "sync-data": "node scripts/sync-data.mjs",
-    "prepublishOnly": "npm run build && npm run verify && node scripts/sync-data.mjs --check"
+    "build": "node ../brand.mjs && node ../build-client.mjs",
+    "verify": "node ../verify.mjs",
+    "brand": "node ../brand.mjs",
+    "sync-data": "node ../sync-data.mjs",
+    "prepublishOnly": "npm run build && npm run verify && node ../sync-data.mjs --check"
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
@@ -85,7 +87,6 @@
     "@deepseek-ai/dsh-llm": "0.1.5-rc.1 || 0.1.5-rc.2",
     "@deepseek-ai/dsh-session": "0.1.5-rc.1 || 0.1.5-rc.2",
     "@deepseek-ai/dsh-settings": "0.1.5-rc.1 || 0.1.5-rc.2",
-    "@deepseek-ai/dsh-skill": "0.1.5-rc.1 || 0.1.5-rc.2",
     "@deepseek-ai/dsh-subagent": "0.1.5-rc.1 || 0.1.5-rc.2",
     "@deepseek-ai/dsh-system-prompt": "0.1.5-rc.1 || 0.1.5-rc.2",
     "@deepseek-ai/dsh-tools": "0.1.5-rc.1 || 0.1.5-rc.2",
@@ -133,9 +134,6 @@
     "@deepseek-ai/dsh-settings": {
       "optional": true
     },
-    "@deepseek-ai/dsh-skill": {
-      "optional": true
-    },
     "@deepseek-ai/dsh-subagent": {
       "optional": true
     },

package/vendor/dsh-agent-teams/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 程序员阿江(Relakkes)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/vendor/dsh-agent-teams/VENDOR.md

@@ -0,0 +1,53 @@
+# vendor: @nanmicoder/dsh-agent-teams（T专家 内置团队引擎）
+
+路线 A：把 AgentTeams 的团队引擎**原样**内置进 T专家，安装后不再需要单独安装 AgentTeams。
+
+| 项 | 值 |
+| --- | --- |
+| 上游仓库 | https://github.com/NanmiCoder/dsh-agent-teams |
+| 上游版本 | `0.1.17-rc.1` |
+| 仓库 commit | `18fba6211fc3aac305fc9bb1c8a7faaf7273137a` |
+| 同步来源目录 | `~/.dsh/profiles/desktop/node_modules/@nanmicoder/dsh-agent-teams` |
+| 同步时间 | 2026-09-11 18:31:14 +0800 |
+| 许可 | MIT（见同目录 LICENSE；本目录文件保持逐字节原样） |
+
+## 同步进来的文件
+
+```
+lib/teams/capabilities.js              4943 bytes
+lib/teams/command.js                   8378 bytes
+lib/teams/event-types.js                569 bytes
+lib/teams/events.js                    2827 bytes
+lib/teams/harness-compat.js            8733 bytes
+lib/teams/index.js                    27236 bytes
+lib/teams/members.js                  33124 bytes
+lib/teams/profiles.js                 23215 bytes
+lib/teams/quality-gates.js            37323 bytes
+lib/teams/scheduler.js                24563 bytes
+lib/teams/snapshot.js                  7725 bytes
+lib/teams/state.js                    38289 bytes
+lib/teams/tool-names.js                 708 bytes
+lib/teams/tools.js                   127546 bytes
+lib/teams/types.js                      780 bytes
+lib/teams/web-routes.js                3328 bytes
+vendor/dsh-agent-teams/client.bundle.txt    197722 bytes
+```
+
+## T专家 的改动点（都在我们的代码里，vendor 文件不动）
+
+1. host：`lib/index.js` 里 `ctx.plugin(engineNamespace, engineConfig)` 内部挂载引擎，配置来自
+   `~/.t-team/t-team.config.json`（由 `team-profiles.py` 依据 `teams.json` 生成）。
+2. client：`src/client.jsx` 在 factory 里临时截获 `window.__ModuleLoader__.load`，取出上游 client bundle
+   注册的 factory，用我们自己的 `require` 物化它，再调用它的 `apply(ctx)` —— 于是团队树/草案面板与
+   T专家 的设置页共用同一个客户端模块（同一个注册 id，DSH 只允许一个包注册一个 id）。
+3. 工具名保持上游的 `agent_teams_*`，命令保持 `/agent-teams`；T专家 另加 `/t` 短命令与专家名册工具。
+
+## 更新上游
+
+```bash
+bash ~/web/t-team/tz.sh 13                  # 从已安装的包同步（先 dshmarket/pnpm 升到新版）
+bash ~/web/t-team/tz.sh engine-sync --check # 只看差异
+bash ~/web/t-team/tz.sh engine-sync --from DIR --clone ~/.t-team/vendor/dsh-agent-teams
+```
+
+同步后：`bash ~/web/t-team/tz.sh 10`（自检）→ `tz.sh 12`（构建）→ `tz.sh 8`（安装）→ 重启 DSH Desktop。

package/vendor/third-party-licenses/README.md

@@ -0,0 +1,22 @@
+# 第三方许可文本（随包分发）
+
+本目录只放**随包分发的第三方内容**的完整许可证文本，以便再分发时履行 MIT 的
+"保留版权声明与许可声明"义务。说明与署名见包根目录的 `THIRD-PARTY-NOTICES`。
+
+| 文件 | 覆盖的随包内容 | 来源 |
+| --- | --- | --- |
+| `agency-agents.LICENSE` | `data/experts/`（18 分区 / 279 位专家的逐字节镜像） | The Agency / AgentLand 名册快照，MIT |
+| `agency-agents-zh.LICENSE` | `data/zh/` 中的中文名字、简介与人格正文 | `agency-agents-zh` 中文翻译与本地化资产，MIT |
+
+两份文本都是从实际用于生成快照的来源包内**逐字节复制**的，未经改写：
+
+```
+<安装的 @michengai/dsh-agency-agents>/assets/agency-agents/LICENSE
+<安装的 @michengai/dsh-agency-agents>/assets/agency-agents-zh/LICENSE
+```
+
+`@michengai/dsh-agency-agents` 自身的 TypeScript 源码与构建脚本是 Apache-2.0，
+但**本插件不打包它的任何代码**，只用到了上面这两份 MIT 授权的资产，
+因此这里只需分发这两份 MIT 文本。
+
+内置团队引擎的许可证在 `../dsh-agent-teams/LICENSE`（同样随包分发）。

package/vendor/third-party-licenses/agency-agents-zh.LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2025 Michael Sitarzewski (original English version)
+Copyright (c) 2026 jnMetaCode (Chinese translation and localization)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/vendor/third-party-licenses/agency-agents.LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 AgentLand Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.