@sema-agent/server 7.43.0 → 7.44.0

package/dist/capabilities/scenarios.js

@@ -8,113 +8,31 @@ import { createDiscussionTools, discussionCoordinatorPrompt, getTeam, teamNames
 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
- * the operator configured — not Claude/Anthropic), so the agent never inherits the model's training-time
- * "I am Claude" hallucination.
- *
- * Live-caught incident (a deployment served by one model family described itself as running on a DIFFERENT
- * vendor's model, because that vendor's name was baked into this text):
- * NOTHING substrate-specific may be hardcoded here — onboard is multi-provider (any OpenAI-/Anthropic-
- * compatible endpoint, self-hosted vLLM included), so a baked maker name makes every deployment that is not
- * that maker's misstate its own substrate. Same for
- * the gateway protocol (the brain stack serves Anthropic-compatible routes too — routing brain +
- * createAnthropicBrain — so "OpenAI-compatible gateway" would be the same class of lie). Neutral wording
- * (zero core-seam need; interpolating the model id would need a `StablePromptContext.model`
- * seam and reads poorly for ugly preset ids). The anti-"I am Claude" design is kept — only the baked
- * substrate facts are removed.
- */
-export { SEMA_IDENTITY } from "./prompts/identity.js"; // copy moved to the bundle-data layer
+export { SEMA_IDENTITY } from "./prompts/identity.js";
 import { SEMA_IDENTITY } from "./prompts/identity.js";
-/**
- * Prompt provider for the branded `default` scenario: SEMA_IDENTITY on top of the ROLE base — the
- * task's own `body.systemPrompt`, or core's {@link DEFAULT_SYSTEM_PROMPT} when none. Core 1.243
- * (提示词主权批) appends the constitution structurally AFTER this role layer (harness
- * safety blocks + modes + memory guidance + the prefix-cache-safe `<user_memory>` tail), so identity
- * cannot displace the safety blocks. The pre-1.243 form (identity + `defaultPromptProvider.stableSystem`,
- * i.e. an ALREADY-assembled prompt) would now trip the migration guard (anchor-detect → pass-through +
- * `onError(phase:"prompt-constitution")`) — this role-only form is the guard-free contract.
- */
 export function semaIdentityProvider() {
-    // Lens-4 endgame (core 1.310, [1006]②/[1012]): the typed stableBlocks branch now carries core's OWN
-    // pass-through guard (M9-family anchor detection on identity declarations → provider-assembled,
-    // un-doubled) — the 0c3352f server-side fallback routing for the already-assembled input face is
-    // retired; the real-composer parity matrix keeps that face pinned byte-equal against the pre-M14 form.
     return {
-        // M14 (core 1.303, 板 [968]): the branded head is a TYPED block — the stable id "sema/identity" gives
-        // it a manifest section identity + digest (the G-1 observability gap; IDENTITY-DIGEST-MIGRATION.md
-        // route B, this hook is its carrier). identity-slot semantics: the block REPLACES core/role.base at
-        // the head position, so it must carry the FULL role layer (identity + role base) — byte-identical to
-        // the previous stableSystem string. Finer identity/role digest separation is the catalog-section
-        // endgame, not this hook's job.
         stableBlocks: (ctx) => [
             { id: "sema/identity", slot: "identity", text: `${SEMA_IDENTITY}\n\n${ctx.userSystemPrompt ?? DEFAULT_SYSTEM_PROMPT}` },
         ],
     };
 }
-/**
- * `code` 场景的提示词提供者([849] 造,[891] clay 裁定改名 autonomous→code):role 基底 = core
- * {@link CODE_SYSTEM_PROMPT}(core 1.298 [891] 改名批正名,旧名 FULL_BODY_SYSTEM_PROMPT=恒等
- * 别名过渡窗;CODE_AGENT persona + AUTONOMY_SELF_AUDIT + ANTI_VERBOSITY +
- * TOOL_PARAM_JSON;[891] 血缘定论 = CC 生产编码提示词的蒸馏去牌版,底本随 CC 版本对表 cc-anchors,
- * 非自研)——与 bench 的请求组装完全同源,引用 core 常量随版本走,绝不复制字符串(tb bench 实测:
- * 产品默认请求与同引擎 bench 态的差距根因就在这三件 persona/自检/终验)。品牌层与
- * {@link semaIdentityProvider} 同构:brandIdentity 开时 SEMA_IDENTITY 叠在 role 基底之上;任务自带
- * systemPrompt 按同一优先序赢过基底(role 合成规则与 default 场景一致)。宪法由 core 1.243 在 role
- * 层之后结构化追加——此处只产 role-only 形态(guard-free 契约,同 semaIdentityProvider 注释)。
- * 无 systemPrompt 且无品牌时原样返回 core 常量(测试以引用比对锁 bench 同源,不做字符串快照)。
- */
 export function codePromptProvider(brand) {
-    // [1158]/[1161]/[1162] b 案(clay 拍):provider 供给的字节 core 永不改写(provenance 卫,1.329),
-    // 所以 known-constant narrowing 够不着 provider 手里的 CODE_SYSTEM_PROMPT——simple 形的「裸底」
-    // 由 server 自己按 ctx.promptProfile 选 core 常量(CODE_AGENT_PROMPT=core 1.329 narrowing 的同一
-    // 目标常量,引用不复制,[891] 同源铁律)。classic 全链字节等价旧形;行为九段随 pack 走(平形
-    // stableSystem/stableBlocks 都不排段;server 从未用 replaceAll)。
     const roleBase = (ctx) => ctx.userSystemPrompt ?? (ctx.promptProfile === "classic" ? CODE_SYSTEM_PROMPT : CODE_AGENT_PROMPT);
-    // Unbranded: plain role layer via the string hook — core keeps its own core/role.base section identity,
-    // and the reference-equality bench-parity tests keep comparing the exact core constant.
     if (!brand) {
         return { stableSystem: (ctx) => roleBase(ctx) };
     }
-    // Branded: same M14 typed form as semaIdentityProvider (identity slot = role-layer replacement with the
-    // brand line on top; the base under the brand follows the SAME profile fork — the brand overlay is the
-    // legal divergence ([1134] 宪法二类), the base stays core-owned bytes).
     return {
         stableBlocks: (ctx) => [
             { id: "sema/identity", slot: "identity", text: `${SEMA_IDENTITY}\n\n${roleBase(ctx)}` },
         ],
     };
 }
-// [2400] CAPS-OPS-11:autonomousPromptProvider 别名导出已随场景退役删除(真身=codePromptProvider)。
-// 其 `@deprecated` JSDoc 曾残留于此,被 tsc 误挂到下方 buildScenarios(三处调用点全告 deprecated
-// ——TODO-3 立案的「迁移」实为孤儿注释,随删除清账;buildScenarios 本身非退役面)。
-/** #196 唯一取用口:场景按自己的判别位取子任务 Runner。场景体内一律不直接摸 `deps.subRunner` /
- *  `deps.handslessSubRunner` —— 两处各挑一次就是漂移的成因,判别位必须是唯一开关。 */
 function subRunnerFor(deps, hands) {
     return pickHandsRunner(hands, { full: deps.subRunner, handsless: deps.handslessSubRunner });
 }
 export function buildScenarios(deps) {
-    // The default scenario filters skills by "default" — NOT by req.scenario (which may be an unknown name
-    // that fell back here): the bundle must be a coherent "default" set, matching how main.ts resolves an
-    // unknown scenario to "default" for tools/prompt/mcp too (council finding — else default-tagged drop).
-    // 抽成具名工厂:`code` 直接复用它取 bundle(工具/技能面与 default 恒等由构造保证,不靠两处
-    // 各写一份 assembleCodeTools 参数再祈祷不漂移)。
     const defaultScenario = (req, _principal, ctx) => {
-        // gap-audit rank-1 BLOCKER: the default agent is the CC agent loop — it MUST have the
-        // full-body roster, not just nowTool. core's `assembleCodeTools` (1.161) ships TodoWrite (planning) +
-        // the subagent/Task delegation tool (runs on the sub-runner, child ⊆ parent — no escalation) + WebFetch.
-        // 🔒 WebFetch is GATED OUT on a multi-tenant deployment (REQUIRE_PRINCIPAL): allowHosts is unset = all PUBLIC,
-        // and core says a multi-tenant deployment MUST allowlist (an injected tenant model could exfil via an
-        // arbitrary public URL — the SSRF floor only blocks INTERNAL). Single-user TOC keeps it (the user's own box).
-        // WebSearch backend resolution: a per-request `body.settings.webSearch` (the user's shell settings) WINS, but
-        // ONLY on the single-user host lane (a per-request endpoint/key is a capability config — on multi-tenant a tenant
-        // could SSRF via a `searxng` URL pointed at an internal host, so multi-tenant uses ONLY the deployment-env
-        // `deps.webSearch`; design/107 axis, mirrors settings.env). Absent both ⇒ WebSearch not assembled (core ships none).
         const reqWebSearch = deps.requirePrincipal !== true
             ? webSearchConfigFromSettings(req?.settings?.webSearch)
             : undefined;
@@ -123,43 +41,13 @@ export function buildScenarios(deps) {
             tools: [
                 nowTool(),
                 ...assembleCodeTools({
-                    // [1900]/[1904]:WebFetch 摘要缝——键在场才铸(负控=修前字节形)。
                     ...(deps.webFetchSummarize ? { webFetch: { summarize: deps.webFetchSummarize } } : {}),
-                    // CC 201 parity: CC 201 makes the two planning families MUTUALLY
-                    // EXCLUSIVE — with TodoV2 (the Task trio) enabled, TodoWriteTool.isEnabled returns false and the
-                    // interactive model sees ONE family (TodoWrite survives only as an SDK/non-interactive compat slot).
-                    // Both-on was the CC 198 posture (live-caught cost: the model wastes a turn comparing the two tools
-                    // and juggles duplicate state). taskList:true below ⇒ TodoWrite OFF.
                     todoWrite: false,
-                    // core 1.215 (design/119): the structured task-list family (TaskCreate/TaskGet/TaskUpdate/TaskList —
-                    // stable ids, status transitions, dependencies); core defaults it OFF, the full-body deployment opts
-                    // in. Under CC 201 this family is the ONLY planning leg (see todoWrite above).
                     taskList: true,
-                    // #318([4659] F2 → [4692] 定谳):**会话级**清单店。缺这一键时 core 落
-                    // `store ?? createMemoryTaskListStore()` 的私有 per-run 臂,而本工厂是**每请求**调用的
-                    // (resolve-spec 的 selectScenario;resume 同链重解析)⇒ 同一会话每 turn 一只新店:
-                    // TaskList 中途报空、TaskCreate 从 #1 重铸号,已发给用户的任务回执从此指向别的任务。
-                    // 分区键 = 会话(同 session 跨 turn/跨 resume 连续,跨 session 互不可见);sessionId 只从
-                    // 鉴权解析的 {@link ScenarioContext} 取,绝不从 req(= 调用方自报的 body)取。
-                    // 无 sessionId 的调用形(parkedReviveTool 的裸 Agent 取用、能力详情探针)整键省略 ⇒
-                    // per-call 私店 = 修前字节形(那两条腿都不消费 task-list 家族)。
                     ...(ctx?.sessionId !== undefined && deps.taskListStoreFor
                         ? { taskListStore: deps.taskListStoreFor(ctx.sessionId) }
                         : {}),
-                    // core 1.206 (design/115 P3): `background` exposes CC's `run_in_background` on the Agent tool — the
-                    // child runs async under an `a*` task id (TaskOutput/TaskStop; ONE "later" completion notification;
-                    // parent teardown aborts orphans). Same trust envelope as the sync path (child ⊆ parent roster, same
-                    // rights) — only the scheduling is async, so no posture gate. owner/scope: core 1.365 BREAKING 升必填,
-                    // 但 core 仍 ctx-first(subagent.js `ctx.taskId ?? bg.owner` / `ctx.principal ?? bg.scope`)——引擎链
-                    // 每 spawn 恒带 ctx.taskId,这里的值是类型要求的兜底:scope="default" 与引擎链 `principal ?? "default"`
-                    // 同词([1509] 单租户拼法);owner 哨兵在 ctx.taskId 缺席的病态窗把行锚到无人可匹配的键(fail-closed
-                    // 方向,default-deny 谓词下不可读,绝不放大)。
-                    // core 1.364 agentStore = durable 写半场,与 RunnerDeps.backgroundAgentStore 同实例(deps 注入)。
-                    // core 1.382 checkpointStore/ensureChildSessionDurable = design/153 parked 状态机的「同车必接」
-                    // 一对([1561] 提货单①②,ScenarioDeps 字段注释详述);两者任一缺席 = 净是 pre-153 行为。
                     subagent: {
-                        // #196:default/code 的委派子代**要**手(CC parity;main.ts subRunner 注里那条 "subagent
-                        // couldn't run pwd" 缺陷就是这条腿缺手),故按本场景判别位取 full 支。
                         runner: subRunnerFor(deps, "full"),
                         background: {
                             registry: defaultTaskRegistry,
@@ -169,57 +57,26 @@ export function buildScenarios(deps) {
                             ...(deps.checkpointStore ? { checkpointStore: deps.checkpointStore } : {}),
                             ...(deps.ensureChildSessionDurable ? { ensureChildSessionDurable: deps.ensureChildSessionDurable } : {}),
                         },
-                        // core 1.287 extraTools seam ([795]/[802]③): per-spawn dynamic tool injection (SendUserFile
-                        // reaches the delegated-child roster; product still goes through resolveToolSubset).
                         ...(deps.subagentExtraTools ? { extraTools: deps.subagentExtraTools } : {}),
-                        // 历史复审轴B #3(1.254):extraTools 工厂 throw 的错误 sink——core 契约「absent ⇒ dropped after
-                        // the generic disclosure」= 部署日志零痕迹,只剩模型面固定 note。接 warn 让故障可观测。
                         ...(deps.subagentExtraTools && deps.logger
                             ? { onExtraToolsError: (err, info) => deps.logger?.warn?.("subagent_extra_tools_error", { ...info, err: err instanceof Error ? err.message : String(err) }) }
                             : {}),
                     },
                     ...(webSearch ? { webSearch } : {}),
-                    // A-033.1(#256):工具名取 core 的 `WEB_FETCH_TOOL_NAME` 而不是裸串 —— 这是**多租户闸**
-                    // (allowHosts 未设 = 全公网可达 ⇒ 一个租户能把另一个租户的内网可达面当出口)。core 改名该工具时,
-                    // 裸串比对恒不相等,闸门整条不生效且零症状:名单里照样挂着一只全公网 WebFetch。
                 }).filter((t) => t.name !== WEB_FETCH_TOOL_NAME || deps.requirePrincipal !== true),
             ],
-            // default/code 是手带并集的**故意消费者**(上方 rank-1 BLOCKER 注:CC agent loop MUST have the
-            // full-body roster)——#196 判别位在这里表态 full,收窄只落在声明了 none 的场景上。
             hands: "full",
             skills: skillsForScenario(deps.skills, "default"),
-            // Local/TOC deployment brands the neutral default scenario as Sema (so the local engine answers "who
-            // are you" as Sema, not the model's hallucinated identity). Cloud leaves it neutral unless opted in.
             ...(deps.brandIdentity ? { promptProvider: semaIdentityProvider() } : {}),
         };
     };
     return {
         default: defaultScenario,
-        // [849]→[891] code(原名 autonomous,clay 裁定改名+persona×终验解耦):与 default 完全同 roster
-        // (full-body 工具面 + default 技能面原样复用,连 WebFetch 多租户闸/WebSearch 装配都跟着 default
-        // 工厂走),只换一轴——role 基底 = core CODE_SYSTEM_PROMPT(CC 编码 persona 蒸馏版,见
-        // codePromptProvider)。**不再定死 finalVerification**([891] 解耦:终验是无人值守运行模式旋钮,
-        // caller 显式声明,交互态不多烧终验轮)。这是 [891] 起的出厂缺省场景(config DEFAULT_SCENARIO
-        // 缺省 "code")——编码产品出厂态对标 CC 出厂态;通用域中性 persona 的 default 保留为显式可选。
-        // 刻意走内建、不走 center overlay:overlay 已无 prompt 通道([1053] ScenarioEntry.prompt 直删,场景级提示词=center prompts binding)。
-        // #318:`ctx` 必须原样转给 default 工厂 —— 漏转 = 出厂缺省场景(DEFAULT_SCENARIO 缺省即 code)
-        // 拿不到会话级清单店,F2 在最常用的那条腿上原地复活([4659] 症状③ 钉的就是这一格)。
         code: (req, principal, ctx) => ({
             ...defaultScenario(req, principal, ctx),
             promptProvider: codePromptProvider(deps.brandIdentity === true),
         }),
-        // [891]→[2400] CAPS-OPS-11(clay 裁 2026-08-03,不留任何过渡):`autonomous` 过渡 alias 已退役。
-        // body 显式传它 ⇒ 5.1.0 起的 scenario_unknown 400 响亮拒(附现役词表);旧语义迁移形=
-        // scenario:"code" + body.finalVerification:true(终验自此=纯 caller 显式旋钮,场景层无定死)。
         "code-review": (req) => codeReview(deps, req),
-        // Neutral repo-readonly scenario (OA ask): the SAME clone-free read-only repo tools as code-review
-        // (repo_tree / repo_read_file / repo_pull_diff over GIT_API_TOKEN) with NO promptProvider — the
-        // objective and the center-distributed skills own the output contract. The reviewer framing was
-        // never a security control (the boundary is the token's scope + the read-only tool set); it only
-        // fought skill-driven outputs (live: oa-repo-scan loaded but the lead still wrote a review).
-        // Deliberately NOT the alternative "let a scenario-targeted skill override promptProvider": that
-        // would let runtime-distributed content rewrite the deployment-pinned system prompt and break the
-        // stablePrompt STABLE→VARIABLE prefix-cache discipline (design/12/17).
         scan: (req) => {
             const repoClient = requireRepoClient(deps, "scan");
             if (typeof req.repo !== "string" || !req.repo.trim()) {
@@ -227,28 +84,18 @@ export function buildScenarios(deps) {
             }
             return {
                 tools: [...repoToolsFor(repoClient, parseRepo(req.repo)), nowTool()],
-                // #196:头注的「工具集即边界」自此在**最终 roster** 上成立(修前 core 把手带 band 并集进来,
-                // clone-free 承诺只存在于这份声明里)。
                 hands: "none",
                 skills: skillsForScenario(deps.skills, "scan"),
             };
         },
-        // 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
+            const template = getTeam(name);
             if (!template) {
                 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: createDiscussionTools(subRunnerFor(deps, hands), template, { objective, businessContext, ...(deps.logger ? { logger: deps.logger } : {}) }),
@@ -259,39 +106,26 @@ export function buildScenarios(deps) {
         },
     };
 }
-/** 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 校验 ⇒ 当前不可利用,
-    // 本守卫是纵深防御(本函数是导出面,不得依赖单一调用方的入口校验)。
+    const resolved = name;
     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/discuss 工厂对良性请求无副作用可真调(拿真实工具名单);code-review/scan 是
- *  fail-loud 语义(缺 GIT_API 配置/principal 即 throw)→ 探针失败落静态表兜底(表↔工厂一致性由测试锁:
- *  测试喂 fake deps 真调工厂对账工具名)。enabled 对内建恒 true(约定②)。 */
 export function builtinScenarioDetails(scenarios, deps) {
     const probe = (name, req, principal, fallback) => {
         try {
-            return ((Object.hasOwn(scenarios, name) ? scenarios[name] : undefined)?.(req, principal)?.tools ?? []).map((t) => t.name); // P2-13 同族守卫
+            return ((Object.hasOwn(scenarios, name) ? scenarios[name] : undefined)?.(req, principal)?.tools ?? []).map((t) => t.name);
         }
         catch {
-            return fallback; // 工厂 fail-loud(部署未配该场景的后端)→ 静态名单(web 仍能展示工具面选项)
+            return fallback;
         }
     };
     const REPO_TOOLS = ["repo_tree", "repo_read_file", "repo_pull_diff", "Now"];
     const mk = (name, summary, toolset, tools, promptSummary) => ({
         name, source: "builtin", builtin: true, summary, toolset, tools, promptSummary, enabled: true,
-        // [C132]:可用性与上面的静态回退表分家 —— 回退表答的是「工具面长什么样」(缺配置时也照画),
-        // 这两个键答的是「现在点下去会不会 501」。同一份属主判据,内建与 center 两条产线共用。
         ...availabilityFields(deps, toolset),
     });
     return {
@@ -301,13 +135,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 拥有输出契约)"),
-        // #273 / C-R14:旧名 `team` 不再是一条**被声明**的场景(它只是 SCENARIO_ALIASES 里的入口别名)——
-        // 列举面只列现役主名,免得消费方把别名当成第二条能力画上去。
-        discuss: mk("discuss", "多智能体讨论圆桌(模板成员+synthesizer,模板可由 registry 配置)", "discuss", probe("discuss", {}, undefined, ["run_discussion", "run_team"]), "讨论协调者提示词(圆桌纪律+合成流程)"),
+        discuss: mk("discuss", "多智能体讨论圆桌(模板成员+synthesizer,模板可由 registry 配置)", "discuss", probe("discuss", {}, undefined, ["run_discussion"]), "讨论协调者提示词(圆桌纪律+合成流程)"),
     };
 }
-/** center 条目详情(有效性判定与 centerScenarios 完全同款:无效条目既不进 overlay 也不进详情——
- *  保证约定①「详情显示的来源=运行实际用的定义」永不错位)。 */
 export function centerScenarioDetails(specs, builtinNames, deps) {
     const out = {};
     for (const spec of specs ?? []) {
@@ -315,23 +145,17 @@ 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 同族守卫
+            continue;
         out[spec.name] = {
             name: spec.name,
             source: "center",
             builtin: builtinNames.includes(spec.name),
-            summary: "", // center spec 无 notes 字段(回落空串;registry 侧加 notes 后在此透传)
+            summary: "",
             toolset: spec.toolset,
             tools: spec.toolset === "repo-readonly" ? ["repo_tree", "repo_read_file", "repo_pull_diff", "Now"] : ["Now"],
-            // [1053] ScenarioEntry.prompt 已删(scenario 级提示词=center prompts binding 单入口)——center 条目
-            // 恒空串;字段本身保留(builtin 条目仍有真值,wire 形不变)。
             promptSummary: "",
             enabled: true,
-            // [C132]:center 声明的 repo 型场景与内建的 scan/code-review 受**同一份**判据管辖
-            // ——overlay 不是判据的第二属主。
             ...availabilityFields(deps, spec.toolset),
         };
     }
@@ -352,47 +176,28 @@ const TOOLSETS = {
     },
 };
 const SCENARIO_AVAILABLE = { available: true };
-/**
- * 🔴 场景可用性的**唯一属主**。列举面(`ScenarioDetail.available` / `unavailableReason`)与请求面
- * ({@link requireRepoClient} 的 501 拒绝臂,三处调用点)都只从这里取值——两处各写一份就是本仓反复
- * 吃过的「同一语义两个属主」病:判据一漂,列举面开始说谎而没人先红。一致性由 capabilities.test 的
- * **对表格**逐名钉住(`available:false` ⟺ 良性请求真吃 501),而不是靠这段注释。
- *
- * 判据键 = **toolset**:内建详情与 center 条目都带这个字段,故两条产线天然共用同一份判据。
- * `requiresRepo` 的 toolset 需要部署配好 git 后端(`GIT_API_BASEURL` ⇒ `deps.repoClient`)。
- * 词表外的 toolset(内建的 `full-body`/`discuss`)不依赖后端 ⇒ 恒可用。
- */
 export function scenarioAvailability(deps, toolset) {
-    if (Object.hasOwn(TOOLSETS, toolset) && TOOLSETS[toolset]?.requiresRepo === true && deps.repoClient === undefined) { // P2-13 同族守卫
+    if (Object.hasOwn(TOOLSETS, toolset) && TOOLSETS[toolset]?.requiresRepo === true && deps.repoClient === undefined) {
         return { available: false, reason: "git_client_unconfigured" };
     }
     return SCENARIO_AVAILABLE;
 }
-/** 拒绝文案的唯一属主:闭集穷举 switch(新增原因词不在这里表态即编译红)。 */
 export function scenarioUnavailableMessage(reason, scenarioLabel) {
     switch (reason) {
         case "git_client_unconfigured":
             return `${scenarioLabel} scenario needs GIT_API_BASEURL configured`;
     }
 }
-/** repo 型场景取 git 客户端的唯一口(三处场景工厂同源)。不可用 ⇒ 按属主给的原因与文案 501 响亮拒。 */
 function requireRepoClient(deps, scenarioLabel) {
     const client = deps.repoClient;
     if (client !== undefined)
         return client;
     const verdict = scenarioAvailability(deps, "repo-readonly");
-    // 判成 available 却没有客户端 = 属主与消费面脱钩(对表格会先红)。此处仍 fail-loud,不静默放行。
     throw new HttpError(501, verdict.available
         ? `${scenarioLabel} scenario has no repo client although the availability owner reports it available (wiring defect)`
         : scenarioUnavailableMessage(verdict.reason, scenarioLabel));
 }
 export const SCENARIO_NAME_RE = /^[a-z][a-z0-9-]{1,31}$/;
-// ([1053] registry-core 0.10.15:SCENARIO_PROMPT_MAX 随 ScenarioEntry.prompt 一并退役)
-/**
- * Build the center-declared scenario overlay. Invalid specs are SKIPPED with a warning (never fail
- * boot — same posture as skills/teams); valid ones become scenarios keyed by name, ready to be merged
- * OVER the built-ins (center wins). Returns the overlay plus which built-in names it shadows.
- */
 export function centerScenarios(deps, specs, builtinNames, logger) {
     const overlay = {};
     const shadows = [];
@@ -403,30 +208,15 @@ 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 同族守卫
+        const toolset = Object.hasOwn(TOOLSETS, spec.toolset) ? TOOLSETS[spec.toolset] : undefined;
         if (!toolset) {
             logger?.warn("sema_registry_scenario_invalid", { name: spec.name, reason: `unknown toolset "${String(spec.toolset)}" (have: ${Object.keys(TOOLSETS).join(", ")})` });
             continue;
         }
-        // [1053] registry-core 0.10.15:ScenarioEntry.prompt 直删(clay 亲裁)——center 场景的提示词通道收敛为
-        // center prompts binding(scenario 维,[1050]①a/[1051]③a);overlay 只组装工具面+技能面,提示词由投影腿
-        // (effective 声明数组→core stableBlocks,[1054]③ 已认领)在 binding 落地后统一承载。
         const name = spec.name;
         overlay[name] = (req) => ({
             tools: toolset.build(deps, req),
-            hands: toolset.hands, // #196:表态随 toolset 走(center 声明面不可自选 hands —— 能力仍是代码定死的)
+            hands: toolset.hands,
             skills: skillsForScenario(deps.skills, name),
         });
         if (builtinNames.includes(name))
@@ -443,34 +233,19 @@ function codeReview(deps, req) {
     const repoTools = repoToolsFor(repoClient, coords);
     const skills = skillsForScenario(deps.skills, "code-review");
     const objective = typeof req.objective === "string" ? req.objective : "Review this repository.";
-    // Tiering: `council: true` runs the multi-lens council (L1 parallel lenses + L3 arbiter) — for
-    // high-value/whole-repo review (~15× tokens). Default = the lead reviews the in-scope files DIRECTLY
-    // (cheap, reliable, finishes fast). A live run showed the model self-orchestrates unreliably, so for
-    // review (a KNOWN decomposition) the subagent fan-out is CODE-driven here, not left to the model
-    // (deterministic + cheaper + cacheable; see design/35). For OPEN-ENDED tasks where the decomposition
-    // isn't known, core's `createSubagentTool` (model-driven self-delegation, with maxDepth / isolated
-    // context / compressed-report guardrails) is the right tool — wire it in a dedicated scenario then.
-    // #196:两条腿(直评 / council)都声明 none —— 直评腿的 lead 只读仓库工具,council 腿的 lead 只调
-    // run_council;lens/arbiter 子任务同样只读仓库,故 council 工具拿无手 subRunner。
     const hands = "none";
-    // [C143]:lenses 非 number 形响亮拒——此前 string[]/任意形静默滑过(typeof 门恒 false 整键落空),
-    // client-core 0.22.0 曾按想象契约钉 string[],用户发出的键被静默吞([C142] web-client wire 实证)。
-    // 与 (a) 案(client-core 改 number)对齐后客户端不会再发该形;本 400 是防第三方直调的纵深。
     if (req.lenses !== undefined && typeof req.lenses !== "number") {
         throw new HttpError(400, "lenses must be a number (council lens COUNT, 1-6) — a named lens subset is not a request-level knob", { code: "request.field_invalid" });
     }
     if (req.council === true) {
-        const rounds = clampRounds(req.rounds); // finite-guarded (NaN/±Inf → undefined → council default 1)
+        const rounds = clampRounds(req.rounds);
         return {
             tools: [
                 createCouncilTool(subRunnerFor(deps, hands), repoTools, objective, {
                     metrics: deps.metrics,
                     logger: deps.logger,
-                    debate: req.debate === true, // L1+L2+L3 (peer debate) vs L1+L3
-                    // OA cost/coverage dial: an optional structured lens COUNT (clamped to [1,6] + NaN-guarded in pickLenses;
-                    // absent = all 6 → zero regression). Per-request, no restart — orthogonal to the lens MODEL (startup env).
+                    debate: req.debate === true,
                     ...(typeof req.lenses === "number" ? { lensCount: req.lenses } : {}),
-                    // Caller-settable debate rounds (finite, clamped [1,3]; absent/NaN = default 1). Only when debate=true.
                     ...(rounds !== undefined ? { rounds } : {}),
                 }),
             ],
@@ -479,31 +254,16 @@ function codeReview(deps, req) {
             promptProvider: coordinatorPrompt,
         };
     }
-    // [C144]([3296]⑤ web-client 实证):直评腿补 nowTool 与 scan 对齐——此前真装配无 Now 而 capabilities
-    // 声明 fallback 表 REPO_TOOLS 含 Now(repoClient 缺席时 probe 落 fallback 多报一枚=声明/装配错位;
-    // scan 当年照本场景抄还多加了 Now)。对齐后 fallback 表自动变准,评审报告带时间戳同样合理。
     return { tools: [...repoTools, nowTool()], hands, skills, promptProvider: directReviewerPrompt };
 }
 const reviewBody = "Produce ONE prioritized review: a short summary, then findings grouped by severity " +
     "(blocker / major / minor), each with `path:line`, the problem, and a concrete fix. Cite real code — never invent files or symbols.";
-// Each provider supplies ONLY its stable base; `stablePrompt` enforces STABLE→VARIABLE ordering
-// (base, then userSystemPrompt, then per-user memoryBlock) so the prefix-cache discipline can't be
-// got wrong by hand (design/12, design/17).
-/** Default: the lead reads the in-scope files and reviews them directly. */
 const directReviewerPrompt = stablePrompt("You are a senior code reviewer. Call repo_tree to map the repository, then repo_read_file to read " +
     "the files in scope, then review them yourself. " +
     reviewBody);
-/** Council mode: the lead just runs the (code-driven) council tool and returns its result verbatim. */
 const coordinatorPrompt = stablePrompt("You coordinate a code-review council. Call `run_council` exactly once (no arguments). When it " +
     "returns the arbitrated review, output that review as your final answer VERBATIM — do not " +
     "summarize, shorten, or rewrite it.");
-/**
- * Personalization seam: merge the caller's own skills AFTER the scenario's, with
- * SCENARIO-WINS on a name clash — the security baseline (scenario/center skills) can never be shadowed
- * by user content. Duplicate names within the user list keep the first. Clashes are logged for audit
- * (silent drops would make "my skill didn't fire" undebuggable). Input is already shape/size-validated
- * by the HTTP layer (validateUserSkills); this stays pure merge policy.
- */
 export function mergeUserSkills(scenarioSkills, userSkills, logger) {
     if (!userSkills || userSkills.length === 0)
         return scenarioSkills;
@@ -515,52 +275,31 @@ export function mergeUserSkills(scenarioSkills, userSkills, logger) {
             dropped.push(s.name);
             continue;
         }
-        reserved.add(s.name); // also dedupes within the user list itself (first wins)
+        reserved.add(s.name);
         out.push(s);
     }
     if (dropped.length > 0)
         logger?.warn("user_skills_dropped", { reason: "name reserved by scenario (or duplicate)", names: dropped });
     return out;
 }
-/**
- * resolveSpec 的执法入口(指派为默认、body.scenario 可换但限 allowlist)。返回本请求的
- * 生效场景名(未做 unknown→default 回退——那是 resolveSpec 既有职责,保持单点)。
- *
- *   - body.scenario 显式给出:allowlist 非空且集外 ⇒ typed 拒绝(400 `scenario_not_allowed`,附 allowlist
- *     ——机器码归 wire、人话归壳/web);集内 ⇒ 用户主动切换赢。allowlist 为空(无 ruling / 该 principal
- *     三层皆无指派 / caps 面故障)⇒ 无治理约束,现状放行(与「null 落兜底链」同一语义:分配面未覆盖 =
- *     不收紧,恒不比没有治理时更宽;caps 故障不把用户锁死在 default——场景切换不是权限放大面,fail-open
- *     到现状,与 workflows 面的 fail-closed 是刻意的 posture 差异,见 runtime-caps-resolver)。
- *   - body.scenario 未给:ruling 胜者 ⇒ 指派为默认;无胜者 ⇒ defaultScenario 现状链。
- */
 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 死)。
+        const requested = 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.map((n) => canonicalScenarioName(n, known)).includes(requested)) {
+        if (allowed.length > 0 && !allowed.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 requested;
     }
-    // 指派面(ruling.scenario)/部署面(DEFAULT_SCENARIO)同样过归一:两者都是**配置里写的名字**,
-    // 旧名不归一就会落到 resolveSpec 的 unknown→default 回退上——静默换场景,正是本窗要避免的。
-    return canonicalScenarioName(ruling?.scenario ?? defaultScenario, known, logger);
+    return ruling?.scenario ?? defaultScenario;
 }
 //# sourceMappingURL=scenarios.js.map

package/dist/capabilities/select-environment-tool.js

@@ -1,35 +1,7 @@
-/**
- * RFC A2 (sema-internal server/docs/design/ENV-SELECT-AND-REGION-SOURCE.md) — the model-facing `SelectEnvironment` tool.
- * A 切片先行;挂载路线 = RFC 判定②(a):deployment 经 `spec.tools` 注入(同 lsp/
- * 自定义工具),core 收编等真用起来再谈。
- *
- * Backend = the EXISTING trusted admission chain, nothing new:
- *  - discovery: `ImageIndex.list({latestOnly, status:'published', viewer})` — the SAME per-principal
- *    visibility the `/v1/images/select` catalog applies (SQL-baked, never caller enumeration).
- *  - selection: `resolveSandboxImageRef` (fail-closed profile→digest re-admission).
- *  - binding: a session-keyed PROFILE (intent — never a digest) the next task's resolveSpec re-resolves
- *    FAIL-CLOSED, exactly like a body-supplied `sandboxImageProfile`. Storing the profile (not the ref)
- *    keeps the re-admit discipline intact: every task re-resolves LIVE, a stale digest can never ride a
- *    session binding past admission.
- *
- * Boundary contract (verbatim in the tool's model-facing note): a binding change takes
- * effect ONLY at a task boundary; any child (including design/129 session-scoped background children)
- * inherits the binding at its spawn moment and never drifts mid-flight. This tool therefore only writes
- * the session-profile store — the RUNNING task's sandbox is untouched.
- *
- * 409-style self-correction: a failed selection returns `missing` + the viewer-visible catalog
- * (tenant-neutral profile names only — the list enters model context).
- */
 import { Type } from "typebox";
 import { BoundedSessionMap } from "../bounded-session-map.js";
 import { resolveSandboxImageRef } from "../per-task-image.js";
-/** Session-keyed selected PROFILE (intent). Mirrors PerTaskImageRegistry's bounded-eviction shape, but holds
- *  the profile string so every subsequent task re-resolves fail-closed (re-admit discipline). In-memory —
- *  honest v1 boundary: a worker restart drops the selection (the model can re-select; nothing fails closed
- *  the wrong way, the session just falls back to the worker default image). */
 export class SessionEnvironmentSelection {
-    // #97 R11: same BoundedSessionMap basis as PerTaskImageRegistry (composition, not inheritance) — this
-    // class's own ctor/method surface is unchanged.
     bounded;
     constructor(maxEntries = 4096) {
         this.bounded = new BoundedSessionMap(maxEntries);
@@ -46,7 +18,6 @@ const capList = (caps) => Object.entries(caps ?? {})
     .map(([k]) => k);
 async function availableProfiles(catalog, viewer) {
     const { entries } = await catalog.list({ ...viewer, status: "published", latestOnly: true, limit: 100 });
-    // tenant-neutral: profile name + boolean capability keys only (this list enters model context).
     return entries.map((e) => ({ profile: e.profile, capabilities: capList(e.capabilities) }));
 }
 export function selectEnvironmentTool(deps) {
@@ -58,7 +29,6 @@ export function selectEnvironmentTool(deps) {
             "The change takes effect for the NEXT task/subagent — the current sandbox is not swapped mid-run; " +
             "running work keeps the environment it started with, and artifacts hand over via the workspace/git. " +
             "Use this instead of hand-installing SDK-level toolchains (Android SDK, JVM, browsers, …).",
-        // set-to-value on a session-keyed map: repeat-safe with the same args.
         effect: "idempotent",
         parameters: Type.Object({
             profile: Type.Optional(Type.String({ description: "Target image profile name (from the available list). Omit to discover." })),
@@ -83,7 +53,6 @@ export function selectEnvironmentTool(deps) {
                 index: deps.catalog,
             });
             if (!resolved.ok) {
-                // self-correction payload: the error + the viewer's own catalog. Model retries with a valid one.
                 const available = await availableProfiles(deps.catalog, viewer);
                 return {
                     content: JSON.stringify({ error: resolved.message, ...(caps.length > 0 ? { missing: caps } : {}), available }),
@@ -91,7 +60,6 @@ export function selectEnvironmentTool(deps) {
                 };
             }
             if (!sessionId) {
-                // outside a Runner session there is nothing to bind to — honest failure, not a silent success.
                 return { content: JSON.stringify({ error: "no session to bind the environment selection to" }), details: { mode: "select-failed" } };
             }
             deps.selection.set(sessionId, a.profile);