@sema-agent/server 6.7.0 → 7.0.0

package/dist/bake-runner/main.js

@@ -15,6 +15,14 @@ import { parseNumOrFailNonNegative } from "../config.js";
 import { shellQuote as shellSafe } from "../plugins/remote-shell.js";
 import { BakeRunner, } from "./runner.js";
 const exec = promisify(execCb);
+// 鲁棒性批5 A3(2026-08-05):claim/ingest/heartbeat 三个 fetch 此前零超时——bake-runner 的整条 loop()
+// 是这台构建宿主机唯一的主循环,一次悬挂的 image-api 连接(网络分区/黑洞 TCP)会让 claim/heartbeat 永久
+// 挂起,直到底层 socket 超时(可能几十分钟),期间既不上报心跳也不能认领新 bake——整机静默停摆。
+// 上界两档:claim/ingest 不在心跳热路径,给 30s 吃满慢网 RTT + 大 body;heartbeat 必须显著小于
+// BAKE_HEARTBEAT_MS 的默认量级(30s)——否则一次超时本身就吃掉一整个心跳周期,取 10s(同
+// fleet-client.ts `FLEET_CLIENT_FETCH_TIMEOUT_MS` 判据的普适形)。
+const BAKE_CLAIM_INGEST_FETCH_TIMEOUT_MS = 30_000;
+const BAKE_HEARTBEAT_FETCH_TIMEOUT_MS = 10_000;
 function loadEnv() {
     const need = (k) => {
         const v = process.env[k];
@@ -55,6 +63,7 @@ function makeApiClient(env, log) {
                 method: "POST",
                 headers: auth,
                 body: JSON.stringify({ runnerId: env.runnerId }),
+                signal: AbortSignal.timeout(BAKE_CLAIM_INGEST_FETCH_TIMEOUT_MS),
             });
             if (res.status === 204)
                 return null; // empty queue — the routine "nothing to do" case, no log line
@@ -93,6 +102,7 @@ function makeApiClient(env, log) {
                 method: "POST",
                 headers: { ...auth, "x-bake-ingest-secret": ingestSecret },
                 body: JSON.stringify(frame),
+                signal: AbortSignal.timeout(BAKE_CLAIM_INGEST_FETCH_TIMEOUT_MS),
             });
             const body = res.ok ? (await res.json().catch(() => ({}))) : {};
             return {
@@ -107,6 +117,7 @@ function makeApiClient(env, log) {
                 method: "POST",
                 headers: { ...auth, "x-bake-ingest-secret": ingestSecret },
                 body: JSON.stringify({ event: "heartbeat" }),
+                signal: AbortSignal.timeout(BAKE_HEARTBEAT_FETCH_TIMEOUT_MS),
             });
             const body = res.ok ? (await res.json().catch(() => ({}))) : {};
             return {

package/dist/boot/leader.d.ts

@@ -23,5 +23,16 @@ export interface LeaderCtx {
     sessionStore: ReturnType<StoreBackend["session"]>;
     checkpointStore: CheckpointStoreFull | undefined;
 }
+/**
+ * 鲁棒性批5 A6(2026-08-05):k8s 腿要求 MinIO 三件套(ENDPOINT/ACCESS_KEY/SECRET_KEY)全在——半开(一件缺)
+ * 就让 `leaderEndpoint` 的三元式落到 undefined,此前**零披露**:运维显式开了 LEADER_ENABLED +
+ * REMOTE_EXEC=k8s,却在日志里既看不到 `leader_endpoint_enabled` 也看不到任何"为什么没启用"的信号——只能
+ * 靠读源码才知道要去检查 MinIO 三件套。
+ *
+ * 纯谓词,抽出独立函数:只吃 leaderEnabled/leaderProvider/hasS3 三个原语 + 直接读 process.env 取缺失的
+ * 具体变量名,不依赖完整 `LeaderCtx`(构造一整套 brain/pricing/sessionStore 只为测一个 warn 分支不值当)。
+ * 返回 null = 不适用该警告(未开启/非 k8s 腿/三件套齐全);非 null = 该报警,携带具体缺的变量名列表。
+ */
+export declare function leaderK8sMinioGap(leaderEnabled: boolean, leaderProvider: string | undefined, hasS3: boolean): string[] | null;
 export declare function createLeaderFace(ctx: LeaderCtx): ReturnType<typeof createLeaderEndpoint> | undefined;
 //# sourceMappingURL=leader.d.ts.map

package/dist/boot/leader.js

@@ -1,5 +1,24 @@
 import { createLeaderEndpoint } from "../leader/endpoint.js";
 import { createLeaderRunner } from "../leader/wire.js";
+/**
+ * 鲁棒性批5 A6(2026-08-05):k8s 腿要求 MinIO 三件套(ENDPOINT/ACCESS_KEY/SECRET_KEY)全在——半开(一件缺)
+ * 就让 `leaderEndpoint` 的三元式落到 undefined,此前**零披露**:运维显式开了 LEADER_ENABLED +
+ * REMOTE_EXEC=k8s,却在日志里既看不到 `leader_endpoint_enabled` 也看不到任何"为什么没启用"的信号——只能
+ * 靠读源码才知道要去检查 MinIO 三件套。
+ *
+ * 纯谓词,抽出独立函数:只吃 leaderEnabled/leaderProvider/hasS3 三个原语 + 直接读 process.env 取缺失的
+ * 具体变量名,不依赖完整 `LeaderCtx`(构造一整套 brain/pricing/sessionStore 只为测一个 warn 分支不值当)。
+ * 返回 null = 不适用该警告(未开启/非 k8s 腿/三件套齐全);非 null = 该报警,携带具体缺的变量名列表。
+ */
+export function leaderK8sMinioGap(leaderEnabled, leaderProvider, hasS3) {
+    if (!(leaderEnabled && leaderProvider === "k8s" && !hasS3))
+        return null;
+    return [
+        !process.env.MINIO_ENDPOINT && "MINIO_ENDPOINT",
+        !process.env.MINIO_ACCESS_KEY && "MINIO_ACCESS_KEY",
+        !process.env.MINIO_SECRET_KEY && "MINIO_SECRET_KEY",
+    ].filter((v) => typeof v === "string");
+}
 export function createLeaderFace(ctx) {
     const { config, logger, brain, pricing, executionEnvFactory, toolResultStore, sessionStore, checkpointStore } = ctx;
     // v2 leader endpoint (design/50 + design/68): wire when LEADER_ENABLED + an isolated remote-exec backend
@@ -19,6 +38,9 @@ export function createLeaderFace(ctx) {
         }
         : {};
     const leaderProvider = config.remoteExec?.provider;
+    const minioGap = leaderK8sMinioGap(config.leaderEnabled, leaderProvider, "s3" in leaderMinio);
+    if (minioGap)
+        logger.warn("leader_k8s_minio_incomplete", { missing: minioGap });
     // DUAL-MODE §5: orchestration is an ENGINE capability, not fleet-only — the TOC `host` lane runs leader fan-out
     // bounded by ONE box (isolation=none, NON-durable: no snapshot, so the durable sub-worker suspend block below is
     // skipped — host workers run to completion in-process-adjacent). e2b/k8s keep their isolated/suspendable posture.

package/dist/boot/org-memory.d.ts

@@ -0,0 +1,36 @@
+/**
+ * design/170 件A(#148 件3③)——org 记忆准入的装配点:把 org-memory-admission 模块接上 core 5.13.0
+ * 的两个 seam(`RunnerDeps.memoryScopeAdmission` / `RunnerDeps.deploymentMemoryScopes`)。
+ *
+ * 目录源三态(单选,授权面不做双源合并):
+ *  · center 在场(configCenter 且非 dryRun)⇒ 远程腿:per-principal caps 响应的 `orgMemory` 段
+ *    (fetchPrincipalCaps 已 schema 读+透传;段键缺席=旧 center 能力握手 ⇒ 目录记 section_absent 瞬时)。
+ *    **独立 fetch,不复用 caps 缓存条目**(C3:org 授权段自带判别联合缓存,两张表的失败域互不干扰
+ *    ——caps 腿的 deny 缓存/304 复用机制一旦共享,org 面的 gen 拒退与退避语义就会被 caps 语义污染)。
+ *    流量记账:每 principal 每 grant TTL(60s)至多多一拍 caps 拉取,有界。
+ *  · 无 center 而 `MEMORY_ORG_DIRECTORY_JSON` 在场 ⇒ 单机腿:operator 自证静态表(此处装载=启动期,
+ *    坏表 parseOrgDirectoryStatic 直接 throw 拒启动——config 层因 A4 分层不校验,见 config.ts 注)。
+ *    两者都在 ⇒ center 胜,env 表忽略 + warn(授权面双源合并=语义地雷,显式拒)。
+ *  · 都缺 ⇒ resolver 缺席:core 对 request-origin org scope 铸 `memory.admission_required`(fail-closed),
+ *    deployment-origin 走 `deploymentMemoryScopes` 自证通道不受影响(单用户零迁移,v4 §0 伤害①)。
+ *
+ * 能力探测(C12,fail-loud):多租户(requirePrincipal)部署的 projects 登记簿里挂了 org 键 ——这些
+ * 键在多租户下按 request-origin 盖章(N2 部署形态维)——而目录源缺席(含 configCenter dryRun 形)
+ * ⇒ 启动报错:该部署的每个 projectId 请求都会在 prepare 期被整拒,「audit 在跑但恒拒」不是可运行
+ * 状态,响亮拒启动比静默全拒服务诚实(clay 三裁 [2687]:直接 BREAKING,不留兼容臂)。
+ */
+import type { RunnerDeps } from "@sema-agent/core";
+import type { ServiceConfig } from "../config.js";
+import type { Logger } from "../observability/logger.js";
+import type { Metrics } from "../observability/metrics.js";
+export interface OrgMemoryAdmissionWiring {
+    memoryScopeAdmission: RunnerDeps["memoryScopeAdmission"];
+    deploymentMemoryScopes: RunnerDeps["deploymentMemoryScopes"];
+}
+/** 依赖收窄到真实消费面(warn/inc 各一手)——接口隔离让测试用真形字面量,零铸形([2704] §1)。 */
+export declare function createOrgMemoryAdmissionWiring(opts: {
+    config: ServiceConfig;
+    logger: Pick<Logger, "warn">;
+    metrics: Pick<Metrics, "inc">;
+}): OrgMemoryAdmissionWiring;
+//# sourceMappingURL=org-memory.d.ts.map

package/dist/boot/org-memory.js

@@ -0,0 +1,76 @@
+import { fetchPrincipalCaps } from "../config-center/http-client.js";
+import { createMemoryScopeAdmission, createOrgMemoryDirectory, parseOrgDirectoryStatic } from "../org-memory-admission.js";
+const ORG_PREFIX = "org:";
+/** 部署自证 org scope 集(core 准入门的 deployment origin 词表):env 钉的 MEMORY_SCOPE(org 形时)
+ *  + **单用户部署**的 projects 登记簿 org 键(N2:requirePrincipal !== true 的部署无租户边界,operator
+ *  登记簿条目归 deployment)。多租户下登记簿 org 键**不入**此集——它们由 resolve-spec 按 request 盖章,
+ *  走目录判决。 */
+function collectDeploymentOrgScopes(config) {
+    const scopes = new Set();
+    if (config.memoryScope !== undefined && config.memoryScope.startsWith(ORG_PREFIX))
+        scopes.add(config.memoryScope);
+    if (config.requirePrincipal !== true) {
+        for (const project of Object.values(config.projects)) {
+            for (const s of project.defaultScopes ?? [])
+                if (s.startsWith(ORG_PREFIX))
+                    scopes.add(s);
+        }
+    }
+    return [...scopes];
+}
+/** 依赖收窄到真实消费面(warn/inc 各一手)——接口隔离让测试用真形字面量,零铸形([2704] §1)。 */
+export function createOrgMemoryAdmissionWiring(opts) {
+    const { config, logger, metrics } = opts;
+    const deploymentMemoryScopes = collectDeploymentOrgScopes(config);
+    const centerLeg = config.configCenter !== undefined && !config.configCenter.dryRun ? config.configCenter : undefined;
+    const staticJson = config.memoryOrgDirectoryJson;
+    if (centerLeg !== undefined && staticJson !== undefined) {
+        logger.warn("org_memory_directory_env_ignored", {
+            reason: "MEMORY_ORG_DIRECTORY_JSON is set but a config-center is wired — the center directory wins; the env table is IGNORED (authorization faces never merge two sources)",
+        });
+    }
+    const directory = centerLeg !== undefined
+        ? createOrgMemoryDirectory({
+            fetchSection: async (principal) => {
+                // etag 恒缺席 ⇒ fetchPrincipalCaps 永不走 304 臂(返回 null 的唯一途径是条件请求),
+                // 这里的 null 防御臂只为类型收口;C8 回声核与 schema 校验都在 fetchPrincipalCaps 内。
+                const r = await fetchPrincipalCaps(centerLeg.baseUrl, centerLeg.token, principal, undefined, fetch, centerLeg.worker);
+                if (r === null)
+                    throw new Error("config-center returned 304 to a non-conditional org-directory fetch");
+                return r.orgMemory;
+            },
+            grantTtlMs: config.memoryOrgGrantTtlMs,
+            unavailableBackoffMs: config.memoryOrgUnavailableBackoffMs,
+        })
+        : staticJson !== undefined
+            ? createOrgMemoryDirectory({
+                staticTable: parseOrgDirectoryStatic(staticJson), // 启动期 fail-loud(坏表拒启动)
+                grantTtlMs: config.memoryOrgGrantTtlMs,
+                unavailableBackoffMs: config.memoryOrgUnavailableBackoffMs,
+            })
+            : undefined;
+    // C12 能力探测:多租户 + 登记簿有 org 用面 + 目录源缺席 ⇒ 拒启动(见文件头注)。
+    if (directory === undefined && config.requirePrincipal === true) {
+        const orgProjects = Object.entries(config.projects)
+            .filter(([, p]) => (p.defaultScopes ?? []).some((s) => s.startsWith(ORG_PREFIX)))
+            .map(([id]) => id);
+        if (orgProjects.length > 0) {
+            throw new Error(`multi-tenant deployment has org: keys in projects[${orgProjects.join(", ")}].defaultScopes but NO org-memory directory source ` +
+                `(config-center absent/dry-run and MEMORY_ORG_DIRECTORY_JSON unset) — every request selecting these projects would be refused at prepare ` +
+                `(memory.admission_required, fail-closed). Wire a config-center or set MEMORY_ORG_DIRECTORY_JSON, or remove the org keys.`);
+        }
+    }
+    const memoryScopeAdmission = directory !== undefined
+        ? createMemoryScopeAdmission(directory, {
+            mode: config.memoryOrgAdmissionMode,
+            // §5 观测:outcome 闭集 metric + 审计日志线(per-principal 归因走日志,principal 不入 metric label)。
+            onOutcome: (outcome, details) => {
+                metrics.inc("memory_admission_total", { outcome });
+                if (outcome !== "ok" || details !== undefined)
+                    logger.warn("memory_admission_outcome", { outcome, ...details });
+            },
+        })
+        : undefined;
+    return { memoryScopeAdmission, deploymentMemoryScopes };
+}
+//# sourceMappingURL=org-memory.js.map

package/dist/boot/resolve-spec.d.ts

@@ -55,6 +55,12 @@ export interface ResolveSpecCtx {
         root: string;
     } | undefined;
     durableEnabled: boolean;
+    /** #152 ([2703] 案二):活体 AskUserQuestion 面(QuestionCoordinator 的判决探针切面)。在场(=
+     *  ASK_QUESTION_ENABLED)时 durable question 门按活流上下文分腿、spec 不再 stamp QUESTION_AWAITS_RESUME
+     *  (否则 spec.onQuestion 恒遮蔽 RunnerDeps.onQuestion 的活人腿);缺席时行为与旧形逐字一致。 */
+    liveQuestionFace: {
+        hasLiveContext(): boolean;
+    } | undefined;
     approvalExemptionStore: ReturnType<StoreBackend["approvalExemption"]> | undefined;
     singleUserAutoAcceptBaseline: boolean;
     checkpointStore: ReturnType<NonNullable<StoreBackend["checkpoint"]>> | undefined;

package/dist/boot/resolve-spec.js

@@ -48,8 +48,27 @@ import { resolveRequestMcp } from "../task-mcp.js";
 import { MAX_SETTINGS_OUTPUT_STYLE_CHARS, acceptAppendSystemPrompt, applyTaskSettings, coercePermissionMode, effectiveThinking, hasConstitutionAnchors, parseTaskSettings, providerDropsAppend, withPermissionMode } from "../task-settings.js";
 import { enableForkFromBody, normalizeRetainSubagentSessions, selfOrchestrationFromBody } from "../task-workflow.js";
 import { redactSecrets } from "../trace/redact.js";
+/** #152([2703] 案二):durable 部署上的 AskUserQuestion 门。活体面(QuestionCoordinator)缺席 ⇒ 原形
+ *  `createDurableQuestionPolicy()`(恒 ask ⇒ 恒 durable park)。在场 ⇒ **判决时**按活流上下文分腿:
+ *  活流腿(bg/SSE,coordinator.runWithContext 包裹,ALS 判)allow——工具执行落到 RunnerDeps.onQuestion
+ *  的 coordinator,问正在 tail 流的活人;无活流腿(sync /v1/tasks、verify/cascade)ask——durable park
+ *  原语义逐字保留(此时执行只会拿到 headless 空答,park 才是把问题送到人面前的那条腿)。
+ *  工具名字面量与 server.ts 的 pre-CAS 守卫同源("AskUserQuestion",core 未根导出常量)。 */
+function durableQuestionPolicy(live) {
+    if (live === undefined)
+        return createDurableQuestionPolicy();
+    return {
+        check(req) {
+            if (req.toolName !== "AskUserQuestion")
+                return { action: "allow" };
+            return live.hasLiveContext()
+                ? { action: "allow" }
+                : { action: "ask", message: "AskUserQuestion: awaiting a human answer (durable)" };
+        },
+    };
+}
 export function createResolveSpec(ctx) {
-    const { config, logger, metrics, localRoot, scenarios, principalCaps, centerRuntimeCapsResolver, getCenterPrompts, getKeyResolver, taskAttachmentStore, perSessionCwd, setSessionCwd, setSessionShellEnv, hookLlm, hookAgent, fleetBus, hookWakeBus, resumeAnchorStore, ownerAware, taskLimitCaps, taskTimeoutSec, selectEnvTool, sendUserFileToolSpec, memoryEngine, durableEnabled, approvalExemptionStore, singleUserAutoAcceptBaseline, checkpointStore, deploymentHooks, imageIndex, perTaskImage, sessionEnvSelection, } = ctx;
+    const { config, logger, metrics, localRoot, scenarios, principalCaps, centerRuntimeCapsResolver, getCenterPrompts, getKeyResolver, taskAttachmentStore, perSessionCwd, setSessionCwd, setSessionShellEnv, hookLlm, hookAgent, fleetBus, hookWakeBus, resumeAnchorStore, ownerAware, taskLimitCaps, taskTimeoutSec, selectEnvTool, sendUserFileToolSpec, memoryEngine, durableEnabled, approvalExemptionStore, singleUserAutoAcceptBaseline, checkpointStore, deploymentHooks, imageIndex, perTaskImage, sessionEnvSelection, liveQuestionFace, } = ctx;
     // Deployment-owned mapping. Tools/prompt/skills come from the selected scenario (assembled once,
     // bound per request); identity/session/policy stay server-side. Never taken from the request body.
     // design/158 A8:从 createHttpServer 实参里提出来(原地占该字面量 1,093 行中的 967 行)——
@@ -677,7 +696,9 @@ export function createResolveSpec(ctx) {
             // (`writeScope:null` — the engine materializes/reads but harvest commits nothing). Per-request (not a
             // stored flag) → no new per-session state; the shell carries the toggle. RESUME re-runs resolveSpec
             // from the persisted body, so a paused run stays paused across resume legs.
-            memory: memoryEngine ? memorySpecForRequest(auth?.memoryScope, body.memoryWrite, s4DefaultScopes) : undefined,
+            // 件A origin 盖章(#148 件3④):部署形态维随 requirePrincipal——多租户下登记簿种子(projectId
+            // 选定)按 request 盖章走 core 准入门,单用户一律 deployment(v4 §1 N2;零 org 键=整键缺席零迁移)。
+            memory: memoryEngine ? memorySpecForRequest(auth?.memoryScope, body.memoryWrite, s4DefaultScopes, { multiTenant: config.requirePrincipal === true }) : undefined,
             // Scenario-provided capabilities (e.g. code-review = repo tools + reviewer subagents + prompt).
             // RFC A2: the SelectEnvironment tool rides after the scenario's tools (spec.tools is ADDITIVE to core's
             // built-in roster — prepare-task mounts first-party tools separately). Only when the image chain is live.
@@ -711,10 +732,11 @@ export function createResolveSpec(ctx) {
             // operator with approval intent but no checkpointStore falls to `undefined` (core's UNGATED warning).
             // Durable ask (TC-5.4, core 1.95): in durable mode an AskUserQuestion call suspends like an F4 gate —
             // the question policy adjudicates it `ask`, the operator answers out-of-band, and the resume carries
-            // the QuestionAnswer (server.ts `body.answer` → onQuestion closure). Suspend side mounts the tool with
-            // QUESTION_AWAITS_RESUME (it must never run pre-suspend; reaching it = wiring bug, typed throw).
+            // the QuestionAnswer (server.ts `body.answer` → onQuestion closure). #152([2703] 案二): the question
+            // policy is LIVE-AWARE when the QuestionCoordinator is wired — a live-stream leg adjudicates `allow`
+            // (the live human answers over the stream) instead of unconditionally parking; see durableQuestionPolicy.
             toolPolicy: durableEnabled
-                ? combinePolicies(createDurableQuestionPolicy(), createDurableAskPolicy({
+                ? combinePolicies(durableQuestionPolicy(liveQuestionFace), createDurableAskPolicy({
                     requireApproval: config.approvalRequire, deny: config.approvalDeny, autoBudget: config.approvalAutoBudget, neverAuto: config.approvalNeverAuto,
                     // The probe key is the CONTINUED session (auth.sessionId — the same id that keys the
                     // durable checkpoint /decide route). A fresh session (no body.sessionId) has no exemptions by
@@ -761,7 +783,11 @@ export function createResolveSpec(ctx) {
                         isCascade: body.cascade === true,
                         scope: encodeCheckpointScope(auth?.principal),
                     })),
-                    onQuestion: QUESTION_AWAITS_RESUME,
+                    // #152([2703] 案二):sentinel 只在活体面缺席时 stamp。core 取 `spec.onQuestion ?? deps.onQuestion`
+                    // (spec 位恒赢),无条件 stamp 会把 ASK_QUESTION_ENABLED 部署的活人腿永久遮蔽成 durable park。
+                    // 活体面在场 ⇒ 键缺席,RunnerDeps.onQuestion 的 coordinator 生效;park 与否由上面的判决门分腿。
+                    // (suspend 侧的「未答 approve」拒绝不靠 sentinel:server.ts decide 路由 pre-CAS 400 守着。)
+                    ...(liveQuestionFace === undefined ? { onQuestion: QUESTION_AWAITS_RESUME } : {}),
                 }
                 : {}),
         };

package/dist/boot/runner-deps.d.ts

@@ -49,6 +49,10 @@ export interface RunnerDepsCtx {
         root: string;
     } | undefined;
     memorySyncRunner: MemorySyncRunner | undefined;
+    /** design/170 件A(#148 件3③):org 记忆准入两 seam 的装配产物(boot/org-memory.ts)。进**共享
+     *  基座**——主/sub 两 Runner 必须同源:委托子代的 prepare 同样跑准入(委托冻结的重判腿),漏挂
+     *  subRunner=子代平面绕过目录判决。 */
+    orgMemoryAdmission: import("./org-memory.js").OrgMemoryAdmissionWiring;
     toolResultStore: ToolResultStoreFull | undefined;
     sessionPolicyStore: ReturnType<StoreBackend["sessionPolicy"]> | undefined;
     runtimeCapsResolver: RunnerDeps["runtimeCapsResolver"];
@@ -68,7 +72,7 @@ export interface RunnerDepsCtx {
 }
 /** design/158 A10 留档发现②:main runner `RunnerDeps` 与 main.ts subRunner 字面量之间此前手工重复
  * 的 ~15 个键,类型标注见 {@link createSharedRunnerDeps} 头注。 */
-export type SharedRunnerDeps = Pick<RunnerDeps, "brain" | "models" | "roles" | "tiers" | "pricing" | "tracer" | "promptSource" | "executionEnvFactory" | "lspManager" | "backgroundAgentStore" | "mailboxStore" | "rosterStore" | "hooks" | "toolResultStore" | "sessionPolicyStore" | "usageWindows" | "usageWindowStore">;
+export type SharedRunnerDeps = Pick<RunnerDeps, "brain" | "models" | "roles" | "tiers" | "pricing" | "tracer" | "promptSource" | "executionEnvFactory" | "lspManager" | "backgroundAgentStore" | "mailboxStore" | "rosterStore" | "hooks" | "toolResultStore" | "sessionPolicyStore" | "usageWindows" | "usageWindowStore" | "memoryScopeAdmission" | "deploymentMemoryScopes">;
 /**
  * design/158 A10 留档发现②(review 2026-07-29,[1543]§三族A 同源修补的延续):main runner 的
  * `RunnerDeps` 字面量(下方 `createRunnerDeps`)与 `main.ts` 里 subRunner 的 `new Runner({...})`
@@ -97,7 +101,7 @@ export type SharedRunnerDeps = Pick<RunnerDeps, "brain" | "models" | "roles" | "
  *    属性,比再抽一层共享基座更强的同源保证),不重复收纳进这里。
  */
 /** 基座真实消费的窄面(Pick)——subRunner 调用点(main.ts)只需凑这 13 个字段,不必造全量 ctx。 */
-export type SharedRunnerDepsCtx = Pick<RunnerDepsCtx, "config" | "brain" | "pricing" | "tracer" | "promptSource" | "executionEnvFactory" | "lspManager" | "backgroundAgentStore" | "mailboxStore" | "rosterStore" | "deploymentHooks" | "toolResultStore" | "sessionPolicyStore" | "usageWindowStore">;
+export type SharedRunnerDepsCtx = Pick<RunnerDepsCtx, "config" | "brain" | "pricing" | "tracer" | "promptSource" | "executionEnvFactory" | "lspManager" | "backgroundAgentStore" | "mailboxStore" | "rosterStore" | "deploymentHooks" | "toolResultStore" | "sessionPolicyStore" | "usageWindowStore" | "orgMemoryAdmission">;
 export declare function createSharedRunnerDeps(ctx: SharedRunnerDepsCtx): SharedRunnerDeps;
 export declare function createRunnerDeps(ctx: RunnerDepsCtx): RunnerDeps;
 //# sourceMappingURL=runner-deps.d.ts.map

package/dist/boot/runner-deps.js

@@ -49,6 +49,12 @@ export function createSharedRunnerDeps(ctx) {
         // E6: operator-tightened session tool rules — core folds them into the ToolPolicy FIRST (subtract-only) for tasks
         // carrying a sessionId (a delegated subagent has none → inherits no rules). Opt-in: undefined ⇒ no rules read.
         sessionPolicyStore: ctx.sessionPolicyStore ? ctx.sessionPolicyStore : undefined,
+        // design/170 件A:org 记忆准入两 seam(core 5.13.0)。共享基座=主/sub 同源(委托子代 prepare 的
+        // 委托冻结重判腿同样过目录);resolver 缺席=core 对 request-origin org 铸 admission_required
+        // fail-closed,deployment 自证集空=键缺席(诚实缺席>空数组——core 按 Set 语义消费,空集与缺席
+        // 同义,但缺席让 deps 字面量不携带死键)。
+        memoryScopeAdmission: ctx.orgMemoryAdmission.memoryScopeAdmission ? ctx.orgMemoryAdmission.memoryScopeAdmission : undefined,
+        deploymentMemoryScopes: ctx.orgMemoryAdmission.deploymentMemoryScopes && ctx.orgMemoryAdmission.deploymentMemoryScopes.length > 0 ? ctx.orgMemoryAdmission.deploymentMemoryScopes : undefined,
         // design/166-T1:治理窗两键**成对**且进共享基座——主/sub/hook 三 runner 全覆盖(漏挂 subRunner=
         // 子代用量不进窗,治理可被 subagent 刷穿;双记不存在:core stats.nested 是旁路侧栏不折入
         // stats.tokens,governance.commit 是 per-任务 delta 制)。store 只在 config.usageWindows 配置时
@@ -203,8 +209,11 @@ export function createRunnerDeps(ctx) {
         // E23: the live-only inbound-elicitation seam. core invokes it only for servers that opted in via
         // McpServerSpec.elicitation (default OFF) AND only when this is wired — both must hold (doubly fail-closed).
         onElicit: elicitation ? elicitation.elicit : undefined,
-        // §4④: the live AskUserQuestion seam. core mounts the tool when onQuestion is present + routes each ask here; the
-        // DURABLE leg's spec.onQuestion (QUESTION_AWAITS_RESUME) OVERRIDES this per-task so a disconnected-human ask suspends.
+        // §4④: the live AskUserQuestion seam. core mounts the tool when onQuestion is present + routes each ask here.
+        // #152([2703] 案二): with the coordinator wired the durable leg NO LONGER stamps spec.onQuestion
+        // (QUESTION_AWAITS_RESUME) — park-vs-live is decided per-leg by resolve-spec's live-aware question policy
+        // (live-stream leg → this coordinator; no-live-context leg → durable park). The sentinel is stamped only
+        // when the coordinator is absent (ASK_QUESTION_ENABLED off).
         onQuestion: question ? question.question : undefined,
         // [816]/[820]②: the live tool-approval seam (core `resolveAsk` — `spec.onAsk ?? deps.onAsk`). ALS-routed like
         // onQuestion: a leg wrapped by the coordinator's runWithContext reaches the human.

package/dist/config-center/http-client.d.ts

@@ -38,6 +38,7 @@ export declare function fetchPrincipalCaps(baseUrl: string, token: string, princ
     scenario?: ScenarioRuling;
     execution?: ExecutionRuling;
     executionDrift?: string;
+    orgMemory?: unknown;
     etag?: string;
 } | null>;
 /** An HTTP error from a config-center fetch that carries the response status so callers can branch on it

package/dist/config-center/http-client.js

@@ -5,7 +5,7 @@
  * facade re-exports every symbol below unchanged).
  */
 import { createHash } from "node:crypto";
-import { readEffectiveWire } from "@sema-agent/registry-core";
+import { readEffectiveWire, PrincipalCapsWire } from "@sema-agent/registry-core";
 import { centerPromptsFromEffective } from "../prompts-domain-validate.js"; // #100 worker 腿 prompts 边界归一(中立叶)
 /** GET the effective config (Bearer + ETag). null = 304 (unchanged). Throws on transport/HTTP error, and on a
  *  payload that is not an effective config at all(非对象 / version 非有限数 / gate 域坏形——[2281] 裁B)。
@@ -94,7 +94,22 @@ export async function fetchPrincipalCaps(baseUrl, token, principal, etag, fetchI
     }
     if (!res.ok)
         throw new Error(`config-center principal-caps HTTP ${res.status}`);
-    const body = (await res.json());
+    // 边界读=schema(clay 宪法 [2704] §2,同源锚=registry-core PrincipalCapsWire):治理面
+    // runtimeCaps/budget 严格+passthrough(值漂移整体拒 ⇒ 本函数 throw ⇒ resolver fail-close,
+    // 「outage 绝不静默 GRANT」同向);[565]/[580] fail-open 面与 orgMemory(C3 失败域隔离)在
+    // schema 里保持宽读,归一/校验仍在下方与目录腿(极性不因 schema 化翻转)。
+    const parsedBody = PrincipalCapsWire.safeParse(await res.json());
+    if (!parsedBody.success) {
+        throw new Error(`config-center principal-caps body failed schema validation: ${parsedBody.error.issues.map((i) => `${i.path.join(".")}: ${i.message}`).join("; ").slice(0, 600)}`);
+    }
+    const body = parsedBody.data;
+    // design/170 件A C8(响应 principal 回声核,串租户防线一行):center 两条 ?principal= 腿的 body 都
+    // 回带 principal——在场且与请求不符 = 中间层/LB 把别人的 caps 视图递了过来,弃用整响应(throw ⇒
+    // caps 腿 fail-close、org 目录腿记 unavailable)。键缺席 = 旧 center 形,按无证据容忍(回声核只拦
+    // 「有回声且对不上」的确定性错递,不把旧形升级成故障)。
+    if (body.principal !== undefined && body.principal !== principal) {
+        throw new Error(`config-center principal-caps response echoes principal ${JSON.stringify(body.principal)} but ${JSON.stringify(principal)} was requested — discarding the whole response (cross-tenant delivery defense)`);
+    }
     return {
         runtimeCaps: body.runtimeCaps ?? null,
         configured: Boolean(body.configured),
@@ -120,28 +135,37 @@ export async function fetchPrincipalCaps(baseUrl, token, principal, etag, fetchI
         // and a drifted `required` into silent non-enforcement. Now: drift ⇒ DROP the whole ruling (fail-open,
         // gate passes) + `executionDrift` so the caller's audit line fires (the resolver routes it to onError).
         ...((() => {
-            const ex = body.execution;
-            if (ex === undefined || ex === null)
+            // [2704] §1:unknown 面的窄化走运行时类型谓词(真检查),不走断言。
+            const isRecord = (v) => v !== null && typeof v === "object" && !Array.isArray(v);
+            const exRaw = body.execution;
+            if (exRaw === undefined || exRaw === null)
                 return {};
-            if (typeof ex.required !== "boolean")
-                return { executionDrift: `execution.required is ${typeof ex.required}, expected boolean — ruling dropped (fail-open)` };
-            if (!Array.isArray(ex.allowedLanes))
-                return { executionDrift: `execution.allowedLanes is ${typeof ex.allowedLanes}, expected string[] — ruling dropped (fail-open)` };
-            const execution = { required: ex.required, allowedLanes: ex.allowedLanes.filter((s) => typeof s === "string") };
+            if (!isRecord(exRaw))
+                return { executionDrift: `execution is ${Array.isArray(exRaw) ? "array" : typeof exRaw}, expected object — ruling dropped (fail-open)` };
+            if (typeof exRaw.required !== "boolean")
+                return { executionDrift: `execution.required is ${typeof exRaw.required}, expected boolean — ruling dropped (fail-open)` };
+            if (!Array.isArray(exRaw.allowedLanes))
+                return { executionDrift: `execution.allowedLanes is ${typeof exRaw.allowedLanes}, expected string[] — ruling dropped (fail-open)` };
+            const execution = { required: exRaw.required, allowedLanes: exRaw.allowedLanes.filter((s) => typeof s === "string") };
             // registry-core 0.10.1-0.10.2:execution.sessionMirror 宽读。observation-only 子面
             // (server 非执法端,见 ExecutionRuling.sessionMirror 注),所以形状漂移只丢**本子面**并走 executionDrift
             // 审计线(resolver 路由到 onError),**绝不**连带丢 lane ruling(那是真执法面,不能被观测子面拖垮)。
             // required 缺省 false = registry-core zod 默认(便利态);engineUrl 必须非空 string。
-            if (ex.sessionMirror !== undefined && ex.sessionMirror !== null) {
-                const sm = ex.sessionMirror;
-                const smOk = typeof sm === "object" && typeof sm.engineUrl === "string" && sm.engineUrl.length > 0 && (sm.required === undefined || typeof sm.required === "boolean");
-                if (smOk)
+            if (exRaw.sessionMirror !== undefined && exRaw.sessionMirror !== null) {
+                const sm = exRaw.sessionMirror;
+                if (isRecord(sm) && typeof sm.engineUrl === "string" && sm.engineUrl.length > 0 && (sm.required === undefined || typeof sm.required === "boolean")) {
                     execution.sessionMirror = { engineUrl: sm.engineUrl, required: sm.required === true };
-                else
+                }
+                else {
                     return { execution, executionDrift: "execution.sessionMirror malformed — mirror observation dropped (fail-open; lane ruling kept)" };
+                }
             }
             return { execution };
         })()),
+        // design/170 件A:org 记忆解析段**原值透传**(键在场保在场、缺席保缺席——缺席=旧 center 能力握手,
+        // org 目录腿据此判 section_absent 瞬时;形状校验是 org-memory-admission 模块用 PrincipalOrgMemoryWire
+        // 的事,本腿保持薄透传不预判)。
+        ...("orgMemory" in body ? { orgMemory: body.orgMemory } : {}),
         etag: res.headers.get("etag") ?? undefined,
     };
 }

package/dist/config-types.d.ts

@@ -205,6 +205,21 @@ export interface ServiceConfigFlat {
         maxPushEntries?: number;
         maxPullEntries?: number;
     };
+    /** design/170 件A(clay 三裁 [2687]):org 记忆准入模式。`enforce`(默认)=判决即结果;`audit`=判决
+     *  照算但纯观察零行为变化(不整拒、不窄化 writeScope,只记 would-deny/would-narrow)——运维诊断位,
+     *  非发布步骤(audit-first 灰度步按裁2 免除)。env `MEMORY_ORG_ADMISSION_MODE`(enumEnv 二值)。 */
+    memoryOrgAdmissionMode: "audit" | "enforce";
+    /** 件A 单机形目录:env `MEMORY_ORG_DIRECTORY_JSON` 原文(`Record<principal, Record<org:scope, {write?}>>`)。
+     *  config 解析期即整段校验(parseOrgDirectoryStatic,fail-loud);此处存**原文**(config=纯数据,
+     *  Map 在装配点重建)。与 config-center 目录腿互斥的裁决在装配点(两者都在=center 腿胜,env 表忽略
+     *  并 warn——授权面不做双源合并)。 */
+    memoryOrgDirectoryJson?: string;
+    /** 件A 目录 granted(含负结果)缓存 TTL(ms)。新任务/新 resume 腿的准入判决滞后上限=此值(「TTL 即
+     *  有界 LKG」);与同仓保护面 grant TTL 对齐默认 60s。env `MEMORY_ORG_GRANT_TTL_MS`(numEnvBounded)。 */
+    memoryOrgGrantTtlMs: number;
+    /** 件A 目录 unavailable 退避窗(ms)——取数失败的退避语义(bound center hammering),不是策略负结果。
+     *  默认 10s。env `MEMORY_ORG_UNAVAILABLE_BACKOFF_MS`(numEnvBounded)。 */
+    memoryOrgUnavailableBackoffMs: number;
     /** design/48 v1b + design/61: opt-in remote execution backend (PEER adapters, chosen by REMOTE_EXEC). Unset
      *  (OA/review deployments) → in-process stub env, zero behavior change. Secrets (apiKey/privateKey) ONLY from env.
      *   - `e2b`  → per-task E2B Firecracker VM (isolated, suspendable). The default code-agent worker.
@@ -893,7 +908,7 @@ export type ServiceModelPlaneConfig = Pick<ServiceConfigFlat, "gatewayBaseUrl" |
  *  就是本组的门状态,故进组;`parseApprovalDomain` 的返回类型相应是 `Omit<…, "directDoorActive">`。 */
 export type ServiceApprovalConfig = Pick<ServiceConfigFlat, "approvalRequire" | "approvalDeny" | "approvalTimeoutSec" | "approvalAutoBudget" | "approvalNeverAuto" | "approvalHmacKeys" | "durableApproval" | "directApprovalDoor" | "directDoorActive" | "resourceSuspend" | "resourceSuspendTtlSec" | "askQuestionEnabled" | "toolApprovalEnabled" | "mcpElicitation" | "sensitiveWritePatterns" | "manualModeShellGate">;
 /** 组:memory(记忆面 + TOC 同步腿)。 */
-export type ServiceMemoryConfig = Pick<ServiceConfigFlat, "memoryEngineEnabled" | "memoryEngineDir" | "memoryEngineRemoteLaneAllowed" | "memoryEngineBackend" | "memoryScope" | "memorySync" | "projectMemoryEnabled" | "syncImportLeaseStaleSec">;
+export type ServiceMemoryConfig = Pick<ServiceConfigFlat, "memoryEngineEnabled" | "memoryEngineDir" | "memoryEngineRemoteLaneAllowed" | "memoryEngineBackend" | "memoryScope" | "memorySync" | "memoryOrgAdmissionMode" | "memoryOrgDirectoryJson" | "memoryOrgGrantTtlMs" | "memoryOrgUnavailableBackoffMs" | "projectMemoryEnabled" | "syncImportLeaseStaleSec">;
 /** 组:auth(鉴权 / 身份 / 治理棒)。`commandPolicy` 只有 sema-registry 腿(无 env 标量形),故 env 解析
  *  函数不产出它,但它与 `autonomy` 是同一根治理棒的两半,归本组。 */
 export type ServiceAuthConfig = Pick<ServiceConfigFlat, "authToken" | "authTokens" | "allowUnauthedWrites" | "corsOrigins" | "principalHeader" | "requirePrincipal" | "autonomy" | "commandPolicy" | "operatorPrincipals" | "principalJwtPubkeys" | "principalJwtIss" | "principalJwtAud" | "principalJwtMaxTtlSec" | "bindHost" | "bindHostSource">;

package/dist/config.js

@@ -491,9 +491,11 @@ function parseStoreDomain(ctx) {
                 user: env("MYSQL_USER"),
                 password: env("MYSQL_PASSWORD", ""),
                 database: env("MYSQL_DATABASE"),
-                connectionLimit: process.env.MYSQL_POOL_SIZE
-                    ? Number(process.env.MYSQL_POOL_SIZE)
-                    : undefined,
+                // 鲁棒性批5 A2(2026-08-05):此前裸 `Number(process.env.MYSQL_POOL_SIZE)` ——一个手滑值(如
+                // "20;drop") → NaN,driver 的 `connectionLimit` 直接拿到 NaN 而不是走池大小默认,行为因驱动
+                // 而异(未必 fail-loud)。optFinitePositiveEnv 与 dbQueryTimeoutMs 同款:非法值回默认(undefined
+                // = driver 默认池大小)+ S20 boot 警告,合法值照常生效。
+                connectionLimit: optFinitePositiveEnv("MYSQL_POOL_SIZE"),
             }
             : undefined,
         pg: needsDb && dbBackend === "pg"
@@ -503,7 +505,8 @@ function parseStoreDomain(ctx) {
                 user: env("PG_USER"),
                 password: env("PG_PASSWORD", ""),
                 database: env("PG_DATABASE"),
-                connectionLimit: process.env.PG_POOL_SIZE ? Number(process.env.PG_POOL_SIZE) : undefined,
+                // 同 MYSQL_POOL_SIZE 族(鲁棒性批5 A2)。
+                connectionLimit: optFinitePositiveEnv("PG_POOL_SIZE"),
             }
             : undefined,
         // S9 deeper fix: per-query DB timeout (see the interface doc). Soft knob — a typo degrades to the default
@@ -984,6 +987,18 @@ function parseMemoryDomain(ctx) {
     // design/158 B4 ② 的 D 家族四枚里,唯一落在 ServiceConfig 上的就是这枚(其余三枚只在使用点懒读,
     // 预登记留在 orchestration 域 —— 顺序与改前一致:本枚的弃用通知仍先于那三枚)。
     const projectMemoryEnabled = boolEnvWithLegacyNegated("PROJECT_MEMORY_ENABLED", "PROJECT_MEMORY_DISABLED", true);
+    // design/170 件A(clay 三裁 [2687]):org 记忆准入四旋钮。模式=enumEnv 二值非布尔(N9),默认
+    // enforce(裁2:audit-first 灰度步免除,audit 降级为运维诊断位);TTL/退避窗=numEnvBounded 启动期
+    // 报错(env-numeric-fail-loud 门,F6:optFinitePositiveEnv 的静默回默认恰是要消灭的形)。单机目录
+    // env 表在这里就整段校验(fail-loud 越早越好——一张半坏的授权表比拒绝启动更危险),config 上只存
+    // 原文(纯数据;Map 在装配点重建)。
+    const memoryOrgAdmissionMode = enumEnv("MEMORY_ORG_ADMISSION_MODE", "enforce", ["audit", "enforce"]);
+    // 原文存 config(纯数据);整段 fail-loud 校验(parseOrgDirectoryStatic)在装配点——它传递值引
+    // security.js(assertPrincipalShape),而 base config 层禁值引 auth 模块(design/158 A4 分层),
+    // 校验不能放这里。装配点仍在启动期,坏表照样拒启动。
+    const memoryOrgDirectoryJson = process.env.MEMORY_ORG_DIRECTORY_JSON || undefined;
+    const memoryOrgGrantTtlMs = numEnvBounded("MEMORY_ORG_GRANT_TTL_MS", "60000", 1000, 3_600_000);
+    const memoryOrgUnavailableBackoffMs = numEnvBounded("MEMORY_ORG_UNAVAILABLE_BACKOFF_MS", "10000", 500, 600_000);
     return {
         memoryEngineEnabled,
         memoryEngineDir: process.env.MEMORY_ENGINE_DIR || undefined,
@@ -997,6 +1012,10 @@ function parseMemoryDomain(ctx) {
         memoryEngineBackend,
         memoryScope, // hoisted above (the 142-S2.5-W1 sync-scope default consumes it)
         ...(memorySync ? { memorySync } : {}),
+        memoryOrgAdmissionMode,
+        ...(memoryOrgDirectoryJson !== undefined ? { memoryOrgDirectoryJson } : {}),
+        memoryOrgGrantTtlMs,
+        memoryOrgUnavailableBackoffMs,
         projectMemoryEnabled, // design/113 C4 opt-out, flipped positive in design/158 B4 (3.0.0 起 legacy PROJECT_MEMORY_DISABLED = fail-loud 墓碑)
         syncImportLeaseStaleSec: Math.max(0, numEnv("SYNC_IMPORT_LEASE_STALE_SEC", "600")),
     };
@@ -1177,7 +1196,12 @@ function parseOrchestrationDomain(ctx) {
                                                         ...(process.env.DOCKER_HOST ? { dockerHost: process.env.DOCKER_HOST } : {}),
                                                         ...(process.env.DOCKER_MEMORY ? { memory: process.env.DOCKER_MEMORY } : {}),
                                                         ...(process.env.DOCKER_CPUS ? { cpus: Number(process.env.DOCKER_CPUS) } : {}),
-                                                        ...(process.env.DOCKER_PIDS_LIMIT ? { pidsLimit: Number(process.env.DOCKER_PIDS_LIMIT) } : {}),
+                                                        // 鲁棒性批5 A1(2026-08-05):此前裸 `Number(process.env.DOCKER_PIDS_LIMIT)`——非数字值(如
+                                                        // 手滑的 "512;") → NaN,而消费端(local-docker 执行环境)对 `pidsLimit` 的守卫是
+                                                        // `?? 512`(只挡 null/undefined),NaN 穿透守卫;随后 `NaN > 0` 恒假,`--pids-limit` 整个
+                                                        // 从 docker run 参数里省略——运维以为设了 fork-bomb 背栓,实际背栓被静默卸掉。
+                                                        // optFinitePositiveEnv:非法值回 undefined(消费端默认 512 生效)+ S20 boot 警告。
+                                                        ...((n) => (n !== undefined ? { pidsLimit: n } : {}))(optFinitePositiveEnv("DOCKER_PIDS_LIMIT")),
                                                         ...(boolEnv("DOCKER_DROP_CAPS", false) ? { dropAllCaps: true } : {}),
                                                         ...(process.env.DOCKER_NETWORK
                                                             ? { network: enumEnv("DOCKER_NETWORK", "bridge", ["none", "bridge", "host"]) }
@@ -1354,7 +1378,8 @@ const APPROVAL_GROUP_KEYS = [
 ];
 const MEMORY_GROUP_KEYS = [
     "memoryEngineEnabled", "memoryEngineDir", "memoryEngineRemoteLaneAllowed", "memoryEngineBackend", "memoryScope",
-    "memorySync", "projectMemoryEnabled", "syncImportLeaseStaleSec",
+    "memorySync", "memoryOrgAdmissionMode", "memoryOrgDirectoryJson", "memoryOrgGrantTtlMs", "memoryOrgUnavailableBackoffMs",
+    "projectMemoryEnabled", "syncImportLeaseStaleSec",
 ];
 const AUTH_GROUP_KEYS = [
     "authToken", "authTokens", "allowUnauthedWrites", "corsOrigins", "principalHeader", "requirePrincipal", "autonomy",

package/dist/fleet/fleet-bus.d.ts

@@ -1,3 +1,12 @@
+import type { TaskNotificationPayload } from "@sema-agent/core";
+/** [2687-cli] 幽灵行案的单源判别:一条 `task_notification` 只有在 **agent 族 × 终态** 时才允许打
+ *  `onChildTerminal`(fleet「subagent 树」只渲 agent 子代)。`background_bash`/`monitor`/`external`
+ *  不属 agent fleet 树——它们此前每条都打,fleet-bus 的「无 tick 无 claim」臂给 b\* 与 m\* handle 合成
+ *  agent 形瞬态终帧,壳终态留存池把这帧渲 60s = footer 幽灵子行;monitor 的 `status:"event"` 还被
+ *  终态映射折成 `failed`。**两侧都正向枚举**(新 task_type/新 status 默认不铸行=安全方向)。
+ *  与 core `isDelegatedAgentTerminal`(task-notification.js,未从包根导出)语义同源——core 根导出后
+ *  换装 import 删本镜像(提货件已上板)。 */
+export declare function isFleetAgentTerminalNotification(n: Pick<TaskNotificationPayload, "task_type" | "status">): boolean;
 /** The fleet vocabulary the shell renders (MF-Fleet `FleetTask.status`). The service maps its run/workflow status
  *  onto this neutral set; `awaiting approval` = a needs-review/plan-approval park, `waiting` = a durable suspend.
  *

package/dist/fleet/fleet-bus.js

@@ -22,6 +22,16 @@
  */
 import { EventEmitter } from "node:events";
 import { redactSecrets } from "../trace/redact.js";
+/** [2687-cli] 幽灵行案的单源判别:一条 `task_notification` 只有在 **agent 族 × 终态** 时才允许打
+ *  `onChildTerminal`(fleet「subagent 树」只渲 agent 子代)。`background_bash`/`monitor`/`external`
+ *  不属 agent fleet 树——它们此前每条都打,fleet-bus 的「无 tick 无 claim」臂给 b\* 与 m\* handle 合成
+ *  agent 形瞬态终帧,壳终态留存池把这帧渲 60s = footer 幽灵子行;monitor 的 `status:"event"` 还被
+ *  终态映射折成 `failed`。**两侧都正向枚举**(新 task_type/新 status 默认不铸行=安全方向)。
+ *  与 core `isDelegatedAgentTerminal`(task-notification.js,未从包根导出)语义同源——core 根导出后
+ *  换装 import 删本镜像(提货件已上板)。 */
+export function isFleetAgentTerminalNotification(n) {
+    return n.task_type === "background_agent" && (n.status === "completed" || n.status === "failed" || n.status === "killed" || n.status === "cancelled");
+}
 /**
  * The process-local fleet aggregation bus. Holds the current active set + fans out deltas to SSE subscribers.
  * Upserts MERGE (a partial delta patches the existing row), so a publisher can emit just the field that changed

package/dist/http/routes/session-sync.js

@@ -420,6 +420,10 @@ async function handleSessionSyncBody(req, res, url, ctx, miss) {
                 }
                 // §4 active-run guard (don't drop a live append) + per-session import lease (don't let two staged imports race
                 // to commit the same session). Both 409.
+                // `runStore?.` 的可选链不是守卫豁免面(鲁棒性批5 #7 亲验定性,2026-08-06):runStore 仅在
+                // **backend 整体缺席**时才 undefined(tidb/pg/local 三形态的 backend.run() 全都在,main.ts:378),
+                // 而 backend 缺席时本路由的 Phase A 已在 `beginImportStaging` 探测处硬 501(capability.session_store_
+                // required)——「守卫被跳过而 sync 仍可达」的组合按构造不存在(能力面与路由解析同真值)。
                 const activeTaskId = await deps.runStore?.getActiveTaskId(sessionId);
                 if (activeTaskId) {
                     sendError(res, 409, "session_active", "session has an active run; sync after it settles", { activeTaskId });