@sema-agent/server 7.27.0 → 7.28.0-rc.1

package/USAGE.md

@@ -282,7 +282,7 @@ FLEET_ADVERTISE_ADDRESS=http://<本机可达IP>:8090  # 可选:设了才启 flee
 - **灰度姿势**(配置控制面 AI 建议):先 `SEMA_REGISTRY_DRY_RUN=true` 起一轮,看日志 `sema_registry_dry_run`(中心给的 models/roles/teams + 会否覆盖 default、per-model apiKeyEnv)对得上 env 再去掉该 flag 真正 apply。
 - 拉取**只读、只取逻辑配置**(模型名册/角色/团队);密钥/网关仍在本服务 env(中心只发 env-**名** 引用,不发密钥值)。models/roles 改动需重启生效,teams 60s 热刷。回滚=去掉 `SEMA_REGISTRY_URL` 即纯 env。
 - **仅 `/v1/tasks`(同步)+ `/v1/runs`(异步)**——`/v1/tasks/stream` 不支持(多次尝试非单流,400)。与 `verify` **互斥**(同时给 → 400)。
-- 成本上界 = 任务的 `maxCostUsd`(防冷重跑税)。**三条 core 警示**:① 每档**冷重跑**重付输入成本(便宜档常过才划算);② 门收到**未脱敏**输出(自定义门转发外部 verifier 要脱敏);③ **写工具会跑 N 次**——**只用于只读/幂等任务**(每次升级整任务重跑)。开放式任务(找全 bug/文笔)没有可判定 oracle、级联会空转,那种用 `team`(广度对抗)而非级联(深度阶梯)。
+- 成本上界 = 任务的 `maxCostUsd`(防冷重跑税)。**三条 core 警示**:① 每档**冷重跑**重付输入成本(便宜档常过才划算);② 门收到**未脱敏**输出(自定义门转发外部 verifier 要脱敏);③ **写工具会跑 N 次**——**只用于只读/幂等任务**(每次升级整任务重跑)。开放式任务(找全 bug/文笔)没有可判定 oracle、级联会空转,那种用 `discuss`(广度对抗)而非级联(深度阶梯)。
 
 **可选 — AskUserQuestion 的裁量窗(问活人的三个帽子)**
 ```bash
@@ -510,7 +510,7 @@ SEMA_PARENT_PID=$$      # 壳把自己的 pid 传给它 spawn 出来的引擎
 | `sessionId` | — | 续聊:带上次返回的 `sessionId`,服务端自动 wake 历史 |
 | `images` | — | 图文输入 `[{data,mimeType}|{url}]`(模型需支持 vision) |
 | `attachmentIds` | — | D-1 通用文件上传(1.289+):先 `POST /v1/attachments?name=…`(raw body,content-type=mime)拿句柄,提交时引用 ≤16 个;文件物化到执行环境工作目录 `attachments/` 下,objective 尾部自动追加文件清单(内容不进会话流)。单文件缺省 ≤32 MiB(`ATTACHMENT_MAX_BYTES`);可配 mime 白名单(`ATTACHMENT_MIME_ALLOWLIST` CSV,缺省不限);上传后未引用的按 `ATTACHMENT_UNBOUND_TTL_MS`(缺省 24h)回收。**云形态(tidb/pg)字节本体存对象存储——MinIO 必配**(`MINIO_ENDPOINT/MINIO_ACCESS_KEY/MINIO_SECRET_KEY`,与快照 lane 同一组变量),未配则附件面 501;local 形走本地文件店。 |
-| `scenario` | — | `default`(默认)/ `code-review`(见 §5)/ `scan`(同 §5 的 repo 只读工具但**中性无框架提示词**——objective+中心下发 skill 全权主导输出,OA 扫描类用;与 `code-review`/`team` 同属 clone-free 无执行环境场景,见 §5 末)/ **配置控制面可声明任意新场景**(`{name, toolset: none\|repo-readonly, prompt?}`,组合即配置、能力钉死在部署;restart-to-apply;center 可覆盖内建名,boot 日志 `config_center_scenarios.shadowsBuiltin` 可审计) |
+| `scenario` | — | `default`(默认)/ `code-review`(见 §5)/ `scan`(同 §5 的 repo 只读工具但**中性无框架提示词**——objective+中心下发 skill 全权主导输出,OA 扫描类用;与 `code-review`/`discuss` 同属 clone-free 无执行环境场景,见 §5 末)/ **配置控制面可声明任意新场景**(`{name, toolset: none\|repo-readonly, prompt?}`,组合即配置、能力钉死在部署;restart-to-apply;center 可覆盖内建名,boot 日志 `config_center_scenarios.shadowsBuiltin` 可审计) |
 | `repo` / `council` / `debate` | — | `repo` 为 `code-review`/`scan` 必填;`council`/`debate` 仅 `code-review`,见 §5 |
 | ~~model / tools / prompt~~ | 🚫 | **不接受**——服务端注入 |
 
@@ -597,7 +597,7 @@ curl -s http://<host>:8090/v1/runs/<taskId> -H 'x-agent-principal: user:42'   #
 > (仅 contents/pull-requests 只读)。未知词拒启;`GIT_API_BASEURL` 指向 github.com 族而 kind 仍是
 > gitea 也拒启并指路(Gitea 形状对 GitHub 恒 404,启动即报优于运行时逐调用 404)。
 
-> **升级注记(7.7.0)**:本版起 `code-review` / `scan` / `team` / `toolset: repo-readonly|none` 的场景改跑
+> **升级注记(7.7.0)**:本版起 `code-review` / `scan` / `discuss`(7.28.0 前叫 `team`)/ `toolset: repo-readonly|none` 的场景改跑
 > 无执行环境的引擎。**升级前**若还有这些场景的 durable 挂起任务(需同时满足:配了 `REMOTE_EXEC`、开了
 > `DURABLE_APPROVAL`、任务已 park),它们在新版上续跑会以 409 `checkpoint.unsupported_version` 响亮失败
 > (run 行落 failed 并释放会话,不会占住会话)——重新提交该任务即可。升级前排空这类挂起任务可完全避免。
@@ -607,7 +607,7 @@ curl -s http://<host>:8090/v1/runs/<taskId> -H 'x-agent-principal: user:42'   #
 模型看到的工具面只有声明的只读仓库工具(`repo_tree` / `repo_read_file` / `repo_pull_diff`)加 `Now`,
 **没有** `Bash` / `Edit` / `Write` / `Read` 等落盘工具,不 clone、不写盘、不起沙箱。
 即使部署配了 `REMOTE_EXEC`(host/e2b/k8s/ssh/adb/local-docker)也如此:执行环境只属于 `default` / `code`
-这类需要动手的场景。`team` 场景同理(协调者只调 `run_team`,成员是纯讨论人格)。
+这类需要动手的场景。`discuss` 场景同理(协调者只调 `run_discussion`,成员是纯讨论人格)。
 
 ## 6. 逐 token 直播(同步流式,连接挂着)
 ```bash

package/dist/boot/resolve-spec.js

@@ -118,7 +118,9 @@ export function createResolveSpec(ctx) {
         // body.scenario is bounded to the allowlist — outside ⇒ typed 400 `scenario_not_allowed`). The ruling
         // {scenario, allowlist} is center-RESOLVED and rides the caps view (TTL-cached, same fetch as runtimeCaps);
         // no center / dry-run / anonymous / older center / caps blip ⇒ undefined ⇒ legacy body-or-default chain.
-        const requested = gateScenarioRequest(await principalCaps?.scenarioRuling(auth?.principal), body.scenario, config.defaultScenario, Object.keys(scenarios));
+        // #273 alias:`gateScenarioRequest` 是 HTTP lane 的唯一归一点(旧名 team → discuss,响亮 warn);
+        // 此后 `scenarioName` 只可能是现役主名,下游判据点一律按主名写(禁双名判)。
+        const requested = gateScenarioRequest(await principalCaps?.scenarioRuling(auth?.principal), body.scenario, config.defaultScenario, Object.keys(scenarios), logger);
         // per-principal execution-lane policy — this worker's lane is a
         // PROCESS identity (REMOTE_EXEC boot wiring, no per-task switch), so admission is the gate: lane ∉
         // allowedLanes ⇒ typed 403 `execution_lane_not_allowed`. Same caps car as the scenario ruling (zero extra
@@ -714,7 +716,7 @@ export function createResolveSpec(ctx) {
             // 退役键(timeoutSec/deadline 族)DROP 必须留痕:task_limits_legacy_key_dropped 带被丢键与最终生效墙钟
             // (null=整任务无墙——单用户 turnkey 无 env 墙时的真后果;多租=被延到租户墙)。
             ...(() => {
-                const limits = resolveTaskLimits(body.limits, taskLimitCaps, taskTimeoutSec, config.requirePrincipal, body.council === true || body.debate === true || scenarioName === "team", (event, fields) => logger.warn(event, { ...fields, sessionId: auth?.sessionId ?? null }));
+                const limits = resolveTaskLimits(body.limits, taskLimitCaps, taskTimeoutSec, config.requirePrincipal, body.council === true || body.debate === true || scenarioName === "discuss", (event, fields) => logger.warn(event, { ...fields, sessionId: auth?.sessionId ?? null }));
                 // [1301]③ config catalog server 半场:env 封顶不再是「五层五值互不知情」的暗手——每个真在场
                 // 的运营方旋钮以 configOverrides 声明进 spec(advisory,core 折进 config.assembled 的
                 // overrideReasons;「谁设的顶」变成读帧不考古)。只声明 SET 了的键(缺省不设=不污染帧)。
@@ -1284,7 +1286,7 @@ export function createResolveSpec(ctx) {
                 isolatedExecEnv,
                 hasExecutionEnv: config.remoteExec != null,
                 ...(config.autonomy ? { autonomy: config.autonomy } : {}),
-                explicitTeam: body.council === true || body.debate === true || scenarioName === "team",
+                explicitTeam: body.council === true || body.debate === true || scenarioName === "discuss",
             });
             logger.info("orchestration_routed", { mode: decision.mode, reason: decision.reason, sessionId: auth?.sessionId ?? null });
             if (decision.mode === "supervisor") {

package/dist/capabilities/center-prompts.js

@@ -21,6 +21,7 @@
  */
 import { verifyPromptArtifact } from "@sema-agent/core";
 import { CORE_ENGINE_VERSION } from "../prompts-domain-validate.js";
+import { scenarioConfigKeys } from "./scenario-alias.js";
 import { SHA256_HEX_RE } from "../digest-form.js";
 import { recordFailOpen } from "../observability/fail-open.js";
 /** 判形半场(validateCenterPrompts/validatePromptsDomain/CORE_ENGINE_VERSION 及两 interface)已下沉到
@@ -115,7 +116,7 @@ export async function applyCatalogToSource(source, next, prev, log, phase) {
  * (F4:空替换集非 v1 语义),所以这里恒有非空声明——恒返回 provider(center-wins 无死分支)。
  */
 export function centerPromptProvider(prompts, scenarioName) {
-    const decls = prompts.scenarioOverrides?.[scenarioName] ?? prompts.sections;
+    const decls = scenarioDecls(prompts, scenarioName);
     // 声明数组在候选采用时已判形+冻结(main.ts ref 整体替换,数组不原位变异)——闭包直接引用,core 侧
     // 1.315 还有声明边界快照(getter 无法让「验过的」≠「发出的」)。
     return { stableBlocks: () => decls };
@@ -127,7 +128,25 @@ export function centerPromptProvider(prompts, scenarioName) {
  *  [1057]①f 的「server 不做语义复检」不动:这不是复检语义,是为 capabilities.appendSystemPrompt 的诚实面
  *  探 core 会走哪条臂。 */
 export function centerIdentityAssembled(prompts, scenarioName, isAssembled) {
-    const decls = prompts.scenarioOverrides?.[scenarioName] ?? prompts.sections;
-    return decls.some((d) => d.slot === "identity" && isAssembled(d.text));
+    return scenarioDecls(prompts, scenarioName).some((d) => d.slot === "identity" && isAssembled(d.text));
+}
+/** 选包的**唯一**实现(两个消费面共用,免得「谁赢」这条优先序有两份副本)。
+ *  #273 alias 窗:`scenarioOverrides` 的键写**旧场景名**时同样命中(`scenarioConfigKeys`,主名优先)——
+ *  运维已经写好的 per-scenario 提示词包不因改名当版静默失效。
+ *  #193 P2-13 同族守卫(顺手补,收拢时发现):`Record` 的裸索引对原型链键会取到 `Object.prototype` 上的
+ *  成员,而场景名词法 `SCENARIO_NAME_RE` 恰好**允许** `constructor` 这种名字 ⇒ 旧写法会把一个函数当
+ *  声明数组返回,下游 `.some(...)` 直接 TypeError。own-property 判定后这条路不存在。 */
+function scenarioDecls(prompts, scenarioName) {
+    const overrides = prompts.scenarioOverrides;
+    if (overrides) {
+        for (const key of scenarioConfigKeys(scenarioName)) {
+            if (Object.hasOwn(overrides, key)) {
+                const hit = overrides[key];
+                if (hit)
+                    return hit;
+            }
+        }
+    }
+    return prompts.sections;
 }
 //# sourceMappingURL=center-prompts.js.map

package/dist/capabilities/scenario-alias.d.ts

@@ -0,0 +1,27 @@
+import type { Logger } from "../observability/logger.js";
+export declare const SCENARIO_ALIASES: Readonly<Record<string, string>>;
+/**
+ * 把请求/配置里的场景名归一到现役主名。
+ *
+ *  - `known` 里**真有**这个名字 ⇒ 原样返回(live 定义优先于 alias)。⚠️ 窗内 center **无法**用旧名
+ *    另立场景:`centerScenarios` 把 alias 名当**保留名**响亮跳过(理由见那里——否则请求面归影子场景、
+ *    而按场景键的配置在 alias 窗里两边都算,MCP/A2A 会静默漏进主名的 roster)。所以这一支今天只是
+ *    纵深防御(万一将来有别的路径往表里塞同名场景,它至少不会被别名劫持)。
+ *  - 否则命中 alias 表 ⇒ 返回主名 + 响亮 `scenario_alias_deprecated`(每 logger 每旧名一次)。
+ *  - 都不命中 ⇒ 原样返回(未知名的处置归调用方:请求面 typed 400,指派面走 unknown→default 回退)。
+ */
+export declare function canonicalScenarioName(name: string, known: readonly string[] | undefined, logger?: Logger): string;
+/**
+ * 「为场景 `name` 查按场景键的运维配置时,应命中哪些键」= 主名 + 其过渡期旧名。
+ *
+ * 🔴 **无二义的前提**(codex 对抗复审 [high] 的修法):旧名在窗内是**保留名** —— `centerScenarios` /
+ * `centerScenarioDetails` 拒绝任何以 alias 名声明的 center 场景,所以「标了旧名的配置」在本部署里
+ * 只可能是冲着(改名前的)主名去的,不存在第二个属主可漏。二义在源头掐掉,而不是在这四个取用口
+ * 各塞一份 live 名册判据(那才是「同一语义多个属主」)。
+ *
+ * 请求面归一之后,运维**已写好的**旧名配置(skill frontmatter 的 `scenarios:`、center mcp/a2a 的
+ * `scenarios`、center prompts 的 `scenarioOverrides`)若不再被命中,就会在改名当版**静默失效**
+ * —— 静默是这里唯一不可接受的形态,所以窗内两名皆认。窗撤销时随 {@link SCENARIO_ALIASES} 一起塌回单键。
+ */
+export declare function scenarioConfigKeys(name: string): readonly string[];
+//# sourceMappingURL=scenario-alias.d.ts.map

package/dist/capabilities/scenario-alias.js

@@ -0,0 +1,61 @@
+// ── #273 / C-R14 场景名 alias 过渡窗(clay 直裁 [4123],server 表态 [4127])──────────────────────
+//
+// 「team」一词全生态只指 agent-teams(持久具名团队);一次性多 agent 讨论一律叫「discuss」。本仓的
+// `team` 场景正中射程 ⇒ 主名改 `discuss`,旧名保**一版**入口别名。
+//
+// 🔴 **单点解析**:归一发生在 {@link canonicalScenarioName},由 {@link gateScenarioRequest}(HTTP lane)
+// 与 run-local 各调**一次**;此后整条下游(`scenarioName` 的每个判据点、trace 字段、skills/mcp/a2a/
+// prompts 的按场景过滤)只见现役主名。**禁**在判据点上一处一处加双名判 —— 改名批最经典的漏改形就是
+// 「改了三处、漏了第四处」,而漏掉的那处会静默按 default 跑(讨论任务被 2400s 墙钟砍腰之类)。
+//
+// ⏳ 窗一版:下一 minor 删本表 + team.ts 的 `run_team` 别名工具(两处同批删,发车帖点名壳/center)。
+export const SCENARIO_ALIASES = Object.freeze({ team: "discuss" });
+/** 一次性 deprecation warn 的去重位:按 logger 实例记已喊过的旧名。部署的 logger 是进程单例 ⇒ 每个
+ *  旧名每进程喊一次(不是每请求刷屏);测试各建各的 logger ⇒ 每格都看得见自己的那一声。 */
+const aliasWarned = new WeakMap();
+/**
+ * 把请求/配置里的场景名归一到现役主名。
+ *
+ *  - `known` 里**真有**这个名字 ⇒ 原样返回(live 定义优先于 alias)。⚠️ 窗内 center **无法**用旧名
+ *    另立场景:`centerScenarios` 把 alias 名当**保留名**响亮跳过(理由见那里——否则请求面归影子场景、
+ *    而按场景键的配置在 alias 窗里两边都算,MCP/A2A 会静默漏进主名的 roster)。所以这一支今天只是
+ *    纵深防御(万一将来有别的路径往表里塞同名场景,它至少不会被别名劫持)。
+ *  - 否则命中 alias 表 ⇒ 返回主名 + 响亮 `scenario_alias_deprecated`(每 logger 每旧名一次)。
+ *  - 都不命中 ⇒ 原样返回(未知名的处置归调用方:请求面 typed 400,指派面走 unknown→default 回退)。
+ */
+export function canonicalScenarioName(name, known, logger) {
+    if (known?.includes(name))
+        return name;
+    if (!Object.hasOwn(SCENARIO_ALIASES, name))
+        return name;
+    const resolved = SCENARIO_ALIASES[name];
+    if (resolved === undefined)
+        return name;
+    if (logger) {
+        let seen = aliasWarned.get(logger);
+        if (!seen)
+            aliasWarned.set(logger, (seen = new Set()));
+        if (!seen.has(name)) {
+            seen.add(name);
+            logger.warn("scenario_alias_deprecated", { requested: name, resolved });
+        }
+    }
+    return resolved;
+}
+/**
+ * 「为场景 `name` 查按场景键的运维配置时,应命中哪些键」= 主名 + 其过渡期旧名。
+ *
+ * 🔴 **无二义的前提**(codex 对抗复审 [high] 的修法):旧名在窗内是**保留名** —— `centerScenarios` /
+ * `centerScenarioDetails` 拒绝任何以 alias 名声明的 center 场景,所以「标了旧名的配置」在本部署里
+ * 只可能是冲着(改名前的)主名去的,不存在第二个属主可漏。二义在源头掐掉,而不是在这四个取用口
+ * 各塞一份 live 名册判据(那才是「同一语义多个属主」)。
+ *
+ * 请求面归一之后,运维**已写好的**旧名配置(skill frontmatter 的 `scenarios:`、center mcp/a2a 的
+ * `scenarios`、center prompts 的 `scenarioOverrides`)若不再被命中,就会在改名当版**静默失效**
+ * —— 静默是这里唯一不可接受的形态,所以窗内两名皆认。窗撤销时随 {@link SCENARIO_ALIASES} 一起塌回单键。
+ */
+export function scenarioConfigKeys(name) {
+    const olds = Object.entries(SCENARIO_ALIASES).filter(([, to]) => to === name).map(([from]) => from);
+    return olds.length > 0 ? [name, ...olds] : [name];
+}
+//# sourceMappingURL=scenario-alias.js.map

package/dist/capabilities/scenarios.d.ts

@@ -4,6 +4,7 @@ import type { Logger } from "../observability/logger.js";
 import { type RepoReadClient } from "./repo-tools.js";
 import { type LoadedSkill } from "./skills.js";
 import { type ScenarioHands } from "./hands-lane.js";
+export { SCENARIO_ALIASES, canonicalScenarioName, scenarioConfigKeys } from "./scenario-alias.js";
 /**
  * Scenario routing — a deployment serves many scenarios from one image. Each request's `scenario`
  * selects a pre-wired capability bundle: tools (incl. subagent roster) + a whole-harness prompt +
@@ -39,7 +40,7 @@ export interface ScenarioDeps {
     subRunner: Runner;
     /**
      * #196:`subRunner` 的无手孪生 —— 同 deps,唯独不挂 `executionEnvFactory`。hands=none 的场景把它交给
-     * 自己造的子任务工具(council 的 lens/arbiter、team 的成员/synthesizer):那些子任务只该读仓库/讨论,
+     * 自己造的子任务工具(council 的 lens/arbiter、discuss 的成员/synthesizer):那些子任务只该读仓库/讨论,
      * 拿全量可写手是 [3208] 病灶里最意外的一支(零工具人格照拿 Bash)。取用一律走 {@link pickHandsRunner},
      * 不在场景体内手挑 —— 判别位是唯一开关。
      */
@@ -64,7 +65,7 @@ export interface ScenarioDeps {
     /**
      * When true, the `default` scenario carries the Sema product identity (see {@link semaIdentityProvider}).
      * Set by the local/TOC deployment (CONFIG_PROVIDER=local / run-local) so the local engine answers "who
-     * are you" as Sema instead of the model's hallucinated identity. Business scenarios (oa/team/code-review)
+     * are you" as Sema instead of the model's hallucinated identity. Business scenarios (discuss/code-review)
      * keep their own prompts; cloud (CONFIG_PROVIDER≠local) leaves the default scenario neutral unless turned
      * on, so integrators that inject their own persona are unaffected.
      */
@@ -170,7 +171,7 @@ export interface ScenarioDetail {
     /** 机读原因键;仅 `available:false` 时在场(缺席=没有理由)。消费方按键分支,禁匹配英文文案。 */
     unavailableReason?: ScenarioUnavailableReason;
 }
-/** 内建五场景详情。default/code/team 工厂对良性请求无副作用可真调(拿真实工具名单);code-review/scan 是
+/** 内建五场景详情。default/code/discuss 工厂对良性请求无副作用可真调(拿真实工具名单);code-review/scan 是
  *  fail-loud 语义(缺 GIT_API 配置/principal 即 throw)→ 探针失败落静态表兜底(表↔工厂一致性由测试锁:
  *  测试喂 fake deps 真调工厂对账工具名)。enabled 对内建恒 true(约定②)。 */
 export declare function builtinScenarioDetails(scenarios: Record<string, Scenario>, deps: Pick<ScenarioDeps, "brandIdentity" | "repoClient">): Record<string, ScenarioDetail>;
@@ -201,7 +202,7 @@ export type ScenarioAvailability = {
  *
  * 判据键 = **toolset**:内建详情与 center 条目都带这个字段,故两条产线天然共用同一份判据。
  * `requiresRepo` 的 toolset 需要部署配好 git 后端(`GIT_API_BASEURL` ⇒ `deps.repoClient`)。
- * 词表外的 toolset(内建的 `full-body`/`team`)不依赖后端 ⇒ 恒可用。
+ * 词表外的 toolset(内建的 `full-body`/`discuss`)不依赖后端 ⇒ 恒可用。
  */
 export declare function scenarioAvailability(deps: Pick<ScenarioDeps, "repoClient">, toolset: string): ScenarioAvailability;
 /** 拒绝文案的唯一属主:闭集穷举 switch(新增原因词不在这里表态即编译红)。 */
@@ -241,5 +242,5 @@ export interface ScenarioRuling {
  *     到现状,与 workflows 面的 fail-closed 是刻意的 posture 差异,见 runtime-caps-resolver)。
  *   - body.scenario 未给:ruling 胜者 ⇒ 指派为默认;无胜者 ⇒ defaultScenario 现状链。
  */
-export declare function gateScenarioRequest(ruling: ScenarioRuling | undefined, bodyScenario: unknown, defaultScenario: string, known: readonly string[]): string;
+export declare function gateScenarioRequest(ruling: ScenarioRuling | undefined, bodyScenario: unknown, defaultScenario: string, known: readonly string[], logger?: Logger): string;
 //# sourceMappingURL=scenarios.d.ts.map

package/dist/capabilities/scenarios.js

@@ -4,10 +4,14 @@ import { nowTool } from "./builtin-tools.js";
 import { parseRepo, repoToolsFor } from "./repo-tools.js";
 import { createCouncilTool, clampRounds } from "./code-review-council.js";
 import { stablePrompt } from "./prompt.js";
-import { createTeamTool, teamCoordinatorPrompt, getTeam, teamNames } from "./team.js";
+import { createDiscussionTools, discussionCoordinatorPrompt, getTeam, teamNames } from "./team.js";
 import { createWebSearchBackend, webSearchConfigFromSettings } from "../plugins/web-search.js";
 import { skillsForScenario } from "./skills.js";
 import { pickHandsRunner } from "./hands-lane.js";
+import { SCENARIO_ALIASES, canonicalScenarioName } from "./scenario-alias.js";
+// #273 / C-R14:alias 表与两只归一口的**属主**是 `scenario-alias.ts`(零依赖模块,避免
+// scenarios ↔ skills/skills-mcp/center-prompts 的循环 import)。此处再导出一次,保持既有 import 面。
+export { SCENARIO_ALIASES, canonicalScenarioName, scenarioConfigKeys } from "./scenario-alias.js";
 /**
  * Sema product identity, prepended to the core default base for the `default` scenario when
  * {@link ScenarioDeps.brandIdentity} is on. Honest about the substrate (the engine runs whichever model
@@ -216,42 +220,49 @@ export function buildScenarios(deps) {
                 skills: skillsForScenario(deps.skills, "scan"),
             };
         },
-        // Multi-agent team: pick a template, the consumer (OA) injects business context, we run it.
-        // Templates resolve from the live registry (`getTeam`) = BUILTIN_TEAMS overridden/extended by the
-        // sema registry at runtime (applyEffective → registerTeams), so a team is config-driven; built-ins
-        // are the fallback when the center supplies none.
-        team: (req) => {
+        // Multi-agent DISCUSSION (#273 / C-R14 改名,旧名 `team` = 入口 alias 一版,见 {@link SCENARIO_ALIASES}):
+        // pick a template, the consumer (OA) injects business context, we run it. Templates resolve from the
+        // live registry (`getTeam`) = BUILTIN_TEAMS overridden/extended by the sema registry at runtime
+        // (applyEffective → registerTeams), so the roster is config-driven; built-ins are the fallback when
+        // the center supplies none. ⚠️ 模板注册面(`req.team` / center `teams` 键 / registry TEAMS.md)刻意
+        // **不**改名:那是 registry-core 的配置词汇(跨仓契约),改它要另立件+center 侧同款 alias;C-R14 的
+        // server 射程 = 场景名/工具名/模型可见文案三件([4127] 认领形)。
+        discuss: (req) => {
             const name = typeof req.team === "string" ? req.team : "default";
             const template = getTeam(name); // built-ins, overridden/extended by the sema registry at runtime
             if (!template) {
-                throw new HttpError(404, `unknown team "${name}" (available: ${teamNames().join(", ")})`);
+                throw new HttpError(404, `unknown discussion roster "${name}" (available: ${teamNames().join(", ")})`);
             }
             const objective = typeof req.objective === "string" ? req.objective : "Discuss the task.";
             const businessContext = typeof req.businessContext === "string" ? req.businessContext : undefined;
             // #196:成员/synthesizer 是纯讨论人格(模板声明零工具),跑在无手 subRunner 上。
             const hands = "none";
             return {
-                tools: [createTeamTool(subRunnerFor(deps, hands), template, { objective, businessContext })],
+                tools: createDiscussionTools(subRunnerFor(deps, hands), template, { objective, businessContext, ...(deps.logger ? { logger: deps.logger } : {}) }),
                 hands,
-                skills: skillsForScenario(deps.skills, "team"),
-                promptProvider: teamCoordinatorPrompt,
+                skills: skillsForScenario(deps.skills, "discuss"),
+                promptProvider: discussionCoordinatorPrompt,
             };
         },
     };
 }
 /** Resolve the scenario for a request (falls back to `default`). */
 export function selectScenario(scenarios, name) {
+    // #273 alias:两条产线(HTTP resolve-spec / run-local)在算 `scenarioName` 时已经归一过,所以这里
+    // 对它们是**幂等**的;真正需要这一手的是**库面**调用方(index.ts 导出 selectScenario,嵌入式装配
+    // 自己传名字)—— 不归一的话旧名会静默落 `default`,那是比「名字过时」更坏的结果(整套工具面换人)。
+    const resolved = name === undefined ? undefined : canonicalScenarioName(name, Object.keys(scenarios));
     // #193 P2-13:own-property 守卫——`Record` 字面量的裸索引对原型链键("constructor" 形状)会把
     // Object.prototype 上的函数当 Scenario 返回。上游 resolve-spec 按 Object.keys 校验 ⇒ 当前不可利用,
     // 本守卫是纵深防御(本函数是导出面,不得依赖单一调用方的入口校验)。
-    return (name && Object.hasOwn(scenarios, name) && scenarios[name]) || scenarios.default;
+    return (resolved && Object.hasOwn(scenarios, resolved) && scenarios[resolved]) || scenarios.default;
 }
 /** 把属主的判别式摊平成 wire 上的两个键(可用臂整键省略原因,契约=「缺席即没有理由」)。 */
 function availabilityFields(deps, toolset) {
     const verdict = scenarioAvailability(deps, toolset);
     return verdict.available ? { available: true } : { available: false, unavailableReason: verdict.reason };
 }
-/** 内建五场景详情。default/code/team 工厂对良性请求无副作用可真调(拿真实工具名单);code-review/scan 是
+/** 内建五场景详情。default/code/discuss 工厂对良性请求无副作用可真调(拿真实工具名单);code-review/scan 是
  *  fail-loud 语义(缺 GIT_API 配置/principal 即 throw)→ 探针失败落静态表兜底(表↔工厂一致性由测试锁:
  *  测试喂 fake deps 真调工厂对账工具名)。enabled 对内建恒 true(约定②)。 */
 export function builtinScenarioDetails(scenarios, deps) {
@@ -277,7 +288,9 @@ export function builtinScenarioDetails(scenarios, deps) {
         default: mk("default", "通用/助理场景(域中性 persona,CC agent loop 全量工具面;[891] 起非出厂缺省,显式可选)", "full-body", probe("default", {}, undefined, ["Now"]), deps.brandIdentity ? "Sema 产品身份 + core 默认宪法(结构层由引擎合成)" : "core 默认宪法(中性,无场景附加 persona)"),
         "code-review": mk("code-review", "代码评审(clone-free 只读仓库工具;council=true 升多镜头评审团)", "repo-readonly", probe("code-review", { repo: "probe/probe" }, undefined, REPO_TOOLS), "评审员/评审团协调提示词(镜头分工+产出契约)"),
         scan: mk("scan", "中性只读仓库扫描(输出契约由 objective+skills 决定)", "repo-readonly", probe("scan", { repo: "probe/probe" }, undefined, REPO_TOOLS), "无场景附加提示词(objective+center skills 拥有输出契约)"),
-        team: mk("team", "多智能体团队圆桌(模板成员+synthesizer,模板可由 registry 配置)", "team", probe("team", {}, undefined, ["run_team"]), "团队协调者提示词(圆桌纪律+合成流程)"),
+        // #273 / C-R14:旧名 `team` 不再是一条**被声明**的场景(它只是 SCENARIO_ALIASES 里的入口别名)——
+        // 列举面只列现役主名,免得消费方把别名当成第二条能力画上去。
+        discuss: mk("discuss", "多智能体讨论圆桌(模板成员+synthesizer,模板可由 registry 配置)", "discuss", probe("discuss", {}, undefined, ["run_discussion", "run_team"]), "讨论协调者提示词(圆桌纪律+合成流程)"),
     };
 }
 /** center 条目详情(有效性判定与 centerScenarios 完全同款:无效条目既不进 overlay 也不进详情——
@@ -289,6 +302,8 @@ export function centerScenarioDetails(specs, builtinNames, deps) {
             continue;
         if (typeof spec.name !== "string" || !SCENARIO_NAME_RE.test(spec.name))
             continue;
+        if (Object.hasOwn(SCENARIO_ALIASES, spec.name))
+            continue; // #273:保留名与 centerScenarios 同判(约定①)
         if (!Object.hasOwn(TOOLSETS, spec.toolset) || !TOOLSETS[spec.toolset])
             continue; // P2-13 同族守卫
         out[spec.name] = {
@@ -332,7 +347,7 @@ const SCENARIO_AVAILABLE = { available: true };
  *
  * 判据键 = **toolset**:内建详情与 center 条目都带这个字段,故两条产线天然共用同一份判据。
  * `requiresRepo` 的 toolset 需要部署配好 git 后端(`GIT_API_BASEURL` ⇒ `deps.repoClient`)。
- * 词表外的 toolset(内建的 `full-body`/`team`)不依赖后端 ⇒ 恒可用。
+ * 词表外的 toolset(内建的 `full-body`/`discuss`)不依赖后端 ⇒ 恒可用。
  */
 export function scenarioAvailability(deps, toolset) {
     if (Object.hasOwn(TOOLSETS, toolset) && TOOLSETS[toolset]?.requiresRepo === true && deps.repoClient === undefined) { // P2-13 同族守卫
@@ -375,6 +390,18 @@ export function centerScenarios(deps, specs, builtinNames, logger) {
             logger?.warn("sema_registry_scenario_invalid", { name: String(spec?.name), reason: "name must match " + String(SCENARIO_NAME_RE) });
             continue;
         }
+        // #273 alias 窗:**旧名是保留名**。窗内 `team` 只能是 `discuss` 的入口别名 —— 让 center 用它另立
+        // 一条场景会立刻造出两个属主:请求面归它、而按场景键的运维配置(skills/mcp/a2a/prompts 的旧名
+        // 标签)在 alias 窗里同时也算 `discuss` 的,于是那条影子场景的 MCP/A2A(工具面+egress 面)会静默
+        // 漏进 discuss 的 roster(codex 对抗复审 [high],验真后采纳)。二义在源头掐掉,并且**响亮**跳过
+        // ——静默跳过等于让运维以为声明生效了。窗撤销时随 SCENARIO_ALIASES 一起消失。
+        if (Object.hasOwn(SCENARIO_ALIASES, spec.name)) {
+            logger?.warn("sema_registry_scenario_invalid", {
+                name: spec.name,
+                reason: `"${spec.name}" is a RESERVED deprecated scenario alias during the rename window — it resolves to "${SCENARIO_ALIASES[spec.name]}". Declare this scenario under a different name.`,
+            });
+            continue;
+        }
         const toolset = Object.hasOwn(TOOLSETS, spec.toolset) ? TOOLSETS[spec.toolset] : undefined; // P2-13 同族守卫
         if (!toolset) {
             logger?.warn("sema_registry_scenario_invalid", { name: spec.name, reason: `unknown toolset "${String(spec.toolset)}" (have: ${Object.keys(TOOLSETS).join(", ")})` });
@@ -493,27 +520,34 @@ export function mergeUserSkills(scenarioSkills, userSkills, logger) {
  *     到现状,与 workflows 面的 fail-closed 是刻意的 posture 差异,见 runtime-caps-resolver)。
  *   - body.scenario 未给:ruling 胜者 ⇒ 指派为默认;无胜者 ⇒ defaultScenario 现状链。
  */
-export function gateScenarioRequest(ruling, bodyScenario, defaultScenario, known) {
+export function gateScenarioRequest(ruling, bodyScenario, defaultScenario, known, logger) {
     if (typeof bodyScenario === "string") {
+        // #273 alias(HTTP lane 的**唯一**归一点,见 SCENARIO_ALIASES 头注):旧名在这里变主名,词表门/
+        // allowlist 门/返回值三者此后只谈主名。allowlist 一并归一——运维写的是旧名、调用方用新名(或反过来)
+        // 说的是**同一个能力**,窗内不许因为改名把人挡在门外。
+        const requested = canonicalScenarioName(bodyScenario, known, logger);
         // [2395]D③(5.1.0):body 显式给出的**未知名**响亮 400——此前静默折 default(oa 退役后老调用方
         // 无声换了场景=更宽工具面,与零兼容纲领相反)。词表面先于治理面:名字都不存在时谈不上 allowlist。
         // 指派链(ruling/default)不在此验——悬空指派名仍走 resolveSpec 既有 unknown→default(runtime-caps
         // 面的误配另案,不该让一次中心误配把每个请求 400 死)。
-        if (!known.includes(bodyScenario)) {
+        if (!known.includes(requested)) {
+            // 文案点名调用方**发的**那个名字(归一后的名字对他没有意义:他没发过它)。
             throw new HttpError(400, `unknown scenario "${bodyScenario}" — this deployment's scenarios are: ${known.join(", ")}`, {
                 code: "scenario_unknown",
                 extra: { known: [...known] },
             });
         }
         const allowed = ruling?.allowlist ?? [];
-        if (allowed.length > 0 && !allowed.includes(bodyScenario)) {
+        if (allowed.length > 0 && !allowed.map((n) => canonicalScenarioName(n, known)).includes(requested)) {
             throw new HttpError(400, `scenario "${bodyScenario}" is not in this principal's assigned allowlist`, {
                 code: "scenario_not_allowed",
-                extra: { allowlist: allowed },
+                extra: { allowlist: allowed }, // 运维自己的字面(不替他改写配置),判定用的是归一后的集合
             });
         }
-        return bodyScenario;
+        return requested;
     }
-    return ruling?.scenario ?? defaultScenario;
+    // 指派面(ruling.scenario)/部署面(DEFAULT_SCENARIO)同样过归一:两者都是**配置里写的名字**,
+    // 旧名不归一就会落到 resolveSpec 的 unknown→default 回退上——静默换场景,正是本窗要避免的。
+    return canonicalScenarioName(ruling?.scenario ?? defaultScenario, known, logger);
 }
 //# sourceMappingURL=scenarios.js.map

package/dist/capabilities/skills.d.ts

@@ -47,7 +47,9 @@ export interface LoadSkillsOptions {
  *  `label` = 错误文本里的对象名(center-plugins 用它约束 manifest 本体,报错不该指成 skill entry)。 */
 export declare function assertConfined(p: string, rootReal: string, label?: string): void;
 export declare function loadSkills(dir: string, opts?: LoadSkillsOptions): LoadedSkill[];
-/** Skills applicable to a scenario: those tagged with it, plus untagged (global) ones. */
+/** Skills applicable to a scenario: those tagged with it, plus untagged (global) ones.
+ *  #273 alias 窗:标签写**旧场景名**的技能同样命中(`scenarioConfigKeys`)—— 请求面归一之后,运维已经
+ *  写好的 `scenarios: team` 若不再被命中,就是改名当版静默摘掉他的配置。 */
 export declare function skillsForScenario(loaded: LoadedSkill[], scenario: string): SkillSpec[];
 export declare function parseFrontmatter(raw: string): {
     meta: Record<string, string>;

package/dist/capabilities/skills.js

@@ -1,5 +1,6 @@
 import { readdirSync, readFileSync, realpathSync, statSync } from "node:fs";
 import { join, sep } from "node:path";
+import { scenarioConfigKeys } from "./scenario-alias.js";
 /** `p` 的 realpath 必须落在 `rootReal` 之内(含自身),否则抛。`sep` 边界判定防 `/a/root-evil` 撞
  *  `/a/root` 前缀。目标不存在 ⇒ realpath 抛 ENOENT,同样是拒绝(悬空链接不该被读)。
  *  `label` = 错误文本里的对象名(center-plugins 用它约束 manifest 本体,报错不该指成 skill entry)。 */
@@ -108,9 +109,12 @@ function parseSkill(raw, fallbackName) {
         .filter(Boolean);
     return { spec: { name, description, content: body.trim() }, scenarios };
 }
-/** Skills applicable to a scenario: those tagged with it, plus untagged (global) ones. */
+/** Skills applicable to a scenario: those tagged with it, plus untagged (global) ones.
+ *  #273 alias 窗:标签写**旧场景名**的技能同样命中(`scenarioConfigKeys`)—— 请求面归一之后,运维已经
+ *  写好的 `scenarios: team` 若不再被命中,就是改名当版静默摘掉他的配置。 */
 export function skillsForScenario(loaded, scenario) {
-    return loaded.filter((k) => k.scenarios.length === 0 || k.scenarios.includes(scenario)).map((k) => k.spec);
+    const keys = scenarioConfigKeys(scenario);
+    return loaded.filter((k) => k.scenarios.length === 0 || keys.some((n) => k.scenarios.includes(n))).map((k) => k.spec);
 }
 export function parseFrontmatter(raw) {
     // Tolerate CRLF (`\r?\n`): a skill .md saved on Windows / via some editors would otherwise miss the regex and

package/dist/capabilities/team.d.ts

@@ -1,7 +1,16 @@
 import { runTeamDiscussion, type ModelRef, type ModelRole, type Runner, type ToolSpec } from "@sema-agent/core";
+import type { Logger } from "../observability/logger.js";
 /**
- * `team` scenario — run a configured multi-agent team (core `runTeamDiscussion`) on a task. Packaged
- * as ONE tool the lead calls once (same shape as the code-review council), so the run model is unchanged.
+ * `discuss` scenario — run a configured multi-agent DISCUSSION (core `runTeamDiscussion`) on a task.
+ * Packaged as ONE tool the lead calls once (same shape as the code-review council), so the run model is
+ * unchanged.
+ *
+ * ── 词汇(#273 / C-R14,clay 直裁 [4123])──────────────────────────────────────────────────────
+ * 「team」= agent-teams(持久具名团队)专用词;一次性多 agent 讨论叫「discuss」。所以**面向调用方/
+ * 模型的名字**全部是 discussion:场景 `discuss`、工具 `run_discussion`、协调者提示词。
+ * 而**模板注册面**(`BUILTIN_TEAMS` / `registerTeams` / `getTeam` / center 的 `teams` 键)保留 team
+ * 词汇 —— 它是 registry-core 的配置契约(docs/TEAMS.md、`GET /api/config/effective → teams`),跨仓
+ * 同改要另立件+center 侧同款 alias;本批刻意不单方面改一半(半改的配置键比不改更坏)。
  *
  * HYBRID layering (mirrors sema-registry docs/TEAMS.md): the TEMPLATE here carries only the
  * GENERIC orchestration skeleton (member roles + generic personas, rounds, synthesizer); the CONSUMER
@@ -9,7 +18,7 @@ import { runTeamDiscussion, type ModelRef, type ModelRole, type Runner, type Too
  *
  * Templates: BUILTIN_TEAMS are the defaults; the sema registry pushes more at runtime via
  * `applyEffective → registerTeams` (GET /api/config/effective → `teams`), and `getTeam` resolves from
- * that merged registry. So teams are config-driven; the built-ins are the fallback.
+ * that merged registry. So rosters are config-driven; the built-ins are the fallback.
  */
 type TeamFn = typeof runTeamDiscussion;
 export interface TeamMemberTemplate {
@@ -41,13 +50,34 @@ export declare const BUILTIN_TEAMS: Record<string, TeamTemplate>;
 export declare function registerTeams(extra: Record<string, TeamTemplate>): void;
 export declare function getTeam(name: string): TeamTemplate | undefined;
 export declare function teamNames(): string[];
-/** Build the `run_team` tool bound to a template + the consumer's per-call business injection. */
-export declare function createTeamTool(subRunner: Runner, template: TeamTemplate, opts: {
+/** 现役工具名(模型可见 = 行为面)。 */
+export declare const DISCUSSION_TOOL_NAME = "run_discussion";
+/** #273 / C-R14 过渡窗的旧工具名。**下一 minor 与 `SCENARIO_ALIASES` 同批删**。 */
+export declare const DEPRECATED_DISCUSSION_TOOL_ALIAS = "run_team";
+/**
+ * Build the discussion tool(s) bound to a template + the consumer's per-call business injection:
+ * `[run_discussion, run_team]` —— 主名 + **同款可执行**的旧名别名(窗一版)。
+ *
+ * 为什么别名要真能跑(而不是只保留名字或直接删):这只工具的调用方是**模型**,而模型读的提示词
+ * 不一定是我们写的 —— center prompts(`scenarioOverrides`)与运维技能里完全可以写死 `run_team`。
+ * 名字直接消失 ⇒ 那些部署当场进「工具不存在」的空转循环;留个空壳 ⇒ 同样跑不出结论。
+ * 代价(诚实记账):模型有可能两只都调 = 两轮完整讨论。压住这条的是**提示词只教主名** + 别名
+ * description 第一句就说 deprecated/别调;命中即 warn(`discussion_tool_alias_deprecated`)——窗撤销
+ * 与否有真读数,不靠猜。
+ */
+export declare function createDiscussionTools(subRunner: Runner, template: TeamTemplate, opts: {
+    objective: string;
+    businessContext?: string;
+    teamFn?: TeamFn;
+    logger?: Logger;
+}): ToolSpec[];
+/** Build the `run_discussion` tool bound to a template + the consumer's per-call business injection. */
+export declare function createDiscussionTool(subRunner: Runner, template: TeamTemplate, opts: {
     objective: string;
     businessContext?: string;
     teamFn?: TeamFn;
 }): ToolSpec;
-/** The lead just runs the team tool once and returns its conclusion verbatim. */
-export declare const teamCoordinatorPrompt: import("@sema-agent/core").PromptProvider;
+/** The lead just runs the discussion tool once and returns its conclusion verbatim. */
+export declare const discussionCoordinatorPrompt: import("@sema-agent/core").PromptProvider;
 export {};
 //# sourceMappingURL=team.d.ts.map

package/dist/capabilities/team.js

@@ -37,11 +37,43 @@ export function getTeam(name) {
 export function teamNames() {
     return Object.keys(TEAMS);
 }
-/** Build the `run_team` tool bound to a template + the consumer's per-call business injection. */
-export function createTeamTool(subRunner, template, opts) {
+/** 现役工具名(模型可见 = 行为面)。 */
+export const DISCUSSION_TOOL_NAME = "run_discussion";
+/** #273 / C-R14 过渡窗的旧工具名。**下一 minor 与 `SCENARIO_ALIASES` 同批删**。 */
+export const DEPRECATED_DISCUSSION_TOOL_ALIAS = "run_team";
+/**
+ * Build the discussion tool(s) bound to a template + the consumer's per-call business injection:
+ * `[run_discussion, run_team]` —— 主名 + **同款可执行**的旧名别名(窗一版)。
+ *
+ * 为什么别名要真能跑(而不是只保留名字或直接删):这只工具的调用方是**模型**,而模型读的提示词
+ * 不一定是我们写的 —— center prompts(`scenarioOverrides`)与运维技能里完全可以写死 `run_team`。
+ * 名字直接消失 ⇒ 那些部署当场进「工具不存在」的空转循环;留个空壳 ⇒ 同样跑不出结论。
+ * 代价(诚实记账):模型有可能两只都调 = 两轮完整讨论。压住这条的是**提示词只教主名** + 别名
+ * description 第一句就说 deprecated/别调;命中即 warn(`discussion_tool_alias_deprecated`)——窗撤销
+ * 与否有真读数,不靠猜。
+ */
+export function createDiscussionTools(subRunner, template, opts) {
+    const primary = createDiscussionTool(subRunner, template, opts);
+    return [
+        primary,
+        {
+            ...primary,
+            name: DEPRECATED_DISCUSSION_TOOL_ALIAS,
+            description: `DEPRECATED alias of \`${DISCUSSION_TOOL_NAME}\` — do not call it; call \`${DISCUSSION_TOOL_NAME}\` instead. ` +
+                "Kept for one release so a deployment whose prompts still name the old tool keeps working. " +
+                primary.description,
+            execute: async (args, ctx) => {
+                opts.logger?.warn("discussion_tool_alias_deprecated", { requested: DEPRECATED_DISCUSSION_TOOL_ALIAS, resolved: DISCUSSION_TOOL_NAME });
+                return primary.execute(args, ctx);
+            },
+        },
+    ];
+}
+/** Build the `run_discussion` tool bound to a template + the consumer's per-call business injection. */
+export function createDiscussionTool(subRunner, template, opts) {
     return {
-        name: "run_team",
-        description: "Run the configured multi-agent team discussion on the task and return the synthesized " +
+        name: DISCUSSION_TOOL_NAME,
+        description: "Run the configured multi-agent discussion on the task and return the synthesized " +
             "conclusion. Call exactly once, with no arguments.",
         effect: "read",
         parameters: Type.Object({}),
@@ -75,12 +107,12 @@ export function createTeamTool(subRunner, template, opts) {
             // 1.32: synthesizer 失败时 `conclusion` 是 `[unavailable…]` 垃圾串。标注失败，别把垃圾当综合结论返回。
             const content = team.conclusionValid
                 ? team.conclusion
-                : "[团队综合失败：synthesizer 重试后仍未产出可靠结论，可重试或检查模型/配置]";
+                : "[讨论综合失败：synthesizer 重试后仍未产出可靠结论，可重试或检查模型/配置]";
             return { content, details: { team: template.name, members: template.members.length, rounds: template.rounds, conclusionValid: team.conclusionValid } };
         },
     };
 }
-/** The lead just runs the team tool once and returns its conclusion verbatim. */
-export const teamCoordinatorPrompt = stablePrompt("You run a multi-agent team. Call `run_team` exactly once (no arguments). When it returns the team's " +
-    "synthesized conclusion, output it VERBATIM as your final answer — do not summarize or rewrite it.");
+/** The lead just runs the discussion tool once and returns its conclusion verbatim. */
+export const discussionCoordinatorPrompt = stablePrompt(`You run a multi-agent discussion. Call \`${DISCUSSION_TOOL_NAME}\` exactly once (no arguments). When it ` +
+    "returns the synthesized conclusion, output it VERBATIM as your final answer — do not summarize or rewrite it.");
 //# sourceMappingURL=team.js.map

package/dist/config-center/skills-mcp.d.ts

@@ -27,7 +27,8 @@ diskCacheDir?: string): Promise<LoadedSkill[]>;
 export declare function resolveMcpServers(mcp: {
     servers: CenterMcpServer[];
 }, logger?: Logger): ScopedMcpServer[];
-/** The MCP servers applicable to a scenario: tagged with it, or untagged (global). undefined when none. */
+/** The MCP servers applicable to a scenario: tagged with it, or untagged (global). undefined when none.
+ *  #273 alias 窗:标签写**旧场景名**的条目同样命中(`scenarioConfigKeys`,同 `skillsForScenario`)。 */
 export declare function mcpForScenario(servers: ScopedMcpServer[] | undefined, scenario: string): McpServerSpec[] | undefined;
 /**
  * DESIGN-269 §2.1 —— resolve center A2A peers (`/effective.a2a`) into core `A2aServerSpec`s + the scenarios

package/dist/config-center/skills-mcp.js

@@ -9,6 +9,7 @@
  * the facade re-exports every symbol below unchanged).
  */
 import { skillContentHash } from "@sema-agent/registry-core";
+import { scenarioConfigKeys } from "../capabilities/scenario-alias.js";
 import { fetchSkillContent } from "./http-client.js";
 import { SHA256_HEX_RE } from "../digest-form.js";
 /**
@@ -146,11 +147,13 @@ export function resolveMcpServers(mcp, logger) {
         logger?.info("sema_registry_mcp", { servers: out.map((s) => s.spec.name) });
     return out;
 }
-/** The MCP servers applicable to a scenario: tagged with it, or untagged (global). undefined when none. */
+/** The MCP servers applicable to a scenario: tagged with it, or untagged (global). undefined when none.
+ *  #273 alias 窗:标签写**旧场景名**的条目同样命中(`scenarioConfigKeys`,同 `skillsForScenario`)。 */
 export function mcpForScenario(servers, scenario) {
     if (!servers || servers.length === 0)
         return undefined;
-    const hit = servers.filter((s) => s.scenarios.length === 0 || s.scenarios.includes(scenario)).map((s) => s.spec);
+    const keys = scenarioConfigKeys(scenario);
+    const hit = servers.filter((s) => s.scenarios.length === 0 || keys.some((n) => s.scenarios.includes(n))).map((s) => s.spec);
     return hit.length > 0 ? hit : undefined;
 }
 /**
@@ -201,7 +204,8 @@ export function resolveA2aPeers(a2a, logger) {
 export function a2aForScenario(peers, scenario) {
     if (!peers || peers.length === 0)
         return undefined;
-    const hit = peers.filter((p) => p.scenarios.length === 0 || p.scenarios.includes(scenario)).map((p) => p.spec);
+    const keys = scenarioConfigKeys(scenario); // #273 alias 窗:旧场景名标签同样命中(同 mcpForScenario)
+    const hit = peers.filter((p) => p.scenarios.length === 0 || keys.some((n) => p.scenarios.includes(n))).map((p) => p.spec);
     return hit.length > 0 ? hit : undefined;
 }
 //# sourceMappingURL=skills-mcp.js.map

package/dist/http/wire-types.d.ts

@@ -11,7 +11,7 @@ export interface TaskRequestBody {
     objective: string;
     sessionId?: string;
     /** Which deployment SCENARIO assembles this task's tools/prompt/skills (the keys of the worker's scenario
-     *  table — e.g. "default"/"code-review"/"scan"/"team"). An INTENT bounded by the deployment's own table AND,
+     *  table — e.g. "default"/"code-review"/"scan"/"discuss"). An INTENT bounded by the deployment's own table AND,
      *  on a governed worker, by the principal's center-resolved allowlist: an unknown name is a typed 400
      *  `scenario_unknown`, a known-but-not-allowed one a typed 400 `scenario_not_allowed`; absent ⇒ the ruling's
      *  assigned scenario, else `DEFAULT_SCENARIO` (consumed at `boot/resolve-spec.ts` via `gateScenarioRequest`).

package/dist/main.js

@@ -311,7 +311,7 @@ async function main() {
     // `Runner.sessions` 就是传进去的那只 store,两只 Runner 不会各持一份会话缓存),唯独不挂
     // `executionEnvFactory`。core 的 `handsEnabled = ownedEnv || deps.executionEnv` 是 **per-Runner** 合同,
     // 单 runner 服务全场景时结构上无法逐场景兑现 —— 这只孪生就是兑现它的那一半(设计小票 §2a)。
-    // 声明 hands:"none" 的场景(scan / code-review 两腿 / team / center overlay)在 HTTP 执行点被路由到这里。
+    // 声明 hands:"none" 的场景(scan / code-review 两腿 / discuss / center overlay)在 HTTP 执行点被路由到这里。
     //
     // 🔴 两条**已知边界**(codex 复审 2026-08-09 两轮提出,逐条亲验 core dist 后如实记账;两条的部署条件
     //     互不相同 —— 不要把它们并成一句)。
@@ -428,7 +428,7 @@ async function main() {
     // "memory backend diverges" premise was wrong; double-review caught it — see the cap site in http/server.ts).
     // Static per deployment (deps are boot-fixed).
     const workflowsCapable = workflowsCapability(runnerDeps);
-    // Sub-task runner (code-review council lenses/arbiter, subagent/team children). [1364]①/[1367]①(core
+    // Sub-task runner (code-review council lenses/arbiter, subagent/discussion children). [1364]①/[1367]①(core
     // 1.350 fork 终修的部署要求):fork 子任务带 `requireExistingSession:true` 在这里执行而源会话在 HOST 店
     // ——拆店=响亮 `resume.session_not_found`(cli fork 案的 server 半场)。但整店共享被 codex 判两 high
     // (普通子任务铸 committed durable 会话:无 reaper 覆盖=无界增长+污染 /v1/sessions 枚举),故走
@@ -509,7 +509,7 @@ async function main() {
     };
     const subRunner = new Runner(subRunnerDeps);
     // #196:`subRunner` 的无手孪生(同一份 deps 字面量摘掉 executionEnvFactory —— 差异面只有这一处,
-    // 结构上不可能漂移)。council 的 lens/arbiter、team 的成员/synthesizer 走它:那些子任务的人格声明
+    // 结构上不可能漂移)。council 的 lens/arbiter、discuss 的成员/synthesizer 走它:那些子任务的人格声明
     // 里一件工具都没有,却在修前照拿全量可写手(设计小票 §1 里最意外的一支)。
     // ⚠️ 与主 subRunner 共享 `subRunnerSessions` 与 `checkpointStore` 同实例 —— park/fork 的行是同一批。
     const handslessSubRunner = new Runner(withoutExecutionEnv(subRunnerDeps));
@@ -525,7 +525,8 @@ async function main() {
     // map; undefined only on the env-only/no-backend deploy (which has no durable approvals either — consistent).
     const approvalExemptionStore = backend ? backend.approvalExemption() : undefined;
     const instanceId = uuidv7();
-    // Per-task wall-clock override (seconds). 0/absent = keep the built-in 600 (1500 council/debate/team) —
+    // Per-task wall-clock override (seconds). 0/absent = keep the tenancy default (see taskWallClockSec:
+    // 2400s, 3600s for the big lane = council/debate/discuss) —
     // the override only ever RAISES (Math.max at the use site), so a misconfigured low value cannot shrink
     // the council budget.
     // 🔴 2026-08-01 env fail-loud 族:原为 `Math.max(0, Math.floor(Number(env ?? "0")) || 0)` ——

package/dist/run-local.js

@@ -65,7 +65,7 @@ import { makeLoadProjectMemory, makeProbeInstructionSources } from "./project-me
 import { loadSkills } from "./capabilities/skills.js";
 import { createRepoClient } from "./capabilities/repo-tools.js";
 import { webSearchConfigFromEnv, createWebSearchBackend } from "./plugins/web-search.js";
-import { buildScenarios, selectScenario, centerScenarios } from "./capabilities/scenarios.js";
+import { buildScenarios, selectScenario, centerScenarios, canonicalScenarioName } from "./capabilities/scenarios.js";
 import { pickHandsRunner, withoutExecutionEnv } from "./capabilities/hands-lane.js";
 import { HttpError } from "./security.js";
 import { memoryEngineBackendFor, memorySpecForRequest } from "./memory-scope.js";
@@ -653,7 +653,7 @@ export async function runLocal(argv, deps = {}) {
             : {}),
     };
     const runner = new Runner(runnerDeps);
-    // Sub-task runner (council lenses/team) — mirrors main.ts's subRunner, INCLUDING executionEnvFactory so a delegated
+    // Sub-task runner (council lenses/discussion members) — mirrors main.ts's subRunner, INCLUDING executionEnvFactory so a delegated
     // child gets hands (Bash/Read/Edit) on the host lane. Without it the child's handsEnabled is false — the exact
     // "subagent couldn't run pwd" defect fixed at main.ts:799; this is its run-local twin, caught by the systematic audit.
     // [1367]① fork server half(main.ts subRunner 同款):ForkRoutingSessionStore——fork/resume 形
@@ -667,7 +667,7 @@ export async function runLocal(argv, deps = {}) {
     const subRunnerDeps = { ...sharedRunnerDeps, sessionStore: new ForkRoutingSessionStore(sessionStore, new TtlSessionStore({ defaultTtlDays: 1 / 24 })), onError: engineOnError, onAsk };
     const subRunner = new Runner(subRunnerDeps);
     // #196:无手孪生一对 —— **mirrors main.ts**(那边是 `handslessRunner` / `handslessSubRunner` 两只,同 deps
-    // 摘掉 executionEnvFactory)。run-local 是同形装配点,漏这一对 = 本地 lane 上 scan/council/team 的最终
+    // 摘掉 executionEnvFactory)。run-local 是同形装配点,漏这一对 = 本地 lane 上 scan/council/discuss 的最终
     // roster 仍被并集进全量可写手(server 修了、CLI 静默留病 —— 这条腿的 subRunner 当年就是这么漏配的)。
     const handslessRunner = new Runner(withoutExecutionEnv(runnerDeps));
     const handslessSubRunner = new Runner(withoutExecutionEnv(subRunnerDeps));
@@ -692,7 +692,10 @@ export async function runLocal(argv, deps = {}) {
     }
     // ── Build the TaskSpec the way the /v1/tasks sync handler's resolveSpec does (minus server-only fields:
     //    no auth/principal/durable/approval/budget-cap-from-body). Fresh sessionId; @-model mention honored. ──
-    const requested = args.scenario ?? config.defaultScenario;
+    // #273 alias:run-local lane 的唯一归一点(旧名 team → discuss + 响亮 warn),与 HTTP lane 的
+    // `gateScenarioRequest` 同一只属主。归一之后 `scenarioName` 只可能是现役主名——下面的墙钟/mcp/a2a
+    // 判据点按主名写,不做双名判。
+    const requested = canonicalScenarioName(args.scenario ?? config.defaultScenario, Object.keys(scenarios), logger);
     const scenarioName = scenarios[requested] ? requested : "default";
     // A scenario may THROW HttpError synchronously when a prerequisite is unmet (e.g. `scan` needs
     // GIT_API_BASEURL + a repo — which a one-shot CLI may not
@@ -721,7 +724,7 @@ export async function runLocal(argv, deps = {}) {
     const scope = args.user ?? "local";
     // Timeout policy mirrors the server (taskWallClockSec): run-local IS the pure single-user
     // TOC lane → NO wall clock by default (core's wedge safety-net still applies); explicit TASK_TIMEOUT_SEC
-    // wins with its raise-only floor (team 1500s — a multi-agent coordinator legitimately exceeds 600s).
+    // wins with its raise-only floor (discuss 3600s — a multi-agent coordinator legitimately exceeds the base).
     // [854]④ 不落此腿:per-request body.limits 是 HTTP body 车道(resolveTaskLimits,main.ts resolveSpec);
     // run-local 无 body,配速仍走 env(要 CLI flag 时另开件,别在这里半做)。
     // 🔴 2026-08-01 env fail-loud 族:原为 `Math.max(0, Math.floor(Number(env ?? "0")) || 0)` ——
@@ -730,7 +733,7 @@ export async function runLocal(argv, deps = {}) {
     // 且启动期零提示。改走 numEnv:非法值当场 fail-loud 并指名键与实际值。
     // (numEnv 的注释早就预言了这个失败模式,只是它没 export、跨文件够不到,于是这两处手写了。)
     const taskTimeoutSec = Math.max(0, Math.floor(numEnv("TASK_TIMEOUT_SEC", "0")));
-    const timeoutSec = taskWallClockSec(taskTimeoutSec, false, scenarioName === "team");
+    const timeoutSec = taskWallClockSec(taskTimeoutSec, false, scenarioName === "discuss");
     const mcp = mcpForScenario(config.mcpServers, scenarioName);
     // DESIGN-269 车1 件3(本腿半场):A2A peers 同样按场景过滤进 spec。**只有 center/config 基线这一半**
     // —— run-local 无 HTTP body,所以没有「调用方自带 peer」那条腿(与 [854]④ 的 body.limits 同姿势:

package/dist/task-mcp.js

@@ -91,8 +91,15 @@ function normalizeServer(e) {
         return null;
     }
     const spec = { name: o.name, transport };
-    if (Array.isArray(o.allowTools) && o.allowTools.every((a) => typeof a === "string"))
+    // #272(#269 车1 codex F1 的孪生修,2026-08-16):`allowTools` 是**收窄**字段,core 把缺席解释成
+    // 「不限制」——旧形「坏形丢键、server 照挂」= 调用方要求只挂一条,实际挂上远端全部工具(每条还可能
+    // 带 write 语义),收窄意图坏形时退化成放行。判据与 task-a2a.ts 同一句:**一个键在场就必须合法,
+    // 否则这条 server 整条不进**(null ⇒ 上层记 dropped 带名)。缺席仍合法=真「不限制」。
+    if (o.allowTools !== undefined) {
+        if (!Array.isArray(o.allowTools) || !o.allowTools.every((a) => typeof a === "string"))
+            return null;
         spec.allowTools = o.allowTools;
+    }
     // caller-trust-root (host-lane single-user): the user's own effect/elicitation choices are kept (CC-parity).
     if (typeof o.elicitation === "boolean")
         spec.elicitation = o.elicitation;

package/dist/task-workflow.d.ts

@@ -83,7 +83,7 @@ export declare function normalizeRetainSubagentSessions(raw: unknown): boolean |
  *  - SINGLE-USER turnkey(`requirePrincipal !== true`)= the user IS the superadmin → **NO wall clock**
  *    (undefined; core arms none — its separate wedge safety-net still catches a stuck tool call, so "no wall"
  *    never means "hangs forever"). CC has no whole-task decapitation either.
- *  - MULTI-TENANT: base 2400s (big tasks — council/debate/team — 3600s). (PAIR-REVIEW F-4 附带修:此行
+ *  - MULTI-TENANT: base 2400s (big tasks — council/debate/discuss — 3600s). (PAIR-REVIEW F-4 附带修:此行
  *    曾写 600s/1500s 与代码漂移——真值以下方 base 为准。)
  *  - Explicit `TASK_TIMEOUT_SEC` wins in ANY tenancy (the operator's deliberate wall) and keeps its documented
  *    raise-only floor (`Math.max` with the base, so a misconfigured low value cannot shrink a council budget).

package/dist/task-workflow.js

@@ -96,7 +96,7 @@ export function normalizeRetainSubagentSessions(raw) {
  *  - SINGLE-USER turnkey(`requirePrincipal !== true`)= the user IS the superadmin → **NO wall clock**
  *    (undefined; core arms none — its separate wedge safety-net still catches a stuck tool call, so "no wall"
  *    never means "hangs forever"). CC has no whole-task decapitation either.
- *  - MULTI-TENANT: base 2400s (big tasks — council/debate/team — 3600s). (PAIR-REVIEW F-4 附带修:此行
+ *  - MULTI-TENANT: base 2400s (big tasks — council/debate/discuss — 3600s). (PAIR-REVIEW F-4 附带修:此行
  *    曾写 600s/1500s 与代码漂移——真值以下方 base 为准。)
  *  - Explicit `TASK_TIMEOUT_SEC` wins in ANY tenancy (the operator's deliberate wall) and keeps its documented
  *    raise-only floor (`Math.max` with the base, so a misconfigured low value cannot shrink a council budget).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "7.27.0",
+  "version": "7.28.0-rc.1",
   "description": "Sema Server — the server/API implementation layer for Sema, wiring core, registry, model providers, and cloud agent execution. Built on @sema-agent/core.",
   "type": "module",
   "license": "BUSL-1.1",
@@ -54,7 +54,7 @@
     "build:binary:run-local:darwin-arm64": "bun build --compile --target=bun-darwin-arm64 src/run-local.ts --outfile dist/run-local-darwin-arm64"
   },
   "dependencies": {
-    "@sema-agent/core": "^5.36.0",
+    "@sema-agent/core": "^5.37.0",
     "@sema-agent/registry-core": "^0.16.0",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",