@sema-agent/server 7.43.0 → 7.44.0

package/dist/run-local.js

@@ -1,47 +1,4 @@
 #!/usr/bin/env node
-/**
- * `run-local` — a ONE-SHOT local CLI for the agent engine.
- *
- * Boots the SAME runtime as `src/main.ts` (createBrain + Runner + the scenario/skills capability layer +
- * the host execution env) IN-PROCESS, runs ONE task from the CLI objective to completion, prints the
- * TaskResult, and exits. There is NO long-running HTTP server and NO submission auth gate — this is the
- * whole point: it removes two friction points (the SERVICE_AUTH_TOKEN 503 on submit and the
- * manual server lifecycle). The user fills `~/.ai-agent/.env` + `config.d/` (the LOCAL config source) and
- * just runs `run-local "<objective>"`.
- *
- * Posture: LOCAL config mode (CONFIG_PROVIDER=local) → createConfigProvider → LocalConfigProvider →
- * applyEffective (config.d/.env drives models/roles/mcp), and the `host` exec lane (run on THIS machine,
- * no container) — identical building blocks to the server path so behavior matches (no drift). It reuses
- * main.ts's helpers verbatim; the only thing it skips is the server-only surface (createHttpServer, listen,
- * auth/rateLimit/quota/run-store/leader/durable-approval-decide/reapers).
- *
- * 🔴 **DEPLOYMENT GOVERNANCE IS NOT IN THAT SKIP LIST** (design/181 件三 / #180). Until 7.4.x this file
- * assembled its `TaskSpec` with the governance chain entirely ABSENT — `loadConfig` + `applyEffective` had
- * already parsed `autonomy` / `commandPolicy` / `sensitiveWritePatterns` into the config, and the spec
- * literal simply never read them (compute-then-discard), so the same operator knob was live on the HTTP leg
- * and structurally non-existent here. It now goes through the SAME single construction port as the other two
- * legs ({@link applyLocalGovernance} → `src/deployment-governance.ts` → `applyRuntimeGovernance` → core's
- * `tightenTaskSpec`). What this leg genuinely does NOT have is the **durable approval** face (a one-shot CLI
- * has no `/v1/approvals/:id/decide` leg to resume from), so the approval baseline is the adjudicated
- * allow-all arm and a gated `ask` is answered by {@link createLocalApprover} — the TTY human, or a
- * fail-closed deny — instead of parking a checkpoint nobody will ever redeem.
- *
- * 🔴 **design/201 的 permissionMode → shellGate 翻译表 SCOPED-OUT 本腿**(设计稿 §5,显式裁定而非欠账)。
- * 这条腿的 operator 就是亲手起这个进程的用户,它**没有 permission mode 这个概念**(一次性 CLI 收不到
- * 客户端表态),今昔都落 core 的缺省 `shellGate: off`。给它硬塞一个 classify 档,在没有 HITL 面的形态下
- * 等于把每一次 shell 调用送进 auto-deny —— 那不是加固,是废掉 run-local。部署治理段(上一段)照旧全接:
- * `MANUAL_MODE_SHELL_GATE` 想要门,operator 在自己的 `.env` 里说一句就有。同族的另一条 scoped-out 是
- * parked-revive 赎回腿(body 全盲,core 的 `InheritedGate` 以 `max(seed, live)` 兜底,自洽)。
- * 「三腿不共享翻译点」是设计,不是漏接:名册对账钉在
- * `test/operator-knob-client-posture-matrix.test.ts`(`shellGateForMode` 已并入构造点名册,第四条腿哪天
- * 接上它必须同时挂矩阵腿)。
- *
- *   Usage:  run-local "<objective>"  [--root <dir>] [--json] [--scenario <name>]
- *
- * `main()` is a thin wrapper over the testable {@link runLocal}, which takes argv + injectable
- * deps (a mock Brain, a captured logger/printer, and an `exit` shim) so the assembly + one-shot flow can be
- * exercised deterministically with no real LLM / network / keys.
- */
 import { homedir } from "node:os";
 import { join } from "node:path";
 import { realpathSync } from "node:fs";
@@ -65,7 +22,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, canonicalScenarioName } from "./capabilities/scenarios.js";
+import { buildScenarios, selectScenario, centerScenarios } from "./capabilities/scenarios.js";
 import { createTaskListLane } from "./boot/task-list-lane.js";
 import { pickHandsRunner, withoutExecutionEnv } from "./capabilities/hands-lane.js";
 import { HttpError } from "./security.js";
@@ -74,14 +31,13 @@ import { createMemorySyncRunner, createMemorySyncTransport } from "./memory-sync
 import { buildPricing, cappedCeiling, createTracer } from "./budget.js";
 import { createSharedRunnerDeps } from "./boot/runner-deps.js";
 import { createGovernanceSeams } from "./boot/governance-seams.js";
-import { assertRetentionLaneWirable } from "./boot/retention-lane.js"; // #270 车2:lane 自持门(本地形恒无执行器)
+import { assertRetentionLaneWirable } from "./boot/retention-lane.js";
 import { createOrgMemoryAdmissionWiring } from "./boot/org-memory.js";
 import { createPermissionDeniedMeter } from "./observability/tool-trace.js";
 import { createKeyResolver } from "./key-resolver.js";
 import { createLogger } from "./observability/logger.js";
 import { createMetrics } from "./observability/metrics.js";
 import { installSecretEnvScrubRecorder } from "./observability/secret-env-scrub.js";
-/** Parse argv (everything AFTER `node run-local.js`). Throws a clear Error on a missing objective. */
 export function parseArgs(argv) {
     let objective;
     let root;
@@ -92,11 +48,6 @@ export function parseArgs(argv) {
     let json = false;
     const valueFlag = (i, name) => {
         const v = argv[i];
-        // 空串/纯空白 = **没给参数**,不是"用户就想要空"(core [1689] 第 3 条同款:`??` 兜不住 `""`)。
-        // 收下它会让空串变成**隔离键**:`--session ""` → `args.session ?? uuidv7()` 得到 `""`,所有这类调用
-        // 复用同一个空 id「会话」;`--user ""` → `args.user ?? "local"` 得到 `""`,长期记忆落进匿名桶而不是
-        // 文档写的默认身份,且「传空串」与「不传」成为两个不同的桶。在解析器这一层拒才对 —— 这个函数存在的
-        // 意义本就是「这个 flag 需要一个参数」。
         if (v === undefined || v.trim() === "" || v.startsWith("--"))
             throw new UsageError(`${name} needs an argument`);
         return v;
@@ -122,7 +73,7 @@ export function parseArgs(argv) {
             throw new UsageError(`unknown flag: ${a}`);
         }
         else if (objective === undefined) {
-            objective = a; // first positional = the objective
+            objective = a;
         }
         else {
             throw new UsageError(`unexpected extra argument: ${a} (quote the objective as one argument)`);
@@ -133,35 +84,15 @@ export function parseArgs(argv) {
     }
     return { objective, root, json, ...(scenario ? { scenario } : {}), ...(session ? { session } : {}), ...(workspace ? { workspace } : {}), ...(user ? { user } : {}) };
 }
-/** A bad-usage error → print to stderr + exit 2 (distinct from a task failure exit 1). */
 export class UsageError extends Error {
 }
-/**
- * The model GATEWAY pre-flight (mirrors the doctor message): the engine cannot run a real
- * task without (a) a gateway base URL that ends in `/v1` and (b) the gateway/model API key resolvable from
- * env. We surface a "you still need to set: …" list rather than letting the first brain call crash with a
- * cryptic auth/connect error. Returns a list of missing items (empty = OK).
- *
- * NOTE: with an injected mock `brain` the gateway is irrelevant (no real call is made), so the caller skips
- * this check in that case — the check is about a REAL run, not the assembly.
- */
 export function missingGatewayRequirements(config) {
     const missing = [];
-    // (a) base URL: loadConfig always has a default, but a real local user must point it at THEIR gateway and
-    //     it must carry the OpenAI-compatible `/v1` suffix (the brain appends `/chat/completions`).
     if (!config.gatewayBaseUrl || !/\/v1\/?$/.test(config.gatewayBaseUrl)) {
         missing.push("MODEL_GATEWAY_BASEURL (the OpenAI-compatible gateway URL, must end in /v1)");
     }
-    // (b) the key: either the single gateway key (MODEL_API_KEY) OR — when the catalog pins a per-model
-    //     apiKeyEnv (sema-registry / config.d) — that named env var must be present. A model without its own
-    //     apiKeyEnv falls back to the gateway key, so the gateway key is the floor.
     const perModelEnvs = Object.values(config.modelApiKeyEnv ?? {});
     const haveGatewayKey = !!config.gatewayApiKey;
-    // The gateway key is the FLOOR: per-model keys only WAIVE it when EVERY catalog model the resolver may be
-    // asked about carries (and has set) its own apiKeyEnv. A model with no per-model key falls back to the
-    // gateway key, so a MIXED catalog (some models keyed, some not) with the gateway key unset would crash on
-    // the unkeyed model's first brain call. We dedupe via the model objects' `.name` so the synthetic `default`
-    // / model-id ALIAS entries of config.models (which mirror an existing per-name model) are not over-counted.
     const catalogModelNames = new Set(Object.values(config.models ?? {}).map((m) => m.name));
     const allModelsHaveOwnKey = catalogModelNames.size > 0 &&
         [...catalogModelNames].every((n) => {
@@ -180,47 +111,9 @@ export function missingGatewayRequirements(config) {
     }
     return missing;
 }
-/**
- * design/181 件三:run-local 腿的**部署治理链装配**(#180)。
- *
- * 与另外两条腿(HTTP 的 `resolveSpec`、durable park 的赎回腿)装的是**同一条**链,经**同一个**构造口:
- * 审批基线作 base 的 `toolPolicy` 座,再经**折叠属主** `applyRuntimeGovernance`(→ core `tightenTaskSpec`)
- * 叠上部署治理段(autonomy / commandPolicy / MANUAL_MODE_SHELL_GATE / 守卫集)。本函数一条 policy 都不
- * 自己合成。
- *
- * · **审批基线 = adjudicated allow-all**:一次性 CLI 没有 durable 审批设施(没有 `/decide` 腿可赎回),
- *   所以 `createApprovalBaselinePolicy` 走 durable 缺席那一臂。它是一条**在场的** effect-aware 策略
- *   (满足 core 的 `hasEffectAwareGate`),运维照旧用 `AUTONOMY` / `commandPolicy` / 守卫集在其上收紧。
- * · **裁决 env 恒 host 形,锚 `workspaceDir`**:run-local 的手就跑在这台机器的这个目录上
- *   (`--workspace` / config.d workdir / cwd 三选一,调用方已解析好),所以 `cwd` 恒在场 —— 相对形写目标
- *   由 core 按 `rootPath` 解析进真身裁决,构造口的词法补层(沙箱腿那条)在这里自动不铺。
- *   ✅ **旧残余面已收口(core 5.19.0 #108,2026-08-08 校正)**:`rootPath` 是装配期的**静态**值,而 core
- *   的写工具解析相对形用的是被 Bash `cd` 就地改写的活 cwd —— 于是 `cd .git/hooks` 之后
- *   `Write("pre-commit")` 落进守卫段却判不出来(两条 host 腿同形,本腿与 resolve-spec)。5.19.0 起守卫
- *   按 `ToolCallRequest.cwd`(引擎每次调用从同一只 tracked cwd 盖戳)解析写目标,本腿零改动即得保护;
- *   **不对称是 core 故意的**:目标跟活 cwd 走,守卫自己配置的目录仍锚静态根,`cd` 搬不动栅栏。全文与
- *   证据见 `deployment-governance.ts` 的 `RelativeTargetLexicalEnv` 顶注,端到端正控钉见
- *   test/run-local.test.ts(该钉已由 🟡 特征化翻成 🔴 正控)。
- * · **禁 memoize**:四个旋钮都是热改字段,每次装配现读活 config(与另两条腿同一姿势)。
- */
 export function applyLocalGovernance(base, config, workspaceDir) {
     return applyRuntimeGovernance({ ...base, toolPolicy: createApprovalBaselinePolicy(config) }, createDeploymentGovernanceInputs(config, { env: new NodeExecutionEnv({ cwd: workspaceDir }), cwd: workspaceDir }));
 }
-/**
- * design/181 件三:**onAsk 座**(§0 潜雷 / §5 锁 6)。
- *
- * 🔴 为什么这个座位是接治理链的**同窗必做项**:run-local 有 checkpointStore(file backend),所以
- * `AUTONOMY=ask` ⇒ `shellGate:"always"` ⇒ Bash 进 `irreversibleTools` ⇒ park lane effective ⇒ **每一次
- * shell 调用都 durable park 成一张永远没人 resume 的 checkpoint**,任务挂起、CLI 退 1。一次性 CLI 里
- * 没有任何赎回腿,那不是「等人来批」,是卡死。core 的 `isLiveApproverSeat(onAsk)` 为真时 `suspendAsk`
- * 早退(prepare-task dist 亲读),ask 于是落回本回调 —— 把 park 换成「问人 / 当场拒」的唯一正当接法。
- *
- * ⛔ **不在 toolPolicy 层做 ask→deny 映射**:core 自己就有 headless auto-deny 的语义与文案,在策略层
- * 复刻一份 = 同源谎(两处判据日后各改各的)。裁决归 core,座位归这里。
- *
- * 🔴 非 TTY 臂答 `false`(真 deny),**绝不答 `"unavailable"`**:后者被 core 读成「席位够不到」并**改道
- * `suspendAsk`**(dist `core/hooks.js:296` 的 `approverUnavailable` 重投),上面那颗雷会原样回来。
- */
 export function createLocalApprover(io) {
     return async (req, signal) => {
         if (!io.isTty) {
@@ -232,15 +125,6 @@ export function createLocalApprover(io) {
         return io.askYesNo(`approve "${req.toolName}"? ${req.message} [y/N] `, signal);
     };
 }
-/** 默认的 TTY 问人器:一问一答,回答写 **stderr**(stdout 是任务结果的专用管道,别污染它)。
- *  streams 可注入=EOF/abort 两臂测得动(默认 process.stdin/stderr)。
- *
- *  🔴 决断三臂(codex 验收轮 high,红先修):`readline/promises` 的 `question` 在输入流 EOF/close 时
- *  **不决**(promise 悬挂)——Ctrl-D、关闭的 stdin、任务取消都会把 runLocal 永久挂住,文件后端的锁
- *  跟着被拖住,下一次同 root 调用直接卡死。三臂全部 fail-closed 决 false:
- *   · `signal` abort(core `OnAsk` 递进来的取消,含预先 aborted);
- *   · readline `close`(输入流 end/close 时 readline 自关);
- *   · `question` 自身 reject(abort throw / 流错误)。 */
 export async function promptYesNoOnTty(prompt, signal, streams = { input: process.stdin, output: process.stderr }) {
     if (signal?.aborted)
         return false;
@@ -263,11 +147,6 @@ export async function promptYesNoOnTty(prompt, signal, streams = { input: proces
         rl.close();
     }
 }
-/**
- * Boot the engine in LOCAL mode, run ONE task to completion, print the result. Returns the process exit
- * code (0 = completed, 1 = the task did not complete / a fatal error, 2 = bad usage / unmet env). Pure of
- * `process.exit` so a test can assert the code; `main()` applies it.
- */
 export async function runLocal(argv, deps = {}) {
     const print = deps.print ?? ((l) => console.log(l));
     const printErr = deps.printErr ?? ((l) => console.error(l));
@@ -282,47 +161,18 @@ export async function runLocal(argv, deps = {}) {
         }
         throw err;
     }
-    // FORCE local posture: a one-shot CLI is a single-machine run. Set the knob BEFORE loadConfig so
-    // (1) createConfigProvider selects the LocalConfigProvider and (2) config.ts defaults the `host` exec lane
-    // (the TOC first-run default for CONFIG_PROVIDER=local with no explicit REMOTE_EXEC). Honor an operator who
-    // already set it to something else (don't override an explicit choice) — but never leave it remote-by-default.
     if (!process.env.CONFIG_PROVIDER)
         process.env.CONFIG_PROVIDER = "local";
-    // FORCE the durable backends OFF: a one-shot, single-machine CLI has nothing durable to persist
-    // and deliberately does NOT assemble the server-only StoreBackend. A shared .env that carries
-    // SESSION_BACKEND set to anything but the enum's "memory"/"mysql"/"auto" would otherwise boot-reject
-    // outright (SESSION_BACKEND is an enum env, validated at load — an old value like the retired public
-    // name "tidb" is rejected, not silently coerced), and even a legit "mysql" value would pull in a
-    // server-only SQL session store this one-shot CLI has no business assembling. Unlike CONFIG_PROVIDER/
-    // REMOTE_EXEC (where an explicit operator choice can be HONORED), a DB session store cannot work here
-    // at all, so we FORCE — never honor — this knob to in-memory so the CLI just works regardless of the
-    // shared config. Long-term memory needs no forcing: the design/138 memory ENGINE is file-based and
-    // default-ON here (single-user; MEMORY_ENGINE=off and MEMORY_ENGINE_DIR pass through loadConfig as-is).
     process.env.SESSION_BACKEND = "memory";
-    // 🔴 REQUIRE_PRINCIPAL is the same shared-config footgun class: run-local IS the single
-    // user at their own terminal — there is no untrusted caller to gate — but a server .env carrying
-    // REQUIRE_PRINCIPAL=true would flip `memoryEngineBackendFor`/`memoryScopeFor` into the multi-tenant
-    // memory-dark branch (plus the host-power gates), silently killing the CLI's long-term memory. FORCE it off.
     process.env.REQUIRE_PRINCIPAL = "false";
-    // --root wins, then the standard local roots (mirrors main.ts's local-root resolution).
     const root = args.root ?? process.env.CONFIG_LOCAL_DIR ?? process.env.AGENT_DATA_DIR ?? join(homedir(), ".ai-agent");
     if (args.root)
-        process.env.CONFIG_LOCAL_DIR = args.root; // so loadConfig's local-dir + the provider agree
+        process.env.CONFIG_LOCAL_DIR = args.root;
     const config = loadConfig();
     const logger = deps.logger ?? createLogger(config.logLevel);
     const metrics = createMetrics();
-    // A-033.3(#256,codex 复审 medium 真修):run-local **也**要装密钥剥除的留痕面。这不是 main.ts 的
-    // 复制粘贴 —— 它恰恰是最该有的那条腿:run-local 是 TOC 本地形,模型可驱动的 shell 跑在**用户自己的
-    // 机器**上、继承的是用户**真实的** env(脑钥/仓库令牌/DB 凭据),而这两条剥除腿(hostExecutionEnvFactory
-    // 的 mergeEnv 与 makeLoadProjectMemory 的 git 子进程)在本入口全都接线了。不装 ⇒ 收集器有了、sink 是空的,
-    // 这条腿保留 A-033.3 要消灭的那个「零披露」原状(而且进程一退,连计数都没了)。
     installSecretEnvScrubRecorder({ logger, metrics });
-    // F10 (codex audit): run-local used to drop the pre-logger config diagnostics on the floor (S20 soft-knob
-    // warnings + [792]④ boot notices) — main.ts drained them, this entrypoint didn't. Shared helper, no drift.
     logConfigDiagnostics(logger);
-    // ── Config source (DUAL-MODE §4): resolve the effective config from the LOCAL FileConfigStore and apply it
-    //    OVER the env defaults (config.d/.env drives models/roles). Unreachable/empty → keep the env-derived
-    //    config (the local root may not exist yet — "fill .env and run" still works off env). ──
     const configProvider = createConfigProvider({
         provider: config.configProvider ?? "local",
         ...(config.configLocalDir ? { localDir: config.configLocalDir } : { localDir: root }),
@@ -331,30 +181,14 @@ export async function runLocal(argv, deps = {}) {
     try {
         const r = await configProvider.fetchEffective(undefined);
         if (r) {
-            // [898] tolerant read(registry-core 0.10.12):catalog 域坏文件不再连坐整包回落 env——坏域按 default
-            // 落+这里 per-domain warn 点名(文件路径在 error 文案里),好域照常生效。gate 域坏仍走下面整包 catch。
             for (const de of r.domainErrors ?? [])
                 logger.warn("config_domain_invalid", { domain: de.domain, error: de.error, note: "domain fell to schema defaults; other domains applied normally" });
             effective = r.effective;
             applyEffective(config, r.effective, logger);
-            // MCP servers (config.d/mcp.json or center) — applied here (NOT inside applyEffective, which only
-            // covers models/roles/gates/teams) so run-local matches the server path (main.ts:446). Restart-to-apply.
             if (effective?.mcp)
                 config.mcpServers = resolveMcpServers(effective.mcp, logger);
-            // DESIGN-269 车1 件1:A2A peers, same line as MCP — applied HERE so run-local matches the server path
-            // (boot/config-center.ts). Restart-to-apply.
-            // ⚠️ 如实记(codex 对抗复审 finding 4,验真后采纳为**文档更正**):今天只有**远端 center** 的
-            // `/effective` 里带 `a2a` 域时这一行才写得进值。**本地 config.d 车道还接不上** —— registry-core
-            // 锁定版的可移植域表里没有 a2a,`config-provider.ts` 的 `mapToServiceEffective` 闭式投影也就没有这
-            // 一域可投。补齐属于 registry-core(上游件),不在本车射程;在那之前别在文档里承诺 config.d/a2a.json。
             if (effective?.a2a)
                 config.a2aPeers = resolveA2aPeers(effective.a2a, logger);
-            // #A4([4147] 件1):READ 容纳面四键的 center 腿 —— 与 server 腿同一只函数、同一条 restart-to-apply
-            // 线(本腿是一次性 CLI,"restart" 即下次运行)。env 显式恒赢的判据在函数内,两腿零分家。
-            // ⚠️ 如实记(与上面 a2a 那条同款诚实句):**本地 config.d 车道今天接不上** —— registry-core 的
-            // 可移植域表里没有 readFace 域,`config-provider.ts` 的 `mapToServiceEffective` 闭式投影也就没有这一
-            // 域可投;这一行今天只在 `CONFIG_PROVIDER=remote` 的 run-local 形上写得进值。补齐属于 registry-core
-            // (上游件),在那之前别在文档里承诺 config.d/read-face.json。
             applyCenterReadFace(config, r.effective, logger);
             logger.info("config_loaded", { source: configProvider.kind, version: r.effective.version });
         }
@@ -362,10 +196,6 @@ export async function runLocal(argv, deps = {}) {
     catch (err) {
         logger.warn("config_source_unreachable_using_env", { source: configProvider.kind, err: String(err) });
     }
-    // ── remoteExec (DUAL-MODE §5): in local mode, honor the SHARED config.d/remote-exec.json via the registry
-    //    loader (the SAME file the client's `agent-cli config` writes). MISSING → keep config.ts's host default;
-    //    PRESENT host → it wins (workdir→workspaceBase); corrupt → fail-closed. Mirrors main.ts's block; the
-    //    isolated lanes (e2b/k8s/ssh/adb) stay env-sourced (a one-shot CLI is the host lane by design). ──
     try {
         const fileRx = await loadRemoteExec(root);
         if (fileRx?.provider === "host") {
@@ -385,10 +215,6 @@ export async function runLocal(argv, deps = {}) {
         printErr(`config.d/remote-exec.json is invalid: ${String(err)}`);
         return 2;
     }
-    // ── design/181 件三 boot 期两件(与 HTTP 腿同一只判据)────────────────────────────────────────
-    // ① 守卫集的**可编译性**门:编译发生在每一次装配上,一条「一个路径段都没有」的模式(`"/"`)会 THROW,
-    //    运维从那条错误里看不出是自己的 env 写错了。共享 .env 的坏值必须炸在启动上——这条腿按 run-local 的
-    //    既定 UX 落地(doctor 文案 + 退 2),而不是把栈抛给用户。
     try {
         assertGuardPatternsUsable(config);
     }
@@ -397,18 +223,12 @@ export async function runLocal(argv, deps = {}) {
         printErr(`(local config root: ${root} — fix it in ${join(root, ".env")} or your shell env; \`SENSITIVE_WRITE_PATTERNS=off\` disables the guard set)`);
         return 2;
     }
-    // ② UNGATED 补偿:接上审批基线后 core 的 `hasEffectAwareGate` 恒真 ⇒ 它那条 "write-capable hand tools
-    //    are present but UNGATED" 的信号在这条腿上结构性消失。判据与文案是**同一只**构造口的
-    //    (buildOnlySensitiveBaselineWarning),两个座位量按本腿的真形取:durable 门恒不在场(一次性 CLI
-    //    没有 /decide 赎回腿),单用户 auto-accept 基线的适用性判据与 main.ts 逐字同源。
     const ungatedCompensation = buildOnlySensitiveBaselineWarning(config, {
         durableEnabled: false,
         singleUserAutoAcceptBaseline: config.requirePrincipal !== true && !hasOperatorGateIntent(config),
     });
     if (ungatedCompensation)
         logger.warn(ungatedCompensation.event, ungatedCompensation.fields);
-    // ── Pre-flight: with a REAL brain, validate the gateway + key and print the doctor-style guidance instead
-    //    of crashing on the first brain call. With an injected mock brain, no real call happens → skip. ──
     if (!deps.brain) {
         const missing = missingGatewayRequirements(config);
         if (missing.length > 0) {
@@ -419,22 +239,11 @@ export async function runLocal(argv, deps = {}) {
             return 2;
         }
     }
-    // ── Minimal runtime assembly (the SAME building blocks as main.ts, server-only bits omitted). ──
     const brain = deps.brain ?? createBrain(config, deps.fetchImpl ? { fetchImpl: deps.fetchImpl } : {});
     const pricing = buildPricing(config.models);
-    // Persistent LOCAL stores (TOC): core's file-backed StorageBackend under the data root → session + long-term
-    // memory + checkpoints SURVIVE across invocations (no DB). flock'd single-instance per data dir; a second
-    // concurrent instance throws in the constructor — surface a clear message instead of a stack.
     let fileBackend;
     try {
         fileBackend = new FileStorageBackend({
-            // 🔴 腐读披露座(codex 复审 R1-medium,#205 件3 连带):本批把 `sessionPolicyStore` 接进了两只
-            // Runner,而 core 对**坏掉的**策略文件是 documented fail-open —— 读不出来按「没有规则」处理。
-            // 这条 fail-open 本身是 core 的裁定(抛会让整条任务死、也会自锁修复写),但它**不许无声**
-            // (#157 安全轴纪律)。一个座覆盖 core 今天转发的三张脸,后果**各不相同**,所以文案只陈述共同事实
-            // (「一次持久读被当成缺席」)并把后果按脸分列,不下统一结论(codex R2-medium:原文案把「少了
-            // 会话规则这一层」写成「整个任务无约束」——那会误导事故定级,而且对另外两张脸根本不成立)。
-            // ENOENT 不触发(那是真缺席)。
             root,
             onCorruptRead: (info) => logger.warn("file_store_corrupt_read", {
                 path: info.path,
@@ -450,47 +259,24 @@ export async function runLocal(argv, deps = {}) {
     }
     catch (e) {
         printErr(`cannot open local data dir ${root}: ${e instanceof Error ? e.message : String(e)}`);
-        // 🔴 core 5.23.0([3372] 件④):这个构造器的第二个拒绝面是 design/183 的 I6 adoption boot 门。
-        // 那一类失败**不能**再补「换一个 --root」这句 —— 换根 = 丢下一个迁移到一半的数据根(与
-        // `plugins/store-backend.ts` 的 local 臂同案同判)。core 的拒绝句已自带出路,上面那行已如实打印。
         if (!(e instanceof AdoptionError)) {
             printErr("(another run-local/engine instance may own it; finish it first, or use a different --root)");
         }
         return 2;
     }
     const sessionStore = fileBackend.sessionStore;
-    const keyResolver = createKeyResolver(config.modelApiKeyEnv, process.env, config.modelApiKeys); // [2006] 后续:三参全链(sealed→env→undefined),与 boot 正形同源——二参形曾让 sealed 模型静默落网关 key
-    // Host exec lane: run on THIS machine, in a FIXED workspace (CC-like) — the cwd by default (or --workspace /
-    // a config.d workdir). The agent's file edits PERSIST there + are user-visible; the dir is the user's OWN and
-    // is NEVER deleted (workspaceDir mode). One env per task; the Runner owns its lifetime.
+    const keyResolver = createKeyResolver(config.modelApiKeyEnv, process.env, config.modelApiKeys);
     const hostRx = config.remoteExec?.provider === "host" ? config.remoteExec : undefined;
     const workspaceDir = args.workspace ?? hostRx?.workspaceBase ?? process.cwd();
     const executionEnvFactory = hostRx
         ? hostExecutionEnvFactory({
             workspaceDir,
-            // systematic-audit (uniformity with main.ts:442 + the worktree-lane gates): gate background-shell by tenancy.
-            // run-local is a single-user CLI (no untrusted caller) so requirePrincipal is ~always false → ON; passing the
-            // gate keeps the policy uniform if a shared .env ever sets REQUIRE_PRINCIPAL, never relying on the `?? true`.
             backgroundShell: config.requirePrincipal !== true,
             ...(hostRx.commandTimeoutMs != null ? { commandTimeoutMs: hostRx.commandTimeoutMs } : {}),
         })
         : undefined;
-    // TOC local LSP (core 1.190): run-local IS the pure-local host lane, so mount core's `NodeLspManager` (local
-    // child_process language servers over stdio, CC `services/lsp` parity) on the host lane. Default ON (degrades
-    // gracefully to grep/read if a server binary is absent); `LSP_HOST_ENABLED=false` opts out (design/158 B4 split
-    // this lane off `LSP_ENABLED`; 🪦 server 3.0.0 起 `LSP_ENABLED=false` 是 fail-loud 墓碑,拒启指路新名,
-    // 不再是可用的 opt-out)。`requirePrincipal !== true`
-    // keeps it uniform with main.ts (a no-op here — run-local is single-user — but never relies on that). Both runners.
     const lspManager = hostRx && config.lspHostEnabled && config.requirePrincipal !== true ? new NodeLspManager({ log: (event, fields) => logger.info(event, fields) }) : undefined;
-    // Long-term memory (design/138 S1): run-local IS the single-user lane, so the file-based memory ENGINE is
-    // default-ON (MEMORY_ENGINE=off opts out). The data root doubles as the engine config-root fallback so a
-    // run-local and the local HTTP service on one box share ONE memory home (MEMORY_ENGINE_DIR overrides).
     const memoryEngine = memoryEngineBackendFor(config, root);
-    // 142-S2.5-W1: TOC 同步 client 腿——run-local 是 file memory 形态本尊(loadConfig 已拒
-    // DB backend 上的 MEMORY_SYNC_*)。run-local 没接 onMemoryHarvestReport 钩子(一次性 CLI:harvest 只在
-    // 任务收尾发生一次,fire-and-forget 轮会被进程退出腰斩),按设计的后备姿势:boot fire-and-forget 一轮
-    // (拉中心增量,失败 warn 不阻断;进程退出腰斩也安全——cursor 保留纪律下轮重收敛)+ 任务结束后 await
-    // 一轮(推本次 harvest 的新记忆;syncOnce 串行链自动排在 boot 轮之后)。
     let memorySync;
     if (config.memorySync && memoryEngine) {
         memorySync = createMemorySyncRunner({
@@ -506,12 +292,7 @@ export async function runLocal(argv, deps = {}) {
     else if (config.memorySync) {
         logger.warn("memory_sync_configured_but_memory_dark", { note: "MEMORY_SYNC_URL is set but the file memory engine is dark (MEMORY_ENGINE=off / remote exec lane) — no sync rounds will run" });
     }
-    // codex-2 F3([985]e run-local 半场):config.d/prompts.json 的 catalog 轴在这条 lane 也要真消费——
-    // 判形(与 server 同一候选门)→ CenterPromptSource(File 形,<root>/prompt-epoch 自管)→ 两 Runner 的
-    // promptSource。坏形/apply 失败=warn + 内置照跑(单进程本地形,无 refresh 重试拍;下次启动再试)。
     const promptEpochDir = join(root, "prompt-epoch");
-    // codex-7:守护工厂与 main.ts 同姿势——File 店构造同步 mkdir,坏 prompt-epoch 路径不得把可选特性
-    // 变成 run-local 启动致命(Memory 兜底=candidate 不跨启动持久;内置照跑)。
     const promptSource = (() => {
         try {
             return new CenterPromptSource({
@@ -526,7 +307,7 @@ export async function runLocal(argv, deps = {}) {
         }
     })();
     try {
-        await promptSource.restore(); // run-local IS the owning local provider — the on-disk candidate is authoritative
+        await promptSource.restore();
         const promptsRaw = effective?.prompts;
         if (promptsRaw !== undefined) {
             const pv = validatePromptsDomain(promptsRaw);
@@ -536,33 +317,23 @@ export async function runLocal(argv, deps = {}) {
                 logger.warn("center_prompts_invalid", { phase: "run-local", error: pv.error, note: "malformed prompts face — built-ins serve" });
         }
         else {
-            // no prompts face on this boot: a persisted candidate whose file was removed must not survive (same
-            // cleared semantics as the server lane) — applyCatalogToSource's current() probe handles the owed disable.
             await applyCatalogToSource(promptSource, undefined, undefined, logger, "run-local");
         }
     }
     catch (e) {
         logger.warn("center_prompts_catalog_restore_failed", { err: String(e), note: "catalog candidate absent — built-ins serve" });
     }
-    // design/181 件三:**onAsk 座**(全文理由见 {@link createLocalApprover})。两只 Runner 同装 —— 委派出去
-    // 的子任务也在同一台机器上动手,少装一只就是「主任务问人、子任务 park 卡死」。
     const onAsk = createLocalApprover({
         isTty: deps.isTty ?? process.stdin.isTTY === true,
         askYesNo: deps.askYesNo ?? promptYesNoOnTty,
         printErr,
     });
-    /** core 的 `RunnerDeps.onError` 座(两只 Runner 共用一只闭包 —— 两处各写一份正是漂移的成因)。 */
     const engineOnError = (err, ctx) => logger.warn("engine_error", {
         phase: ctx.phase,
         sessionId: ctx.sessionId,
         ...(ctx.classification !== undefined ? { classification: ctx.classification } : {}),
         err: String(err),
     });
-    // ⚠️ `createOrgMemoryAdmissionWiring` 有一条 **throw** 路径:`MEMORY_ORG_DIRECTORY_JSON` 形坏时
-    // `parseOrgDirectoryStatic` 启动期炸(config 层按 A4 分层刻意不校验它)。server 那边炸=进程拒启,
-    // 正确;但本腿的既定 UX 是「doctor 文案 + 退 2」(同 assertGuardPatternsUsable / remote-exec-file-invalid
-    // 两处),把栈抛给在终端里敲命令的人是回归。另一条 throw(多租户 org 键 + 无目录源)在本腿**结构上
-    // 不可达**——上面已把 `REQUIRE_PRINCIPAL` 强制成 false。
     let orgMemoryAdmission;
     try {
         orgMemoryAdmission = createOrgMemoryAdmissionWiring({ config, logger, metrics });
@@ -573,50 +344,10 @@ export async function runLocal(argv, deps = {}) {
         await fileBackend.dispose();
         return 2;
     }
-    /**
-     * [3397]①②③ / #205 件3 —— run-local 的两份 Runner deps 走 **server 同一只共享基座**
-     * (`createSharedRunnerDeps`,main.ts:432 的同款展开)。
-     *
-     * 为什么必须收编:这两份 deps 此前各自手写同源键,而漏配**没有任何编译期或运行期信号** —— 复扫亲验
-     * 到三处真漂移:`toolResultStore` 只在主 runner(委派子代的 `ReadToolResult(ref)` 恒空,正是 core
-     * 1.219 修过的那个病在 sub 腿复发)、`config.tiers` **全文件零接线**(而上面的 `applyEffective` 真在
-     * 填它 ⇒ tier 词 / CC 别名在这条腿上解不出来)、`hooks` / `tracer` / `sessionPolicyStore` 两处都没有。
-     * 基座是一份,新增共享键不可能只挂一半。
-     *
-     * ── 逐参裁定(local 车道**真差异**保留,不为收编硬造 stub)───────────────────────────────────
-     *  · `brain` / `pricing` / `promptSource` / `executionEnvFactory` / `lspManager`:本腿真有,直供。
-     *  · `config`(基座据以取 models / roles / **tiers** / usageWindows):本腿真有 —— tiers 正是本件修的漏。
-     *  · `tracer`:`createTracer(metrics)` 真形。配额/舰队/prompt-manifest 四个可选跟踪器是 server 面的
-     *    设施,本腿没有 ⇒ 不传(不是 stub:那几个参数本就可选,缺席即该轴不记账)。
-     *  · `deploymentHooks`:`createPermissionDeniedMeter(metrics)` —— main.ts 在**没有** toolTracer 时的
-     *    同一只值(tool-trace 落库面是 server 侧设施,一次性 CLI 无处落)。
-     *  · `sessionPolicyStore`:`fileBackend.sessionPolicyStore`(core 的 File 形,其文档原话就是「本地部署
-     *    要让会话规则跨重启存活就接这里」)。E6 规则是 subtract-only ⇒ 方向只会更紧;同一个数据根上的
-     *    本地 HTTP 服务写下的规则,这条腿本就该认。
-     *  · `usageWindowStore`:与 `config.usageWindows` **成对**(main.ts 同规:两键同真同假)—— 配了窗才接
-     *    File 账本,没配窗时接一个空账本只会让 core 以为这条腿有治理窗。
-     *  · `toolResultStore`:`fileBackend.toolResultStore`(本件的主修点:现在主/子同源)。
-     *  · `orgMemoryAdmission`:`createOrgMemoryAdmissionWiring(...)` 真形。本腿 `REQUIRE_PRINCIPAL` 被强制
-     *    false(见上),所以那条多租户拒启探测结构上不可达;产物在无 center / 无 `MEMORY_ORG_DIRECTORY_JSON`
-     *    时是「resolver 缺席 + deployment 自证集」——即 `MEMORY_SCOPE=org:x` 的本地用户从此走得通自证通道。
-     *  · `backgroundAgentStore` / `mailboxStore` / `rosterStore`:**undefined** —— core 的 `FileStorageBackend`
-     *    根本不供这三个店(durable 后台子代 / tier-3 懒复活 / 持久名册都是 server+SQL 面的设施)。造个内存
-     *    冒牌货等于让 core 以为「具名子代能跨进程复活」,而一次性 CLI 的进程下一秒就没了。
-     *  · `sharedMemoryStores`:**undefined** —— 供给面只有 SQL 形(`store-backend.ts` 明写:单机造 file 形
-     *    等于给一个人的部署做「团队共享」,能力面会因此说谎)。
-     */
-    // design/170 件B/C/D(#252):三个部署治理座席 —— 本地形与 server 形**同一只装配口**。为什么本地形也要
-    // 有:`COMPLIANCE_PROFILE` / `LOCKED_CONFIG_KEYS` / `RETENTION_MAX_AGE_DAYS` 是从同一份本地 `.env` 读出来
-    // 的,一个写下了档位的用户在 `sema` 与本机 HTTP 服务上必须得到同一个答案(两条腿对同一份配置两套行为
-    // 正是本仓在册的病族)。三键未配 = 三座席缺席 = 本腿逐字零变化。
-    // #270 车2:lane 自持门在本地形也要跑,理由与上一段逐字相同 —— `RETENTION_SWEEP_INTERVAL_SEC>0`
-    // 是从同一份 `.env` 读出来的,而本地形**结构上**没有执行器(file 店三方法不存在,诚实声明 "none")。
-    // 少了这道门,一个写下了那根旋钮的用户会在 `sema` 上得到一台自称有留存治理、其实什么都不删的机器,
-    // 而在 HTTP 形上得到一条拒启 —— 两条腿对同一份配置两套行为,正是本仓在册的病族。
     assertRetentionLaneWirable({
         intervalSec: config.retentionSweep.intervalSec,
         policy: config.retentionPolicy,
-        executor: undefined, // 本地形恒无执行器(见上)
+        executor: undefined,
         stores: [
             { name: "sessionStore", store: sessionStore },
             { name: "checkpointStore", store: fileBackend.checkpointStore },
@@ -636,11 +367,7 @@ export async function runLocal(argv, deps = {}) {
     const sharedRunnerDeps = createSharedRunnerDeps({
         config,
         governanceSeams,
-        logger, // #240②:onNotice 席(共享基座键,本地形同席——结构化通告落同一 logger)
-        // 交接件⑤:commit 尾注署名座进**共享基座** ⇒ 主 runner 与 subRunner 同源。
-        // [931]① clay 拍:run-local = Sema 品牌本地形态,commit 尾注接 Sema 署名(core 1.300 缺省已翻转不署)。
-        // 修前它只写在下面主 runner 的差异键里 ⇒ **委派出去的子代提交不带署名**,而它提交进的是同一个仓、
-        // 代表的是同一个部署。那不是一次有理由的分歧(差异键注释块逐条列了理由,唯独没提它),是漏配。
+        logger,
         hands: { commitCoAuthor: "Sema <noreply@vivi-ai.com>" },
         brain,
         pricing,
@@ -657,87 +384,42 @@ export async function runLocal(argv, deps = {}) {
         usageWindowStore: config.usageWindows ? fileBackend.usageWindowStore : undefined,
         orgMemoryAdmission,
         sharedMemoryStores: undefined,
-        // #324:run-local 无 configCenter runtime = 无中心撤销面 ⇒ 席诚实缺席(pre-338 语义)。
         mcpRevocations: undefined,
     });
     const runnerDeps = {
         ...sharedRunnerDeps,
-        // ── 以下为主 runner 的差异键(不在共享基座;逐个有因)──────────────────────────────────────
-        // (`hands` 已随共享基座展开 —— 交接件⑤;这里手写同名键会 override 展开、把 subRunner 重新甩开。)
         sessionStore,
         ...(memoryEngine ? { memoryBackend: memoryEngine.backend, memoryEngineDir: memoryEngine.root } : {}),
         checkpointStore: fileBackend.checkpointStore,
-        // design/181 件三:core 的降级/配置类告警此前被 `deps.onError?.()` 的可选链整条吞掉(这条腿从不接这
-        // 个座),包括那条 "write-capable hand tools are present but UNGATED"。接上 stderr(logger.warn 走
-        // stderr)后其余告警——compaction / prompt-cache / mcp / memory / hook 的降级——也不再无声。
         onError: engineOnError,
         onAsk,
-        // design/113 C4: run-local IS the single-user host lane (cwd = --workspace ?? process.cwd()) — the CLI path where
-        // CLAUDE.md project-awareness most belongs. Wire it unless explicitly disabled.
         ...(config.projectMemoryEnabled
             ? { loadProjectMemory: makeLoadProjectMemory({ logger }), probeInstructionSources: makeProbeInstructionSources() }
             : {}),
     };
     const runner = new Runner(runnerDeps);
-    // 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 形
-    // (requireExisting)→ host 文件店优先(core 1.350 hostSessionFork 在宿主店 fork,拆店=响亮
-    // resume.session_not_found),普通子任务 → 私有 TTL 店(throwaway 姿势保留)。
-    // #205 件3:与主 runner **同一只**共享基座展开(上面那份 `sharedRunnerDeps`)——此前这里是一行手写
-    // 字面量,`toolResultStore`/`tiers`/`hooks`/`tracer`/`sessionPolicyStore` 全漏,子代 lane 静默降级。
-    // 差异键只剩会话店与两个座位;**checkpointStore 有意不给**(main.ts 的 sub 腿给它是为了子代 durable
-    // park,而本腿的 park 设施结构上不存在:一次性 CLI 没有 `/decide` 赎回腿,gated ask 由 TTY 真人当场答
-    // ——上面 `buildOnlySensitiveBaselineWarning` 传 `durableEnabled: false` 记的就是同一件事实)。
     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/discuss 的最终
-    // roster 仍被并集进全量可写手(server 修了、CLI 静默留病 —— 这条腿的 subRunner 当年就是这么漏配的)。
     const handslessRunner = new Runner(withoutExecutionEnv(runnerDeps));
     const handslessSubRunner = new Runner(withoutExecutionEnv(subRunnerDeps));
-    // Capability layer (loadSkills + buildScenarios + selectScenario) — assembled exactly like main.ts.
     const skills = loadSkills(config.skillsDir);
     const repoClient = config.gitApiBaseUrl ? createRepoClient(config.gitApiKind, config.gitApiBaseUrl, config.gitApiToken) : undefined;
-    // systematic-audit: wire the env-configured WebSearch backend (WEB_SEARCH_PROVIDER) exactly like main.ts, so the
-    // default scenario's WebSearch tool is assembled on the CLI path too (it was silently never built before).
     const webSearchCfg = webSearchConfigFromEnv();
     const webSearch = webSearchCfg ? createWebSearchBackend(webSearchCfg) : undefined;
-    // #318:会话级任务清单车道。run-local 无 SQL 后端 ⇒ 内存臂(进程内 per-session)。一次性 CLI 的
-    // 单进程内本来就只解析一次场景,接它的意义在于**装配面同源**:server 与 run-local 走同一条
-    // `ScenarioDeps.taskListStoreFor` 契约,不让 CLI 腿静默留在「per-call 私店」的修前形上。
-    // `--session` 跨调用续聊的待办清单不跨进程存活(local 形的诚实边界,USAGE 已登记)。
     const taskListLane = createTaskListLane({ logger });
     const scenarioDeps = {
         runner, subRunner, handslessSubRunner, model: "default", skills, repoClient, metrics, logger,
         ...(webSearch ? { webSearch } : {}),
         taskListStoreFor: taskListLane.storeFor,
-        brandIdentity: true, // run-local is always a local/TOC deployment → brand the default scenario as Sema.
+        brandIdentity: true,
     };
     const scenarios = buildScenarios(scenarioDeps);
-    // Center-/config.d-declared scenarios (composition-as-config): overlay over the built-ins, center wins —
-    // mirrors main.ts:453-457 so a config.d/scenarios.json scenario resolves identically in run-local (no drift).
     if (effective?.scenarios) {
         const { overlay } = centerScenarios(scenarioDeps, effective.scenarios.scenarios, Object.keys(scenarios), logger);
         Object.assign(scenarios, overlay);
     }
-    // ── 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. ──
-    // #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 requested = args.scenario ?? config.defaultScenario;
     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
-    // supplies). The server catches this in resolveSpec/prepareSpec and returns a clean 4xx; here we mirror that
-    // with the doctor-style UX (message to stderr + exit 2) instead of letting it bubble to the fatal exit-1 path.
-    // --session REUSES a session (durable multi-turn across invocations, via the file session store); absent →
-    // a fresh uuidv7 (still persisted). --user is the stable memory/identity scope so long-term memory
-    // accumulates per user (default "local" = the single TOC user). The file stores acquire/append lazily.
-    // #318:解析点上提到场景装配**之前** —— 场景工厂现在要 `ScenarioContext.sessionId`(会话级任务
-    // 清单的分区键)。纯移动,取值逐字不变(uuidv7() 无前置依赖)。
     const sessionId = args.session ?? uuidv7();
     let cap;
     try {
@@ -748,7 +430,7 @@ export async function runLocal(argv, deps = {}) {
             printErr(`cannot run scenario "${scenarioName}": ${err.message}`);
             if (scenarioName === "scan")
                 printErr("(the `scan` scenario needs a git API base URL and a repo — run-local cannot supply a repo; use the default scenario)");
-            void lspManager?.dispose(); // symmetry (harmless no-op here — servers spawn lazily during runTask, not yet)
+            void lspManager?.dispose();
             await fileBackend.dispose();
             return 2;
         }
@@ -756,87 +438,49 @@ export async function runLocal(argv, deps = {}) {
     }
     const mention = parseModelMention(args.objective, Object.keys(config.models));
     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 (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)` ——
-    // `TASK_TIMEOUT_SEC="3600s"`(带单位后缀,运维最常见的写法)得 NaN,再被 `|| 0` 折成 0,
-    // 而 0 在这里的语义是**无超时**。运维以为设了一小时上限,实际把超时关掉了,方向恰好相反,
-    // 且启动期零提示。改走 numEnv:非法值当场 fail-loud 并指名键与实际值。
-    // (numEnv 的注释早就预言了这个失败模式,只是它没 export、跨文件够不到,于是这两处手写了。)
     const taskTimeoutSec = Math.max(0, Math.floor(numEnv("TASK_TIMEOUT_SEC", "0")));
     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 同姿势:
-    // 要 CLI flag 时另开件,别在这里半做)。缺席仍是缺席:`a2aForScenario` 恒返回 undefined 而非 []。
     const a2a = a2aForScenario(config.a2aPeers, scenarioName);
-    // A-002.9(#180 governance 缺口的同文件兄弟残余):运营方预算天花板两枚 —— 与 server 主路径
-    // (boot/resolve-spec.ts)**同键同算法**,共用 budget.ts 的 `cappedCeiling`。此腿无 body(见上一段
-    // 的 [854]④ 记账),所以 requested 恒缺席 ⇒ env 天花板在场时**直接成为** spec 值,天花板为 0/未设时
-    // 仍是 undefined(键缺席=无预算,与改前逐字等价)。
-    // ⚠️ 只接这两枚:`degrade`(MODEL_DEGRADE_*)是另一条旋钮线,不在本条案射程内。
     const maxCostUsd = cappedCeiling(undefined, config.maxTaskCostUsd);
     const maxTokens = cappedCeiling(undefined, config.maxTaskTokens);
-    // core 5.8.0:预算族与墙钟同住 limits;三键各自缺席就不写(全缺 ⇒ 整个 limits 键缺席)。
     const limits = {
         ...(timeoutSec !== undefined ? { maxWalltimeMs: timeoutSec * 1000 } : {}),
         ...(maxCostUsd !== undefined ? { maxCostUsd } : {}),
         ...(maxTokens !== undefined ? { maxTokens } : {}),
     };
-    // design/181 件三:自建的 spec 字面量经**同一条**部署治理链(见 {@link applyLocalGovernance})——
-    // 审批基线 + autonomy/commandPolicy/MANUAL_MODE_SHELL_GATE/守卫集,tighten-only,折叠属主仍是 core。
     const spec = applyLocalGovernance({
         objective: mention.cleanedText || args.objective,
         sessionId,
-        // design/129: run-local IS the pure TOC lane → session-scoped background children
-        // (CC Backgrounded semantics; parity with the server's single-user posture).
         backgroundScope: "session",
-        // [1909]⑧(core 5.23.0 `TaskSpec.oneShot`,#205 件1 的**本腿**半场,codex R2-high 抓获):这条腿
-        // 是**定义上**的一次性提交 —— 本文件头注第一句就是「跑完一条任务、打印 TaskResult、退出」,
-        // `runLocal` 返回后 Runner 全被 dispose、进程即散。缺席这个键时,core 会照默认(交互态)给后台
-        // 委派 / run_workflow 发「结束回合,你会被通知」的回执,而这里**没有下一个回合**能接住那条通知 ——
-        // 那正是本键被造出来要消灭的丢结果病族(BGB drilldown case 2)。
-        // 与 HTTP 腿的差别在**来源**而不在语义:那边是调用方表态(缺席不写键),这边是**进程形态的事实**,
-        // 所以无条件为真,不看任何 body/表态(本腿根本收不到客户端表态,同 permissionMode 的 scoped-out 理由)。
         oneShot: true,
-        principal: scope, // stable local memory/identity scope (single-user TOC; --user overrides)
-        // design/138 S1: enable the memory engine for this run (spec.memory is core's per-task activation half of
-        // the deps.memoryBackend switch). Scope = the --user identity (default "local", the single TOC user).
+        principal: scope,
         ...(memoryEngine ? { memory: memorySpecForRequest(scope, undefined) } : {}),
         model: mention.model ?? "default",
         getApiKeyAndHeaders: keyResolver,
         tools: cap.tools,
         skills: cap.skills,
         ...(cap.promptProvider ? { promptProvider: cap.promptProvider } : {}),
-        // [849]→[2400] 场景层定死终验已无生产者(autonomous 退役);OR 折入形保留,与 resolveSpec 同语义。
         ...(cap.finalVerification === true ? { finalVerification: true } : {}),
         ...(mcp ? { mcp } : {}),
         ...(a2a ? { a2a } : {}),
-        // core 5.8.0:timeoutSec 键退役 → maxWalltimeMs(毫秒);taskWallClockSec 仍产秒,换算在上方 limits 合成处。
         ...(Object.keys(limits).length > 0 ? { limits } : {}),
     }, config, workspaceDir);
     logger.info("run_local_start", { scenario: scenarioName, model: spec.model, sessionId, exec: config.remoteExec?.provider ?? "in-process" });
-    // ── Run ONE task to completion (the sync /v1/tasks path: plain runTask, no verify/cascade). ──
     let result;
     let exitCode = 0;
-    // #196:与 HTTP 腿同一条选路 —— 场景声明 hands:"none" 时任务跑无手 Runner(band 不 mount)。
     const taskRunner = pickHandsRunner(cap.hands, { full: runner, handsless: handslessRunner });
     try {
         result = await taskRunner.runTask(spec);
     }
     catch (err) {
         printErr(`task crashed: ${err instanceof Error ? err.message : String(err)}`);
-        // Clean shutdown even on a crash.
         runner.sessions.dispose();
         subRunner.sessions.dispose();
-        void lspManager?.dispose(); // Kill local child-process language servers so a re-run doesn't orphan them
+        void lspManager?.dispose();
         await fileBackend.dispose();
         return 1;
     }
-    // ── Output: --json → the full TaskResult; else the final assistant text (or salvaged/blocked/error info). ──
     if (args.json) {
         print(JSON.stringify(result, null, 2));
     }
@@ -844,7 +488,6 @@ export async function runLocal(argv, deps = {}) {
         print(result.result);
     }
     else {
-        // Non-completed: surface the most useful text we have, then a one-line status footer to stderr.
         const salvage = result.result || result.salvagedOutput || result.blockedReason || "";
         if (salvage)
             print(salvage);
@@ -852,9 +495,6 @@ export async function runLocal(argv, deps = {}) {
     }
     if (result.status !== "completed")
         exitCode = 1;
-    // 142-S2.5-W1: 任务结束后 await 一轮同步(推本次 harvest 的新记忆到中心;串行链自动排在 boot 轮
-    // 之后,绝不并发互踩)。await 保证轮次在进程退出前完成(fire-and-forget 会被 exit 腰斩);失败只
-    // warn——同步是增益面,绝不改变任务本身的退出码。输出已打印完,这里的等待不挡用户看结果。
     if (memorySync) {
         try {
             await memorySync.syncOnce("post-task");
@@ -863,23 +503,16 @@ export async function runLocal(argv, deps = {}) {
             logger.warn("memory_sync_failed", { reason: "post-task", err: String(err) });
         }
     }
-    // ── Clean shutdown: dispose the warm sessions; the host env workspace is rm -rf'd by the Runner on task
-    //    end (executionEnvFactory env → destroy()). No server/pool/reaper to tear down (none were created). ──
     runner.sessions.dispose();
     subRunner.sessions.dispose();
-    void lspManager?.dispose(); // SAME as the crash path — kill local child-process language servers on the
-    // SUCCESS path too. `runLocal` is exported/reusable (tests/embeddings call it directly, no process.exit), so
-    // without this a completed LSP-touching run orphans a fresh set of stdio servers; the leak is per-invocation.
+    void lspManager?.dispose();
     await fileBackend.dispose();
     return exitCode;
 }
-/** Process entrypoint: run, print, exit with the resolved code. */
 async function main() {
     const code = await runLocal(process.argv.slice(2));
     process.exit(code);
 }
-// Only auto-run when invoked as a script (not when imported by the test). Compare REALPATH-resolved paths
-// so symlinked roots (/tmp→/private/tmp) and the tsx loader's file URL still match the entrypoint argv[1].
 function isMainModule() {
     const entry = process.argv[1];
     if (!entry)