@sema-agent/server 7.6.0 → 7.7.0

package/dist/capabilities/scenarios.js

@@ -7,6 +7,7 @@ import { stablePrompt } from "./prompt.js";
 import { createTeamTool, teamCoordinatorPrompt, getTeam, teamNames } from "./team.js";
 import { createWebSearchBackend, webSearchConfigFromSettings } from "../plugins/web-search.js";
 import { skillsForScenario } from "./skills.js";
+import { pickHandsRunner } from "./hands-lane.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
@@ -88,6 +89,11 @@ export function codePromptProvider(brand) {
 // [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
@@ -137,7 +143,9 @@ export function buildScenarios(deps) {
                     // core 1.382 checkpointStore/ensureChildSessionDurable = design/153 parked 状态机的「同车必接」
                     // 一对([1561] 提货单①②,ScenarioDeps 字段注释详述);两者任一缺席 = 净是 pre-153 行为。
                     subagent: {
-                        runner: deps.subRunner,
+                        // #196:default/code 的委派子代**要**手(CC parity;main.ts subRunner 注里那条 "subagent
+                        // couldn't run pwd" 缺陷就是这条腿缺手),故按本场景判别位取 full 支。
+                        runner: subRunnerFor(deps, "full"),
                         background: {
                             registry: defaultTaskRegistry,
                             owner: "unattributed",
@@ -158,6 +166,9 @@ export function buildScenarios(deps) {
                     ...(webSearch ? { webSearch } : {}),
                 }).filter((t) => t.name !== "WebFetch" || 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.
@@ -190,13 +201,15 @@ export function buildScenarios(deps) {
         // 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) => {
-            if (!deps.repoClient)
-                throw new HttpError(501, "scan scenario needs GIT_API_BASEURL configured");
+            const repoClient = requireRepoClient(deps, "scan");
             if (typeof req.repo !== "string" || !req.repo.trim()) {
                 throw new HttpError(400, "scan scenario requires a 'repo' field (owner/name or repo URL)");
             }
             return {
-                tools: [...repoToolsFor(deps.repoClient, parseRepo(req.repo)), nowTool()],
+                tools: [...repoToolsFor(repoClient, parseRepo(req.repo)), nowTool()],
+                // #196:头注的「工具集即边界」自此在**最终 roster** 上成立(修前 core 把手带 band 并集进来,
+                // clone-free 承诺只存在于这份声明里)。
+                hands: "none",
                 skills: skillsForScenario(deps.skills, "scan"),
             };
         },
@@ -212,8 +225,11 @@ export function buildScenarios(deps) {
             }
             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(deps.subRunner, template, { objective, businessContext })],
+                tools: [createTeamTool(subRunnerFor(deps, hands), template, { objective, businessContext })],
+                hands,
                 skills: skillsForScenario(deps.skills, "team"),
                 promptProvider: teamCoordinatorPrompt,
             };
@@ -224,6 +240,11 @@ export function buildScenarios(deps) {
 export function selectScenario(scenarios, name) {
     return (name && scenarios[name]) || 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 是
  *  fail-loud 语义(缺 GIT_API 配置/principal 即 throw)→ 探针失败落静态表兜底(表↔工厂一致性由测试锁:
  *  测试喂 fake deps 真调工厂对账工具名)。enabled 对内建恒 true(约定②)。 */
@@ -237,7 +258,12 @@ export function builtinScenarioDetails(scenarios, deps) {
         }
     };
     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 });
+    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 {
         code: mk("code", "编码主场景([891] 出厂缺省;CC 编码 persona 蒸馏版,default 全量工具面;终验旋钮独立)", "full-body", probe("code", {}, undefined, ["Now"]), deps.brandIdentity
             ? "Sema 产品身份 + core 编码完全体提示词(CODE_AGENT persona+自治自检;CC 血统对表)"
@@ -250,7 +276,7 @@ export function builtinScenarioDetails(scenarios, deps) {
 }
 /** center 条目详情(有效性判定与 centerScenarios 完全同款:无效条目既不进 overlay 也不进详情——
  *  保证约定①「详情显示的来源=运行实际用的定义」永不错位)。 */
-export function centerScenarioDetails(specs, builtinNames) {
+export function centerScenarioDetails(specs, builtinNames, deps) {
     const out = {};
     for (const spec of specs ?? []) {
         if (spec.enabled === false)
@@ -270,24 +296,62 @@ export function centerScenarioDetails(specs, builtinNames) {
             // 恒空串;字段本身保留(builtin 条目仍有真值,wire 形不变)。
             promptSummary: "",
             enabled: true,
+            // [C132]:center 声明的 repo 型场景与内建的 scan/code-review 受**同一份**判据管辖
+            // ——overlay 不是判据的第二属主。
+            ...availabilityFields(deps, spec.toolset),
         };
     }
     return out;
 }
 const TOOLSETS = {
-    none: { build: () => [nowTool()] },
+    none: { build: () => [nowTool()], hands: "none" },
     "repo-readonly": {
         requiresRepo: true,
+        hands: "none",
         build: (deps, req) => {
-            if (!deps.repoClient)
-                throw new HttpError(501, "this scenario needs GIT_API_BASEURL configured");
+            const repoClient = requireRepoClient(deps, "this");
             if (typeof req.repo !== "string" || !req.repo.trim()) {
                 throw new HttpError(400, "this scenario requires a 'repo' field (owner/name or repo URL)");
             }
-            return [...repoToolsFor(deps.repoClient, parseRepo(req.repo)), nowTool()];
+            return [...repoToolsFor(repoClient, parseRepo(req.repo)), nowTool()];
         },
     },
 };
+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`/`team`)不依赖后端 ⇒ 恒可用。
+ */
+export function scenarioAvailability(deps, toolset) {
+    if (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 一并退役)
 /**
@@ -316,6 +380,7 @@ export function centerScenarios(deps, specs, builtinNames, logger) {
         const name = spec.name;
         overlay[name] = (req) => ({
             tools: toolset.build(deps, req),
+            hands: toolset.hands, // #196:表态随 toolset 走(center 声明面不可自选 hands —— 能力仍是代码定死的)
             skills: skillsForScenario(deps.skills, name),
         });
         if (builtinNames.includes(name))
@@ -324,13 +389,12 @@ export function centerScenarios(deps, specs, builtinNames, logger) {
     return { overlay, shadows };
 }
 function codeReview(deps, req) {
-    if (!deps.repoClient)
-        throw new HttpError(501, "code-review scenario needs GIT_API_BASEURL configured");
+    const repoClient = requireRepoClient(deps, "code-review");
     if (typeof req.repo !== "string" || !req.repo.trim()) {
         throw new HttpError(400, "code-review scenario requires a 'repo' field (owner/name or repo URL)");
     }
     const coords = parseRepo(req.repo);
-    const repoTools = repoToolsFor(deps.repoClient, coords);
+    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
@@ -340,11 +404,14 @@ function codeReview(deps, req) {
     // (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";
     if (req.council === true) {
         const rounds = clampRounds(req.rounds); // finite-guarded (NaN/±Inf → undefined → council default 1)
         return {
             tools: [
-                createCouncilTool(deps.subRunner, repoTools, objective, {
+                createCouncilTool(subRunnerFor(deps, hands), repoTools, objective, {
                     metrics: deps.metrics,
                     logger: deps.logger,
                     debate: req.debate === true, // L1+L2+L3 (peer debate) vs L1+L3
@@ -355,11 +422,12 @@ function codeReview(deps, req) {
                     ...(rounds !== undefined ? { rounds } : {}),
                 }),
             ],
+            hands,
             skills,
             promptProvider: coordinatorPrompt,
         };
     }
-    return { tools: repoTools, skills, promptProvider: directReviewerPrompt };
+    return { tools: repoTools, 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.";

package/dist/fleet/fleet-terminal-window.js

@@ -144,8 +144,10 @@ function evictIfIdle(store, scope, st) {
  */
 /** [3156] 轮2 真红的修:进程内终态行 seed 缓存 —— **写路径顺手喂**(publishFleet 的 terminal 臂),
  *  读侧零库查询零时序竞态。存在理由:durable pull 的查询键是 caller 的 scope,而 fleetWide 连接
- *  (无 auth 部署恒是)的可见性判据放行**全部** scope —— 查询键与可见性判据不同源,引擎铸行的
- *  scope("anon:shell-live")永远不等于 caller 侧的 "default",pull 恒 miss。seed 缓存按「发生过什么」
+ *  (无 auth 部署恒是)的可见性判据放行**全部** scope —— 查询键与可见性判据不同源。行 scope 的值
+ *  = 提交方自报的 principal 经引擎透传("anon:shell-live" 是 cli 壳在本地单用户模式**自发的 header
+ *  值**,引擎只做 scope=principal 赋值,不发明该字面量;[3225] 后续侦察定谳,勿再写「引擎铸」),
+ *  它永远不等于 caller 读侧的 "default",pull 恒 miss。seed 缓存按「发生过什么」
  *  记(与订阅方无关),读侧再过各连接自己的 visW。不是活跃集:bus 的 Map 零触碰,单写者不变量原样。
  *  有界:行数 ≤ MAX_ROWS×2、窗长同 WINDOW_MS,超界丢最旧。 */
 const seededTerminalRows = [];
@@ -174,11 +176,12 @@ function seededRowsInWindow() {
 export async function recentTerminalWorkflowRows(store, scope, pullScope) {
     // [3156]:seed 缓存 = 本进程生命周期内全部终态(含 boot recover 判死)的同源可达径——fleetWide 连接
     // (scope=null,可见性判据放行全 scope)取 seed **全量**,并以 `pullScope`(caller principal,尽力形)
-    // 做 durable pull 兜底:pull 的查询键与引擎铸行 scope 可能不同源(cli 轮2 实测 "default" vs
-    // "anon:shell-live" 恒 miss),中了是增益、中不了还有 seed——两径并集,谁都不当唯一真源。
+    // 做 durable pull 兜底:pull 的查询键与行 scope(提交方自报 principal 的透传值)可能不同源
+    // (cli 轮2 实测 "default" vs 壳自发的 "anon:shell-live" 恒 miss),中了是增益、中不了还有 seed
+    // ——两径并集,谁都不当唯一真源。
     // scoped 连接:seed 按本 scope 滤 + durable pull 本 scope(跨进程兜底)。
-    // [3193] 病理3:seed 侧不再按 caller scope 预滤——那是第二份可见性判据(F1 病族),与引擎铸行
-    // scope("anon:shell-live" vs caller "default")恒 miss。本函数只产**候选集**;可见/擦除由路由的
+    // [3193] 病理3:seed 侧不再按 caller scope 预滤——那是第二份可见性判据(F1 病族),与行 scope
+    // (壳自发 "anon:shell-live" vs caller "default")恒 miss。本函数只产**候选集**;可见/擦除由路由的
     // visW/stripW 同一套判据裁(与快照活行、增量帧同源),窗与 MAX_ROWS 双界仍在。
     const seeded = seededRowsInWindow();
     const effectiveScope = scope ?? pullScope;

package/dist/hooks/hook-runner.js

@@ -1395,6 +1395,17 @@ export function composeHooks(deployment, task) {
     const t = task;
     const out = {};
     if (d.preToolUse || t.preToolUse) {
+        // 🔴 观察标(core 5.20.0 `Hooks.preToolUseObservational`)的传承折:复合体只有在**每一只在场的
+        // `preToolUse` 都声明了纯观察**时才继续声明。方向是 fail-closed 的——
+        //  · 漏传承(该声明没声明)= 退回 5.19.0 行为:多一条链条目,跨副本赎回被响亮拒(吵,但不失守);
+        //  · 错传承(有真裁决者却声明了)= core 把复合体的判词整条**拒绝采纳**,客户端 `settings.hooks`
+        //    的 deny/ask 静默蒸发 —— 这是安全轴上的静默 fail-open,比原缺陷坏得多。
+        // 故判据是「无人反对」而不是「有人赞成」:任一在场面未声明 ⇒ 复合体不声明。
+        // 缺席的槽不算反对票(`d.preToolUse` 不在 = 部署侧没有面可裁决,不影响 task 侧的性质)。
+        const bothObservational = (d.preToolUse === undefined || d.preToolUseObservational === true) &&
+            (t.preToolUse === undefined || t.preToolUseObservational === true);
+        if (bothObservational)
+            out.preToolUseObservational = true;
         out.preToolUse = async (toolName, input, ctx) => {
             let current = input;
             const contexts = [];

package/dist/http/route-ctx.d.ts

@@ -15,7 +15,7 @@
  * 本文件对 server.ts 的引用一律 `import type`(tsc 擦除,非装载边)。
  */
 import type { IncomingMessage, ServerResponse } from "node:http";
-import type { TaskStream, TaskSpec, TaskResult, QuestionAnswer, CheckpointToken, ResumeOutcome } from "@sema-agent/core";
+import type { TaskStream, TaskSpec, TaskResult, QuestionAnswer, CheckpointToken, ResumeOutcome, Runner } from "@sema-agent/core";
 import type { FlatServiceDeps, RequestAuth } from "./server.js";
 import type { TaskRequestBody, DecideBinding } from "./wire-types.js";
 import type { IdempotencyCache } from "./idempotency.js";
@@ -82,6 +82,9 @@ export interface RouteRequestState {
  *  命名后好处不只是过 B4 门:两个消费域现在都能对同一个符号做 `import type` 标注,而不是各自重推断结构。 */
 export interface PreparedTaskSubmission {
     spec: TaskSpec;
+    /** #196:本次提交的执行 Runner —— 场景 hands=none 时是无手孪生(不挂 executionEnvFactory)。
+     *  两个消费域一律用它,不再直接摸 `deps.runner`(那正是「场景表态了、执行点没听」的缝)。 */
+    runner: Runner;
     auth?: RequestAuth;
     verify?: VerifyRoundsSpec;
     cascade?: boolean;
@@ -91,6 +94,9 @@ export interface PreparedTaskSubmission {
 /** B4①(命名化):`driveResumeIntoRunLog` 的入参形(resume 家族共用)——原为 9 成员内联匿名对象。 */
 export interface DriveResumeArgs {
     token: CheckpointToken;
+    /** #196:续跑腿的执行 Runner。resume 会用同一条 resolveSpec 重解析场景,故与首跑选同一只 —— 否则
+     *  一次续跑就把手带 band 重新 mount 回来(收窄只在首跑成立 = 没成立)。 */
+    runner: Runner;
     sessionId: string;
     principal: string | undefined;
     fleetScope: string;

package/dist/http/routes/fleet.js

@@ -48,8 +48,12 @@ async function handleFleetBody(req, res, url, ctx, miss) {
         // #189:终态行窗的 durable 读交给 streamFleet 在**订阅注册之后**做(见那里的缓冲段)——放在这里
         // (开流之前)会让"帧已扇出而本连接尚未订阅"的窗口凭空多出一个读的时长,codex R1-H1 红先复现过。
         // [3156] 轮2 真红修:终态窗的查询键必须与可见性判据**同源**——fleetWide 连接(callerScope=null,
-        // visW 放行全 scope)此前窗却按 caller principal("default")查,而行的 scope 是引擎铸的
-        // ("anon:shell-live")⇒ durable pull 恒 miss。fleetWide ⇒ null(窗走进程内 seed 缓存,全 scope)。
+        // visW 放行全 scope)此前窗却按 caller principal("default")查,而行的 scope 是提交方自报
+        // principal 的透传值(cli 壳本地单用户模式自发 "anon:shell-live";引擎不发明该字面量,[3225]
+        // 后续侦察定谳)⇒ durable pull 恒 miss。fleetWide ⇒ null(窗走进程内 seed 缓存,全 scope)。
+        // 读侧 `?? "default"` 三处与 core 写侧铸链同源(core prepare-task `spec.principal ?? "default"`,
+        // 其 CHANGELOG 成文「Single-tenant spelling is an explicit scope:"default"」)——在 core 撤其
+        // 写侧铸点前,server 单方面撤读侧会把无主部署的 durable pull 面弄瞎,故保持同源不动。
         await streamFleet(req, res, deps.fleetBus, fleetWide ? null : (principal ?? "default"), callerSession || null, observeOnly ? undefined : deps.workflowCompletionInbox, { store: deps.workflowRunStore, scope: fleetWide ? null : (principal ?? "default"), pullScope: principal ?? "default", ready: deps.fleetRecoveryDone });
         return;
     }

package/dist/http/routes/runs.js

@@ -326,7 +326,8 @@ async function handleRunsBody(req, res, url, ctx, miss) {
                 rootTaskId: taskId,
                 ...fleetRunLabels(prepared.spec.objective), // BC-1: name = short objective preview (description = live-activity, set by the publisher onEvent tool_start)
             });
-            void runInBackground(deps.runner, { ...prepared.spec, sessionId }, runStore, taskId, deps.metrics, prepared.auth?.principal, prepared.verify, prepared.cascade ? cascadeConfig(deps.config.cascadeLadder, prepared.spec.limits?.maxCostUsd) : undefined, deps.instrumentDegenerate, deps.planCacheProbe, deps.config.traceThinking, inflightRuns, preemptableRuns, steerableRuns, deps.modelUsage, deps.elicitation, // E23: per-run elicitation context (onElicit routes inbound MCP elicitations to this run's stream)
+            void runInBackground(prepared.runner, // #196:场景 hands 判别位选出的 Runner(hands=none ⇒ 无手孪生)
+            { ...prepared.spec, sessionId }, runStore, taskId, deps.metrics, prepared.auth?.principal, prepared.verify, prepared.cascade ? cascadeConfig(deps.config.cascadeLadder, prepared.spec.limits?.maxCostUsd) : undefined, deps.instrumentDegenerate, deps.planCacheProbe, deps.config.traceThinking, inflightRuns, preemptableRuns, steerableRuns, deps.modelUsage, deps.elicitation, // E23: per-run elicitation context (onElicit routes inbound MCP elicitations to this run's stream)
             gatedPrincipal(req, deps.config) ?? null, // E23: the VERIFIED principal that may answer (same source the respond gate uses — never the spoofable header)
             captureTurnAnchor, // E18: per-turn (message eventId → leaf entryId) anchor capture
             fleetPub, // MF-Fleet: the run-scoped fleet-row publisher (onStart/onEvent/onTerminal across all legs)

package/dist/http/routes/tasks.js

@@ -601,7 +601,7 @@ async function handleTasksBody(req, res, url, ctx, miss) {
                             // (mid-flight ctrl+b) and, as a natural consequence, steer/compact — now reach a mid-turn
                             // INTERACTIVE run too (previously only the bg + resume legs registered). Deregistered in the
                             // outer finally (with the fleet settle), so an early throw can't leak a stale handle.
-                            const liveStream = deps.runner.runTaskStream({ ...prepared.spec, signal: ac.signal }, undefined, fwdInternals);
+                            const liveStream = prepared.runner.runTaskStream({ ...prepared.spec, signal: ac.signal }, undefined, fwdInternals); // #196:场景 hands 判别位选出的 Runner
                             liveStreamRef = liveStream;
                             if (durableTaskId)
                                 steerableRuns.set(durableTaskId, liveStream);
@@ -1283,9 +1283,10 @@ async function handleTasksBody(req, res, url, ctx, miss) {
                     // ── B3 ── 原文此处是一处三层三元,把三条模型驱动腿挤在五行里。三腿具名化后判别顺序
                     // (verify → cascade → plain)、短路语义、传参**逐字不变**;`runWithVerification` 仍是整对象
                     // 直传(快审 F1:cost 顶不在重建中丢失),`runCascade` 仍从操作员梯子 + 本任务预算现算配置。
-                    const verifyLeg = (v) => runWithVerification(deps.runner, specWithSignal, v);
-                    const cascadeLeg = () => runCascade(deps.runner, specWithSignal, cascadeConfig(deps.config.cascadeLadder, prepared.spec.limits?.maxCostUsd));
-                    const plainLeg = () => deps.runner.runTask(specWithSignal);
+                    // #196:三腿一律跑 `prepared.runner`(场景 hands 判别位选出的那只),不再直接摸 deps.runner。
+                    const verifyLeg = (v) => runWithVerification(prepared.runner, specWithSignal, v);
+                    const cascadeLeg = () => runCascade(prepared.runner, specWithSignal, cascadeConfig(deps.config.cascadeLadder, prepared.spec.limits?.maxCostUsd));
+                    const plainLeg = () => prepared.runner.runTask(specWithSignal);
                     result = await withPrincipal(principal, () => prepared.verify ? verifyLeg(prepared.verify) : prepared.cascade ? cascadeLeg() : plainLeg());
                 }
                 finally {

package/dist/http/server.d.ts

@@ -77,6 +77,12 @@ export interface ServiceCoreDeps {
     resolveSpec: (body: TaskRequestBody, req: IncomingMessage | undefined, auth?: RequestAuth, opts?: {
         leg?: "fresh" | "resume";
     }) => TaskSpec | Promise<TaskSpec>;
+    /**
+     * #196 场景 hands lane 选路:按 `resolveSpec` 刚产出的 TaskSpec 取本任务的执行 Runner。
+     * 装配点(main.ts)把「场景判别位 → Runner 对」的映射整只闭包传进来 —— 本层不解释场景,只取用。
+     * 缺席 ⇒ 恒 {@link ServiceDeps.runner}(单 Runner 部署形 = #196 之前的行为,逐字不变;测试桩即此形)。
+     */
+    runnerFor?: (spec: TaskSpec) => Runner;
 }
 /** **durable 持久面**:每个键 present ⇔ 对应路由/能力位在场,absent ⇒ 501(诚实缺席),
  *  绝不静默降级。装配点 = main.ts 的 store backend 开箱段。 */

package/dist/http/server.js

@@ -615,6 +615,11 @@ export function createHttpServer(rawDeps) {
             return;
         sendError(res, 404, "not_found.route", "not found");
     }
+    /** #196:本任务跑哪只 Runner —— 由装配点按场景 hands 判别位裁定(main.ts 的 `runnerFor` 闭包)。
+     *  seam 缺席 = 单 Runner 部署形(#196 之前的行为逐字不变),不是降级臂。 */
+    function runnerFor(spec) {
+        return deps.runnerFor?.(spec) ?? deps.runner;
+    }
     /** Read + validate the body, authorize, and build the spec. Returns null if it already responded. */
     async function prepareSpec(req, res) {
         const body = (await readJson(req));
@@ -1205,7 +1210,10 @@ export function createHttpServer(rawDeps) {
         }
         try {
             const auth = deps.authorize ? await deps.authorize({ req, body }) : undefined;
-            return { spec: await deps.resolveSpec(body, req, auth, { leg: "fresh" }), auth, verify, cascade, jobId: body.jobId, body };
+            const spec = await deps.resolveSpec(body, req, auth, { leg: "fresh" });
+            // #196:执行 Runner 与 spec 同一次解析产出 —— 两个消费域(tasks 同步/流式、runs 异步)拿的都是这一只,
+            // 不各自再问一遍(再问 = 两处判别,正是漂移的成因)。
+            return { spec, runner: runnerFor(spec), auth, verify, cascade, jobId: body.jobId, body };
         }
         catch (err) {
             if (err instanceof HttpError) {
@@ -1413,9 +1421,12 @@ export function createHttpServer(rawDeps) {
         // Typed pre-check: the pending tool must still exist in the rebuilt config; a scenario
         // redeploy that removed it means the approval can no longer be applied — fail clearly, never a 500/silent.
         // The "hand" tools are NOT in spec.tools — core mounts them at the runner from the executionEnvFactory
-        // (core `HAND_TOOL_EFFECTS`, not re-exported from the package root → mirrored here). When this deployment
-        // has remote exec configured the rebuilt task WILL expose them, so union them in; else gating a hand tool
-        // (the common code-agent case) would always 422 on resume. Keep in sync with core's HAND_TOOL_EFFECTS.
+        // (`HAND_TOOL_NAMES` above derives from core's root-exported `HAND_TOOL_EFFECTS`; nothing is mirrored here).
+        // When this deployment has remote exec configured the rebuilt task WILL expose them, so union them in; else
+        // gating a hand tool (the common code-agent case) would always 422 on resume.
+        // #196 旁注:本 union 只看部署有没有 remoteExec,不看本任务的 hands lane —— 对 hands=none 的任务这是
+        // **过近似**(那些工具根本没 mount,也就不可能有它们的 park 行),只影响 422 的 UX 宽严,不放大任何权限;
+        // band 的**完整**名单(含 Monitor/EnterWorktree/… 这些不在 effects 表里的)在 capabilities/hands-lane.ts。
         // [2380] RB-476(5.0.0):Q6 折叠预检退役——满足性匹配按 RAW 名。pre-floor 旧名 checkpoint
         // (`bash`/`run_workflow` 等)在此 422 诚实拒,与 core 自己的 resume.tool_unavailable 同方向
         // ([2364] 令:耐久面响亮牺牲 + P-7 重开,不静默兜)。现役名恒自映射。
@@ -1510,7 +1521,7 @@ export function createHttpServer(rawDeps) {
         // heartbeat, the resumeStream / resumeWithVerification loop, CheckpointError classification, re-suspend vs
         // terminal drive. This HITL /decide path supplies a `policy_ask` outcome; the scheduler preempt path supplies
         // a `resource_limit`/continue one — sharing this prevents the two resume entries from drifting.
-        return driveResumeIntoRunLog({ token, sessionId: cp.sessionId, principal: auth.principal, fleetScope: resumeFleetScope(req, auth), taskConfig, resumeObjective, outcome, verifyRounds, ...(onResumeCommitted ? { onResumeCommitted } : {}) });
+        return driveResumeIntoRunLog({ runner: runnerFor(spec), token, sessionId: cp.sessionId, principal: auth.principal, fleetScope: resumeFleetScope(req, auth), taskConfig, resumeObjective, outcome, verifyRounds, ...(onResumeCommitted ? { onResumeCommitted } : {}) });
     }
     /**
      * The resume-drive machinery SHARED by `resumeCheckpoint` (operator /decide, `policy_ask`) and `resumePreempted`
@@ -1524,7 +1535,8 @@ export function createHttpServer(rawDeps) {
      * (setSuspended, keep the lock) vs a terminal (setTerminal), and returns the HTTP {status, body}.
      */
     async function driveResumeIntoRunLog(args) {
-        const { token, sessionId, principal, fleetScope, taskConfig, resumeObjective, outcome, verifyRounds } = args;
+        // #196:`runner` = 本次续跑的执行 Runner(场景 hands 判别位裁定,与首跑同源;见 DriveResumeArgs 注)。
+        const { runner: legRunner, token, sessionId, principal, fleetScope, taskConfig, resumeObjective, outcome, verifyRounds } = args;
         // ── #151 车3 刀 3b:resume 腿的 `legKey` 真值(设计稿 §3.2′)──────────────────────────────────
         // 一次 park→resume 的 checkpoint token **就是**这条腿的天然身份:同一 token 重投 = 同一条腿(幂等,
         // askId 不变);新 park ⇒ 新 token ⇒ 新腿 ⇒ 新 askId ⇒ **重新征询**(§3.3「resume 只重放未完成兄弟」)。
@@ -1732,7 +1744,7 @@ export function createHttpServer(rawDeps) {
                 if (verifyRounds !== undefined) {
                     // resumeWithVerification runs the SAME pre-CAS guard + atomic CAS as resume() internally, so a lost
                     // CAS rejects with CheckpointError before any work — handled by the catch below, same as the stream path.
-                    const vr = await resumeWithVerification(deps.runner, token, outcome, { ...taskConfig, signal: cancelCtrl.signal, preemptSignal: preemptCtrl.signal }, resumeObjective, verifyRounds); // 快审 F1:整对象直传
+                    const vr = await resumeWithVerification(legRunner, token, outcome, { ...taskConfig, signal: cancelCtrl.signal, preemptSignal: preemptCtrl.signal }, resumeObjective, verifyRounds); // 快审 F1:整对象直传
                     let safe = stripCheckpointToken(vr);
                     // 🔴 A re-suspend on a LATER gate is NOT terminal: core maps it to status:"failed" +
                     // verification.unverifiedReason:"suspended" with the checkpoint token still live. Treat it exactly like
@@ -1828,7 +1840,7 @@ export function createHttpServer(rawDeps) {
                     // (`++seq` is a sync increment — sink-vs-loop appends get unique seqs); only when a durable log exists.
                     // false once this leg settles — notifications after that take the durable-inbox path.
                     resumeLegLive = true;
-                    const stream = await deps.runner.resumeStream(token, outcome, { ...taskConfig, signal: cancelCtrl.signal, preemptSignal: preemptCtrl.signal }, {
+                    const stream = await legRunner.resumeStream(token, outcome, { ...taskConfig, signal: cancelCtrl.signal, preemptSignal: preemptCtrl.signal }, {
                         onForwardEvent: (e) => {
                             fleetPub?.onForwardEvent(e);
                             // S2 live tail(复审 #1:forward sink 有三条腿——resume 腿上 spawn 的 bg 子代同样带
@@ -2256,7 +2268,7 @@ export function createHttpServer(rawDeps) {
         // A resource-suspended task that was submitted with verify:true is re-gated on completion (parity with the
         // HITL path — the flag rides the persisted ctx.body).
         const verifyRounds = verifyRoundsFromBody(ctx.body);
-        return driveResumeIntoRunLog({ token, sessionId: cp.sessionId, principal: auth.principal, fleetScope: resumeFleetScope(req, auth), taskConfig, resumeObjective, outcome: { gate: "resource_limit", decision: "continue" }, verifyRounds });
+        return driveResumeIntoRunLog({ runner: runnerFor(spec), token, sessionId: cp.sessionId, principal: auth.principal, fleetScope: resumeFleetScope(req, auth), taskConfig, resumeObjective, outcome: { gate: "resource_limit", decision: "continue" }, verifyRounds });
     }
     /** design/144 §3:wake 一个 task_done 纯 park——非门决策,解除 park 消费消息续跑。owner 门:非 operator
      *  只能 wake 自己 scope 的 park(404 无 oracle);core 端 gate_pending/nothing_to_deliver 双拒兜底。 */
@@ -2314,6 +2326,7 @@ export function createHttpServer(rawDeps) {
         const spec = await deps.resolveSpec({ ...ctx.body, resumeAt: undefined }, req, auth);
         const { objective: resumeObjective, sessionId: _sessionId, ...taskConfig } = spec;
         return driveResumeIntoRunLog({
+            runner: runnerFor(spec),
             token,
             sessionId: cp.sessionId,
             principal: auth.principal,
@@ -2379,7 +2392,7 @@ export function createHttpServer(rawDeps) {
             ...(editedPlan !== undefined ? { editedPlan } : {}),
             ...(reason ? { reason } : {}),
         };
-        return driveResumeIntoRunLog({ token, sessionId: cp.sessionId, principal: auth.principal, fleetScope: resumeFleetScope(req, auth), taskConfig, resumeObjective, outcome, verifyRounds });
+        return driveResumeIntoRunLog({ runner: runnerFor(spec), token, sessionId: cp.sessionId, principal: auth.principal, fleetScope: resumeFleetScope(req, auth), taskConfig, resumeObjective, outcome, verifyRounds });
     }
     function recordTaskResult(result) {
         deps.metrics?.inc("tasks_total", { status: result.status });

package/dist/main.js

@@ -1,7 +1,7 @@
 import { readFileSync } from "node:fs";
 import { homedir } from "node:os";
 import { join } from "node:path";
-import { Runner, TtlSessionStore, uuidv7, defaultTaskRegistry, createAllowDenyPolicy, workflowsCapability, createWebFetchSummarizer, resolveTaskModel as coreResolveTaskModel, probeSearchBackend, describeStaticWiring } from "@sema-agent/core";
+import { Runner, InMemoryToolResultStore, TtlSessionStore, uuidv7, defaultTaskRegistry, createAllowDenyPolicy, workflowsCapability, createWebFetchSummarizer, resolveTaskModel as coreResolveTaskModel, probeSearchBackend, describeStaticWiring } from "@sema-agent/core";
 import { createSessionTitler } from "./session-titler.js";
 import { posIntEnv } from "./session-watch.js";
 import { selectEnvironmentTool } from "./capabilities/select-environment-tool.js";
@@ -18,6 +18,7 @@ import { assertGateIntentServiceable, hasOperatorGateIntent } from "./approval.j
 import { loadSkills } from "./capabilities/skills.js";
 import { GiteaClient } from "./capabilities/repo-tools.js";
 import { buildScenarios, builtinScenarioDetails } from "./capabilities/scenarios.js";
+import { createHandsLaneRegistry, pickHandsRunner, withoutExecutionEnv } from "./capabilities/hands-lane.js";
 import { createLogger } from "./observability/logger.js";
 import { createToolTracer, createPermissionDeniedMeter } from "./observability/tool-trace.js";
 import { createRegistryJwtVerifier } from "./auth-bridge.js";
@@ -193,16 +194,54 @@ async function main() {
     const { principalCaps, centerRuntimeCapsResolver, runtimeCapsResolver } = createRuntimeCaps({ config, logger });
     // design/170 件A(#148 件3③):org 记忆准入装配(目录源三态选择+C12 能力探测,坏配置在此拒启动)。
     const orgMemoryAdmission = createOrgMemoryAdmissionWiring({ config, logger, metrics });
+    // 🔴 codex 复审(#196 finding-2b):`toolResultStore` 在**无 backend** 形下是 undefined,而 core 的
+    // Runner 构造函数会在缺席时**每只各自私建**一份 `RunnerSharedToolResultStore`(runtask.js
+    // `if (!this.deps.toolResultStore)`)。本部署有多只 Runner(主 / subRunner / hookAgent / #196 的两只无手
+    // 孪生),私建 ⇒ 每只一个独立店 ⇒ A 车道 offload 出去的 `ReadToolResult` 引用在 B 车道解引用不到
+    // (fork 子任务跨 runner 读父的 offload 是既有可达形,#196 的车道分家又多了一条)。这里显式铸**一份**
+    // 共享兜底(参数与 core 私建那只逐字相同:`RunnerSharedToolResultStore` 是 `InMemoryToolResultStore`
+    // 的空子类,cap 64M chars),只喂 Runner 侧。
+    // ⚠️ 刻意**不动** `toolResultStore` 本身:那个键的「present ⇔ durable 后端在场」语义还管着 E21 purge、
+    // reaper 清扫、leader 装配与 /health 的接线自述(改它会让无 backend 的部署自述成 "shared(sql)" = 谎)。
+    const runnerOffloadStore = toolResultStore ?? new InMemoryToolResultStore({ maxTotalChars: 64_000_000 });
     // design/158 A10:RunnerDeps 装配段搬到 src/boot/runner-deps.ts(逐字;runStore 晚绑改取值,见该文件头注)。
     const runnerDeps = createRunnerDeps({
         config, logger, metrics, localRoot, promptSource: configCenter.promptSource, rosterStore, backgroundAgentStore, mailboxStore, usageWindowStore, brain,
         pricing, tracer, outcomeSink, elicitation, question, toolApproval, sessionStore, memoryEngine,
-        memorySyncRunner, toolResultStore, sessionPolicyStore, runtimeCapsResolver, fileSnapshotStore,
+        memorySyncRunner, toolResultStore: runnerOffloadStore, sessionPolicyStore, runtimeCapsResolver, fileSnapshotStore,
         executionEnvFactory, lspManager, fleetBus, deploymentHooks, workflowRunStore, workflowJournalStore,
         workflowAgentRegistry, workflowNotifyGate, workflowCompletionInbox, deliverWorkflowCompletion, orgMemoryAdmission,
         getRunStore: () => runStore,
     });
     const runner = new Runner(runnerDeps);
+    // #196:`runner` 的无手孪生 —— 同 deps 同实例(sessionStore/toolResultStore/checkpointStore… 全共享,
+    // `Runner.sessions` 就是传进去的那只 store,两只 Runner 不会各持一份会话缓存),唯独不挂
+    // `executionEnvFactory`。core 的 `handsEnabled = ownedEnv || deps.executionEnv` 是 **per-Runner** 合同,
+    // 单 runner 服务全场景时结构上无法逐场景兑现 —— 这只孪生就是兑现它的那一半(设计小票 §2a)。
+    // 声明 hands:"none" 的场景(scan / code-review 两腿 / team / center overlay)在 HTTP 执行点被路由到这里。
+    //
+    // 🔴 两条**已知边界**(codex 复审 2026-08-09 两轮提出,逐条亲验 core dist 后如实记账;两条的部署条件
+    //     互不相同 —— 不要把它们并成一句)。
+    //
+    //  ① 会话锁是 **per-Runner** 的(core runtask.js 的 `sessionLocks` Map,每只 Runner 一份)。
+    //     **条件:无 store backend 的部署形**。有 runStore 时同会话并发提交被服务端的 run 认领挡成 409
+    //     (routes/tasks.ts:317 / routes/runs.ts:335 的 `createRun` 认领),两车道并发结构上不可达;无
+    //     backend 的部署没有那道认领,同一 sessionId 上「一条 full + 一条 none」并发就失去了修前由单
+    //     Runner 提供的串行化。同类缺口本就存在(subRunner 经 ForkRoutingSessionStore 也会碰宿主会话),
+    //     本件让它多一条可达路径。补偿:配任一 backend(含 `DB_BACKEND=local`)即恢复认领。
+    //
+    //  ② 升级窗的旧 checkpoint。**条件恰恰相反:必须有 checkpointStore**(= 有 backend + DURABLE_APPROVAL),
+    //     且部署在 REMOTE_EXEC 车道上 —— 修前建立的 hands=none 场景 durable checkpoint 会带 workspaceHandle
+    //     (可挂起 env 的快照形,以及**非**可挂起远端 env 的 `restoreMode:"park_only"` 形,两者都算;审批 park
+    //     与 resource suspend 都会写),续跑时被路由到这只无手 Runner,core 在 **CAS 之前**抛
+    //     `CheckpointError("checkpoint.unsupported_version", "checkpoint has a remote workspaceHandle but no
+    //     RunnerDeps.executionEnvFactory is wired to rebuild the env")`(runtask.js:3704)。
+    //     本仓的分类表把该码归 **TERMINAL**(http/server.ts 的 CheckpointError 分支):run 行被 `setTerminal`
+    //     成 failed 并**释放** task_active,响应 409 携带该 errorCode —— 会话**不会**被占住到 TTL,运维重提该
+    //     任务即可。故这是**响亮的、有界的**升级窗代价,不是静默损坏;但它是行为面的升级注记,发车说明必须写。
+    //     ⚠️ 未覆盖登记:本形需要「真 durable 店 + 带 workspaceHandle 的旧 checkpoint」才能驱动,本批未建格
+    //     (属真双库/迁移测试面)—— 移交主会话裁定是否要做 checkpoint 感知的续跑选路或启动期预检。
+    const handslessRunner = new Runner(withoutExecutionEnv(runnerDeps));
     // codex R10: TRUE ⇒ the Runner just froze a PRIVATE tier-expanded catalog copy (core runtask.js constructor,
     // dist-read) — in-place model-plane mutation no longer reaches it, so refresh-time plane changes must be
     // DEFERRED to restart (see appliedPlaneEff / applyEffective deferModelPlane). Captured HERE, at the same
@@ -321,7 +360,7 @@ async function main() {
     // (子会话住私有 TTL 店,park 前整树拷进 host durable 店——只查不迁的 1.263 形在拆店生产形下恒
     // 否决 park,cli 真机 14ms~2s expired 即此)。
     const subRunnerSessions = new ForkRoutingSessionStore(sessionStore, new TtlSessionStore({ defaultTtlDays: 1 / 24 }));
-    const subRunner = new Runner({
+    const subRunnerDeps = {
         // [1543]§三族A 结构性根治(design/158 冲刺尾件):与主 runnerDeps 重复的 ~15 键统一走
         // createSharedRunnerDeps 展开——「双点挂载」从人工纪律变结构性保证(新共享键漏配其一=不可能,
         // 基座只有一份)。差异键在展开后显式列出,每个都有为何不同的理由(见 boot/runner-deps.ts 头注)。
@@ -337,7 +376,7 @@ async function main() {
             mailboxStore,
             rosterStore,
             deploymentHooks,
-            toolResultStore,
+            toolResultStore: runnerOffloadStore,
             sessionPolicyStore,
             usageWindowStore,
             orgMemoryAdmission,
@@ -359,7 +398,13 @@ async function main() {
         // TaskStop on parked 走 expire CAS 仲裁(1.389 F-1);/decide 可赎回。行为钉 =
         // test/subagent-park-wiring.test.ts(SOURCE PIN + park 全链 + 旧形反向控制)。
         checkpointStore: checkpointStore ? checkpointStore : undefined,
-    });
+    };
+    const subRunner = new Runner(subRunnerDeps);
+    // #196:`subRunner` 的无手孪生(同一份 deps 字面量摘掉 executionEnvFactory —— 差异面只有这一处,
+    // 结构上不可能漂移)。council 的 lens/arbiter、team 的成员/synthesizer 走它:那些子任务的人格声明
+    // 里一件工具都没有,却在修前照拿全量可写手(设计小票 §1 里最意外的一支)。
+    // ⚠️ 与主 subRunner 共享 `subRunnerSessions` 与 `checkpointStore` 同实例 —— park/fork 的行是同一批。
+    const handslessSubRunner = new Runner(withoutExecutionEnv(subRunnerDeps));
     // S6: resolve identity + owned session from the authenticated channel (never the body).
     const authorize = createAuthorizer(config, sessionStore);
     // S1/S2: durable async run registry + replayable event log (TiDB-backed).
@@ -598,7 +643,7 @@ async function main() {
     // design/158 S4:标注 `: ScenarioDeps` —— 无标注的字面量连自己的键名都不校验(打错/多写一个键
     // 只是多一个没人读的属性,编译期无声),这是 1.304 落错家那一族的另一半土壤。
     const scenarioDeps = {
-        runner, subRunner, model: "default", skills, repoClient, requirePrincipal: config.requirePrincipal,
+        runner, subRunner, handslessSubRunner, model: "default", skills, repoClient, requirePrincipal: config.requirePrincipal,
         webSearch: webSearch ? webSearch : undefined, metrics, logger, webFetchSummarize,
         // core 1.364 写半场:与 RunnerDeps.backgroundAgentStore 同实例(组装区注释;半接=静默死特性)。
         backgroundAgentStore: backgroundAgentStore ? backgroundAgentStore : undefined,
@@ -898,8 +943,12 @@ async function main() {
         // 帽只在 watch 面在场时才有意义(缺席时路由 501,读不到它)——保持与原条件段同门,不单独接线。
         sessionEventsMaxConnections: sessionWatchRegistry ? posIntEnv(process.env.SESSION_EVENTS_MAX_CONNS, 256, 100_000) : undefined,
     };
+    // #196:hands lane 登记簿 —— resolveSpec 登记本请求场景的表态,HTTP 执行点凭 spec 取回选 Runner。
+    // 两处**同一实例**(交给 createResolveSpec 与 runnerFor 闭包),配对由这一行结构性保证。
+    const handsLanes = createHandsLaneRegistry();
     // design/158 A10:resolveSpec 段搬到 src/boot/resolve-spec.ts(逐字;两处活引用改取值,见该文件头注)。
     const resolveSpec = createResolveSpec({
+        handsLanes,
         config, logger, metrics, localRoot, scenarios, principalCaps, centerRuntimeCapsResolver,
         getCenterPrompts: () => configCenter.getCenterPrompts(),
         getKeyResolver: () => configCenter.getKeyResolver(),
@@ -910,7 +959,9 @@ async function main() {
         sessionEnvSelection,
         liveQuestionFace: question, // #152:活体问答面在场 ⇒ durable question 门按活流分腿(见 ResolveSpecCtx 注)
     });
-    const server = createHttpServer({ runner, config, resolveSpec, stores, coordinators, seams, observability, governance, deployment, knobs });
+    // #196:执行点选路。resolveSpec 已按场景判别位登记 lane;`full` 恒回主 runner(修前行为逐字不变)。
+    const runnerFor = (spec) => pickHandsRunner(handsLanes.laneOf(spec), { full: runner, handsless: handslessRunner });
+    const server = createHttpServer({ runner, runnerFor, config, resolveSpec, stores, coordinators, seams, observability, governance, deployment, knobs });
     // D-D SLA-timer: wire the server's deny-sweep into the reaper holder declared above (the reaper is defined
     // before the server, so it calls through this late-bound reference).
     runDenySweep = server.denyExpiredApprovals;