@sema-agent/server 7.52.0 → 7.53.0

package/dist/leader/leader.d.ts

@@ -1,8 +1,8 @@
 /**
- * v2 MVP M4 — the leader orchestrator (design/50 §3, V2-MVP-PLAN.md). Composes the proven pieces into one
+ * v2 MVP M4 — the leader orchestrator ([ref] §3, V2-MVP-PLAN.md). Composes the proven pieces into one
  * callable API: Planner → fanOut (M1) → diff-out (M2) → merge(b) (M3) → Coordinator push.
  *
- * Worker-env model (design/68 §8 F2(a)): preferred = FACTORY env (runner-owned lifecycle; durable suspend only
+ * Worker-env model ([ref] §8 F2(a)): preferred = FACTORY env (runner-owned lifecycle; durable suspend only
  * yields a complete ownedEnv on this path) + diff-out via the worker's mandatory SELF-UPLOAD last step
  * (`fetchDiff`, diffup.ts). Compat = the original static env the leader owns: provision up-front, pull each
  * branch's diff OUT of the still-alive env (pullDiff), destroy every env in a `finally`.
@@ -16,7 +16,7 @@ import { type RunnerLike, type WorkerReport } from "./fanout.js";
 import { type ExecStreamLike } from "./diffout.js";
 import { type MergeDeps, type MergeResult } from "./merge.js";
 import { type TaskSpec, type VerifyConfig, type CheckpointToken, type ToolSpec, type RepairTerminal, type OracleTier, type RepairResult } from "@sema-agent/core";
-/** design/74 Slice 6: drive a worker's resource-suspend auto-resume to a terminal (or bound) state. Exported
+/** [ref] Slice 6: drive a worker's resource-suspend auto-resume to a terminal (or bound) state. Exported
  *  for unit tests. Loops `resume(token, slice)` WHILE the result carries a `resource_limit` checkpoint gate —
  *  NOT by status (the verify wrapper may surface a suspend as failed-with-token). Exits on: a terminal result
  *  (completed/failed → no gate), an exhausted budget (core fails the resume fast → no token/gate), a
@@ -44,16 +44,16 @@ export interface ProvisionedWorker {
     branch: string;
     /** base commit of THIS worker's env (drives `git format-patch <baseSha>..<branch>` diff-out). */
     baseSha: string;
-    /** runs the worker agent on this worker's env (static `executionEnv` or a factory — design/68 F2(a)). */
+    /** runs the worker agent on this worker's env (static `executionEnv` or a factory — [ref] F2(a)). */
     runner: RunnerLike;
     /** Static-env mode (M2 compat): pull the worker's branch diff OUT of its (post-task, still-alive) env. */
     diffEnv?: ExecStreamLike;
-    /** Factory-env mode (design/68 F2(a), preferred when set): fetch the diff the worker SELF-UPLOADED as its
+    /** Factory-env mode ([ref] F2(a), preferred when set): fetch the diff the worker SELF-UPLOADED as its
      *  mandatory last task step (presigned MinIO object) — the env is runner-owned and already gone. */
     fetchDiff?: () => Promise<import("./diffout.js").PullDiffResult>;
     /** Static-env mode only: the leader owns + destroys the env. Factory envs omit this — the runner's factory
      *  lifecycle destroys them, and a SUSPENDED worker's paused env is thereby exempt from the leader's reap
-     *  (design/68 row4/C4: destroying a suspended worker's env = expiring its resume token). */
+     *  ([ref] row4/C4: destroying a suspended worker's env = expiring its resume token). */
     destroy?: () => Promise<void>;
     spec: Omit<TaskSpec, "sessionId" | "signal">;
     /** Optional read-effect PROBE tools for the L3 verifier (verifyWorker path). The default verifierTools = the
@@ -71,7 +71,7 @@ export interface LeaderDeps {
     push: MergeDeps["push"];
     /** Integration test command (the merge gate) + repo dir inside the sandbox. */
     testCmd: string;
-    /** Optional truecorrect MEASURE (design/59): a thorough hidden-oracle command run IN the integration sandbox
+    /** Optional truecorrect MEASURE ([ref]): a thorough hidden-oracle command run IN the integration sandbox
      *  after the gate passes (NOT a gate) — offloads the measure from the control plane. Result in result.merge.measure. */
     measureCmd?: string;
     repoDir?: string;
@@ -80,7 +80,7 @@ export interface LeaderDeps {
     /** fan-out deadline + concurrency cap. */
     timeoutMs: number;
     maxConcurrency: number;
-    /** design/52 L3a — optional per-module sub-gate + bounded repair, run AFTER fan-out, BEFORE merge. For each
+    /** [ref] L3a — optional per-module sub-gate + bounded repair, run AFTER fan-out, BEFORE merge. For each
      *  completed worker: judge its module (diff) vs its sub-objective; on fail, re-run that ONE worker with the
      *  judge's feedback (bounded by maxRepairs, default 1) on its own still-alive env, then re-judge. A module that
      *  still fails is marked `failed` (merge quarantines it). Catches per-module escapes the end-integration test
@@ -93,12 +93,12 @@ export interface LeaderDeps {
         repairObjective: (sub: SubtaskSpec, reason: string) => string;
         maxRepairs?: number;
     };
-    /** core 1.72 native L3a (design/54 §4): when set, each worker runs via `runWithVerification` (run the module +
+    /** core 1.72 native L3a ([ref] §4): when set, each worker runs via `runWithVerification` (run the module +
      *  an INDEPENDENT DECORRELATED verifier tries to break it reading the diff/workspace + a bounded fix-loop)
      *  instead of plain fan-out. The worker runner's `models` catalog MUST carry the heterogeneous `verifierModel`
      *  (decorrelation = deployment contract). Mutually exclusive with `moduleGate` (this IS the native version). */
     verifyWorker?: VerifyConfig;
-    /** Replan-lite (design/68 §6): bounded, DETERMINISTIC reactions — no runtime DAG surgery. When set:
+    /** Replan-lite ([ref] §6): bounded, DETERMINISTIC reactions — no runtime DAG surgery. When set:
      *  worker failed → redispatch ×1 on a FRESH env (clean base; a crashed worker's half-written workspace is
      *  never reused) → still failed = collapse-remainder-to-single; verify FAIL (repair already bounded inside
      *  the verify loop) → collapse; structural merge conflict → collapse + record; budgetUsd exceeded → stop
@@ -151,7 +151,7 @@ export interface LeaderResult {
     route?: "single" | "fanout";
     /** Set when planning/provisioning failed before fan-out. */
     error?: string;
-    /** Replan-lite (design/68 §6): which trigger won arbitration + what was done. */
+    /** Replan-lite ([ref] §6): which trigger won arbitration + what was done. */
     replan?: {
         trigger: "suspended" | "budget" | "merge-conflict" | "verify-fail" | "worker-failed";
         redispatched?: string[];
@@ -163,7 +163,7 @@ export interface LeaderResult {
         workerId: string;
         sessionId: string;
     }>;
-    /** design/74 Slice 6 / task#16: the diff (uncommitted work auto-committed by the belt, then diff-out) of
+    /** [ref] Slice 6 / task#16: the diff (uncommitted work auto-committed by the belt, then diff-out) of
      *  workers that did NOT merge (failed / still-suspended). Their progress is otherwise lost — the merge only
      *  integrates COMPLETED workers — so surface it here for review/cherry-pick instead of silently dropping it
      *  (the migration-run loss: a network-failed worker's 4 commits vanished). Best-effort + non-empty only. */

package/dist/leader/merge.d.ts

@@ -1,5 +1,5 @@
 /**
- * v2 MVP M3 — merge(b), the hard bone (design/50 §7, V2-MVP-PLAN.md, search [25]/[26], council round-1).
+ * v2 MVP M3 — merge(b), the hard bone ([ref] §7, V2-MVP-PLAN.md, search [25]/[26], council round-1).
  *
  * The deterministic Coordinator integrates N completed workers' branches under FULL isolation:
  *   1. pull each worker's patch OUT of its container (M2 `pullDiff` — no creds go in).
@@ -65,7 +65,7 @@ export interface IntegrationRepair {
  * then VERIFIES no marker/.rej remains before continuing, and the downstream test gate still guards correctness.
  * Wired by the caller (provisionIntegrationSandbox); when unset, an apply conflict stays terminal exactly as before
  * (zero behaviour change). Reuses the IntegrationRepair sandbox + hands pattern → no new core/env seam (the seam
- * design/68 §8 feared for "adopting N half-done workspaces" is unnecessary for the conflict case).
+ * [ref] §8 feared for "adopting N half-done workspaces" is unnecessary for the conflict case).
  */
 export interface ConflictResolver {
     /** Max resolution attempts before giving up (each = one agent run + one marker/.rej re-check). */
@@ -112,7 +112,7 @@ export interface MergeDeps {
     repoDir?: string;
     /** Full test command run in the sandbox (the merge gate). */
     testCmd: string;
-    /** Optional truecorrect MEASURE (design/59): a thorough hidden-oracle command run IN the integration sandbox
+    /** Optional truecorrect MEASURE ([ref]): a thorough hidden-oracle command run IN the integration sandbox
      *  (E2B) right after the gate passes — offloads the measure from the CPU-contended control plane (the
      *  frontier-multi oracle-timeout fix). NOT a gate (does not affect `ok`); the result lands in MergeResult.measure
      *  for the caller to read as the objective truly-correct signal. Same place + env as the gate, just a thornier test. */

package/dist/leader/planner.d.ts

@@ -1,5 +1,5 @@
 /**
- * v2 MVP — LLM Planner (design/50 §3: leader = LLM-planner that splits a DAG + deterministic Coordinator).
+ * v2 MVP — LLM Planner ([ref] §3: leader = LLM-planner that splits a DAG + deterministic Coordinator).
  * Decomposes an objective into N **disjoint-file** sub-tasks via one model completion, then VALIDATES the plan
  * deterministically (the trust boundary: an LLM proposes, the Coordinator enforces — service[19] leaderless-
  * leader). Disjoint file-ownership is the invariant that lets workers run in parallel + merge without conflict.
@@ -14,17 +14,17 @@ export interface PlanOptions {
     maxSubtasks?: number;
     /** Extra repo/context guidance appended to the prompt (e.g. file layout, conventions). */
     context?: string;
-    /** Deployment knob (design/68 §11 A6, correctness-first): `false` = never fan out — `routePlan` skips the
+    /** Deployment knob ([ref] §11 A6, correctness-first): `false` = never fan out — `routePlan` skips the
      *  router model call entirely and returns the deterministic single route (zero routing cost, zero risk of a
      *  false fan-out). Default (undefined/true) = the router decides. */
     fanoutEnabled?: boolean;
-    /** Economic guard threshold (design/68 §7, search[83] ruling): an objective SHORTER than this never reaches
+    /** Economic guard threshold ([ref] §7, search[83] ruling): an objective SHORTER than this never reaches
      *  the router — deterministic single (a small task can't be economically decomposable; false-single is the
      *  cheap error side). Default 64 — deliberately below the route corpus's smallest fan-out case. */
     minFanoutChars?: number;
 }
 /**
- * Deterministic economic 防灾 guard (design/68 §7 / §11 D2, search [83] ruling (b)): the asymmetry is that a
+ * Deterministic economic 防灾 guard ([ref] §7 / §11 D2, search [83] ruling (b)): the asymmetry is that a
  * false fan-out is the -98% disaster while a false single merely runs slower — so every case decidable WITHOUT
  * the model resolves to single, for free. Pure function (unit-testable); the semantic judgments (sequential/
  * coupled/uncertain) stay with the router LLM, and "估不准回 single" is the collapse fallback (B3).
@@ -65,7 +65,7 @@ export declare function routePrompt(objective: string, opts?: PlanOptions): stri
  *  validated by `parsePlan` (the same disjointness/shape invariants the Coordinator depends on). */
 export declare function routePlan(objective: string, runRoute: (prompt: string) => Promise<string>, opts?: PlanOptions): Promise<SubtaskSpec[]>;
 /**
- * Decomposer quality gate (design/68 §5/§11 B1-B3): run the router, and on a rejected/unparseable plan retry
+ * Decomposer quality gate ([ref] §5/§11 B1-B3): run the router, and on a rejected/unparseable plan retry
  * the LLM AT MOST ONCE, then COLLAPSE TO SINGLE (never fail the task on a bad plan — single is almost always
  * the right fallback, and a false fan-out is the -98% disaster; a plan failure must not be louder than that).
  * `collapsed` carries the reason (observability: a collapse is a router-quality signal, not silent).

package/dist/leader/repair-oracle.d.ts

@@ -1,6 +1,6 @@
 /**
  * The PROFILE-injected `RepairOracle` closure for the leader's single-agent self-repair loop
- * (`runRepairLoop`, core design/78 / D1). See `sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` (§3.1 + the authoritative
+ * (`runRepairLoop`, core [ref] / D1). See `sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` (§3.1 + the authoritative
  * §10 corrected layer). The closure GRADES a worker's candidate in an ISOLATED grader env (the reused
  * integration sandbox, distinct from the worker env) and maps the result to a core `OracleResult`. core only
  * fixes the `OracleResult` shape + the read-only/identity contract; the composition lives HERE so the core type

package/dist/leader/wire.d.ts

@@ -5,11 +5,11 @@ import type { LeaderRequestBody } from "./endpoint.js";
 export interface LeaderWireConfig {
     /** Static-env compat mode (E2B only): the leader provisions/owns each env. Required when `envFactory` unset. */
     e2bApiKey?: string;
-    /** design/68 F2(a) + k8s lane: the per-task execution-env factory the service main already built for
+    /** [ref] F2(a) + k8s lane: the per-task execution-env factory the service main already built for
      *  REMOTE_EXEC (e2b or k8s/Kata) — workers and the integration sandbox run on envs from THIS factory.
      *  Requires `s3` (diff-out is the worker's self-upload; there is no leader-held env to pull from). */
     envFactory?: ExecutionEnvFactory;
-    /** Durable suspend/resume for SUB-WORKERS (design/68 C4): when set, each worker task carries the durable
+    /** Durable suspend/resume for SUB-WORKERS ([ref] C4): when set, each worker task carries the durable
      *  question/ask policy + checkpoint store, so a gated ask/AskUserQuestion SUSPENDS the worker (checkpoint +
      *  paused env) instead of failing — the trigger replan-lite C4 arbitrates on. Mirrors main.ts's per-task
      *  durable wiring; ctx is seeded at provision so the surfaced token is resumable on the single-agent path. */
@@ -31,7 +31,7 @@ export interface LeaderWireConfig {
      *  the resume dies with SessionError "Entry <leafId> not found" (found live: drill c3 deny path). */
     sessionStore?: SessionStore;
     /**
-     * design/170 件B/C/D(#252,codex R2-F1)—— 部署治理三座席,**原样递给本车道的每一只 Runner**。
+     * [ref] 件B/C/D([ref],codex R2-F1)—— 部署治理三座席,**原样递给本车道的每一只 Runner**。
      * 主车道的 `boot/governance-seams.ts` 是唯一属主(判据、拒启、解析全在那里),本字段只是把它的产物
      * 搬过来:一个进程里「这台部署禁哪些能力、锁了哪些键」只能有一个答案。缺席 = 与接线前逐字相同。
      */
@@ -48,7 +48,7 @@ export interface LeaderWireConfig {
         name: string;
         email: string;
     };
-    /** design/68 A6 knob: false = router never fans out (deterministic single route, zero router cost). */
+    /** [ref] A6 knob: false = router never fans out (deterministic single route, zero router cost). */
     fanoutEnabled?: boolean;
     /** The model (a catalog name) the ROUTER/planner call runs on. The route is a trivial single-vs-fanout
      *  classification; running it on a heavy reasoning model (deepseek-v4-pro + reasoning) returns an EMPTY
@@ -65,7 +65,7 @@ export interface LeaderWireConfig {
      *  Env override: LEADER_CONFLICT_ROUNDS. Resolves the conflict in-place + keeps the other workers' work, instead
      *  of discarding all fan-out output and redoing single. Runs the strong (default) model with hands in the sandbox. */
     conflictRounds?: number;
-    /** design/68 §8 F2(a): when set, workers run on FACTORY envs (runner-owned lifecycle — the durable-suspend-
+    /** [ref] §8 F2(a): when set, workers run on FACTORY envs (runner-owned lifecycle — the durable-suspend-
      *  complete path; a suspended worker's paused env is exempt from the leader reap by construction) and diff-out
      *  is the worker's mandatory self-upload to this MinIO/S3 store (presigned per worker; creds adapter-held).
      *  Unset = the original leader-owned static-env mode (pullDiff compat). */
@@ -85,11 +85,11 @@ export interface LeaderWireConfig {
 /** The env surface wire needs (both the E2B and k8s adapters implement core's RemoteExecutionEnv). */
 type WireEnv = Pick<RemoteExecutionEnv, "exec" | "writeFile">;
 /**
- * Resume-safe worker staging (the design/68 F2(a) factory-env path). Runs adapter-side before the agent's
+ * Resume-safe worker staging (the [ref] F2(a) factory-env path). Runs adapter-side before the agent's
  * first workspace-touching call: seed the base repo at the worker branch + plant the upload script (so the
  * presigned URL never passes through the model).
  *
- * 🔴 BL-1 fix (design/74 Slice 6): on a RESOURCE-SUSPEND RESUME core re-invokes the `executionEnvFactory`,
+ * 🔴 BL-1 fix ([ref] Slice 6): on a RESOURCE-SUSPEND RESUME core re-invokes the `executionEnvFactory`,
  * producing a FRESH `withStaging` wrapper (`staged=undefined`) whose `stage()` runs AGAIN — AFTER core's
  * `resumeVM()` has already untar'd the snapshot onto the fresh pod (`resumeVM` is not a STAGED_METHOD, so it
  * is NOT intercepted by the staging proxy; the agent's first `exec` is what triggers `stage()`, lazily, and
@@ -134,7 +134,7 @@ export declare function leaderResourceConfig(env?: NodeJS.ProcessEnv): {
     workerBudgetUsd: number;
     workerLimits: Partial<TaskSpec>;
     presignTtlSec: number;
-    /** design/74 Slice 6: opt-in (LEADER_RESOURCE_SUSPEND=true) resource-slice suspend for workers. When set, a
+    /** [ref] Slice 6: opt-in (LEADER_RESOURCE_SUSPEND=true) resource-slice suspend for workers. When set, a
      *  worker SUSPENDS at the per-slice window (`sliceMaxCostUsd`) instead of failing at the budget, and the
      *  leader auto-resumes (resumeWithVerification) until the TOTAL (`totalBudgetUsd` = workerBudgetUsd) is spent
      *  — a budget overrun becomes a resumable pause, not a worker failure. ⚠️ 语义更新(core 5.11.0 B3,
@@ -160,7 +160,7 @@ export interface LeaderLoopConfig {
     measureGatesOn: boolean;
     repairLoopAttempts: number;
     oracleFlakyK: number;
-    /** replan-lite (design/68 §6) fan-out spend cap from LEADER_BUDGET_USD. Absent = replan-lite's own default
+    /** replan-lite ([ref] §6) fan-out spend cap from LEADER_BUDGET_USD. Absent = replan-lite's own default
      *  (unset env stays absent — existing contract untouched; see leaderLoopConfig doc below). */
     replanBudgetUsd?: number;
 }

package/dist/lsp/manager.d.ts

@@ -68,7 +68,7 @@ export interface E2bLspManagerOptions {
 }
 /**
  * §DESIGN-V2 F1/F8/F9 —— 本文件曾**手抄**一份 core 的 `settleOnAbort`(注释自陈 core「un-exported」,并写下
- * 「一旦 core 导出即 find-and-delete」的计划)。A-033.1(#256)执行了那句话:core 现已从包根导出它
+ * 「一旦 core 导出即 find-and-delete」的计划)。[ref]([ref])执行了那句话:core 现已从包根导出它
  * (`index.d.ts:27`,来自 `core/lsp.js`),手抄件遂删除,本文件的两处调用直接消费 core 的实现。
  *
  * 它的语义(读点在 `open` 的两处调用):给**这一个**调用方一个自己的 settle —— 调用方的 `signal` 让它拿到
@@ -86,7 +86,7 @@ export declare class E2bLspManager implements LspServerManager {
     private readonly log;
     private readonly hasServerCommand;
     private readonly metrics;
-    /** design/121 (core 1.220, board [S] ①): the workspace diagnostics registry — WORKSPACE-scoped (survives
+    /** [ref] (core 1.220, board [S] ①): the workspace diagnostics registry — WORKSPACE-scoped (survives
      *  heal/evict; diagnostics belong to files, not servers), drained by the Runner at turn boundaries. Every
      *  session feeds it from `textDocument/publishDiagnostics` (the WS transport now dispatches notifications).
      *  ⚠️ ONE registry across sandboxes on this manager instance (it is per-deployment) — same posture as

package/dist/lsp/types.d.ts

@@ -1,5 +1,5 @@
 /**
- * LSP sidecar — service-side types (design/64 §13.1). core 1.82+ ships `createLspTool(manager)`
+ * LSP sidecar — service-side types ([ref] §13.1). core 1.82+ ships `createLspTool(manager)`
  * + the `LspServerManager`/`LspSession`/`LspResult` SEAM (`@sema-agent/core`); the runner mounts the tool
  * when OUR manager is wired via `RunnerDeps.lspManager`. We re-export core's seam types — SINGLE SOURCE OF TRUTH,
  * incl. the injectable `LspTransport` (the WS-bridge connection to the language server inside E2B) + `LspReadText`.

package/dist/lsp/ws-transport.d.ts

@@ -17,7 +17,7 @@ export declare class WsLspTransport implements LspTransport {
     private isClosed;
     private keepalive;
     private awaitingPong;
-    /** design/121: server→client NOTIFICATION subscribers (publishDiagnostics etc.). */
+    /** [ref]: server→client NOTIFICATION subscribers (publishDiagnostics etc.). */
     private readonly notificationHandlers;
     constructor(ws: WsLike, requestTimeoutMs?: number, keepaliveMs?: number);
     /** Manager-visible liveness (LspTransport.closed): evict + reopen instead of reusing a dead connection. */
@@ -26,7 +26,7 @@ export declare class WsLspTransport implements LspTransport {
     private failAll;
     request(method: string, params: unknown, signal?: AbortSignal): Promise<unknown>;
     notify(method: string, params: unknown): void;
-    /** design/121 (core 1.220): subscribe to server→client notifications; returns unsubscribe. Additive —
+    /** [ref] (core 1.220): subscribe to server→client notifications; returns unsubscribe. Additive —
      *  core's diagnostics registry is the intended consumer; with no subscriber, behavior is byte-identical. */
     onNotification(handler: (method: string, params: unknown) => void): () => void;
     close(): Promise<void>;

package/dist/main.js

@@ -32,7 +32,7 @@ import { createHttpServer, explicitOperatorOk, hasServiceAuth } from "./http/ser
 import { exportMemoryScope } from "./memory-export.js";
 import { workflowModelAllowlistFor } from "./task-workflow.js";
 import { createMemoryBundleFaces } from "./memory-bundle-engine.js";
-import { backendOwnsControlPlane, createMemoryComplianceFaces, createMemoryOriginFaces } from "./memory-operator-faces.js";
+import { backendOwnsControlPlane, createMemoryComplianceFaces, createMemoryOriginFaces, createSessionMemoryStatusFace } from "./memory-operator-faces.js";
 import { performMemorySync } from "./memory-sync.js";
 import { startOtlpExporter } from "./observability/otel-exporter.js";
 import { HEARTBEAT_MS, backgroundAgentOutput, taskHandleOutput, taskHandleStop } from "./runs.js";
@@ -120,17 +120,23 @@ async function main() {
     await configCenter.applyLocalRemoteExec();
     const { backend, storeBackendDegraded, memoryEngine, memorySyncCursors, rosterStore, backgroundAgentStore, taskAttachmentStore, mailboxStore, memoryExportBackend, memorySyncRunner, sessionStore, breakerState, usageWindowStore, memoryPosture, taskListLane, } = await openStores({ config, logger, metrics, localRoot });
     const instanceId = uuidv7();
-    const memoryBundleFaces = memoryEngine ? createMemoryBundleFaces(memoryEngine) : undefined;
+    const sessionCaptureRecordStore = backend?.sessionCaptureRecords();
+    const memoryBundleFaces = memoryEngine ? createMemoryBundleFaces(memoryEngine, { ...(sessionCaptureRecordStore !== undefined ? { captureRecordStore: sessionCaptureRecordStore } : {}) }) : undefined;
     const memoryComplianceFaces = memoryEngine
         ? createMemoryComplianceFaces(memoryEngine, {
             onIncident: (err) => logger.warn("memory_compliance_incident", { code: err.code ?? null, detail: err.message }),
+            ...(sessionCaptureRecordStore !== undefined ? { captureRecordStore: sessionCaptureRecordStore } : {}),
         })
         : undefined;
     const memoryOriginFaces = memoryEngine
         ? createMemoryOriginFaces(memoryEngine, {
             onIncident: (err) => logger.warn("memory_origin_incident", { code: err.code ?? null, detail: err.message }),
+            ...(sessionCaptureRecordStore !== undefined ? { captureRecordStore: sessionCaptureRecordStore } : {}),
         })
         : undefined;
+    const sessionMemoryStatusFace = memoryEngine
+        ? createSessionMemoryStatusFace(memoryEngine, { ...(sessionCaptureRecordStore !== undefined ? { captureRecordStore: sessionCaptureRecordStore } : {}) })
+        : undefined;
     const adoptionBoot = await runAdoptionBootScan({ backend, logger });
     if (adoptionBoot.scanned > 0 || adoptionBoot.error !== undefined) {
         logger.info("adoption_boot_scan", { ...adoptionBoot });
@@ -211,6 +217,7 @@ async function main() {
             ...(config.memoryProvenance !== undefined ? { provenance: config.memoryProvenance } : {}),
             onIncident: (err) => logger.warn("memory_consolidation_incident", { code: err.code ?? null, detail: err.message }),
             onStopDetail: (audit) => logger.warn("memory_consolidation_stop_detail", audit),
+            ...(sessionCaptureRecordStore !== undefined ? { captureRecordStore: sessionCaptureRecordStore } : {}),
         })
         : undefined;
     for (const w of buildConsolidationValveAudit({
@@ -246,6 +253,7 @@ async function main() {
         mcpRevocations,
         config, logger, metrics, localRoot, promptSource: configCenter.promptSource, rosterStore, backgroundAgentStore, mailboxStore, usageWindowStore, brain,
         pricing, tracer, outcomeSink, elicitation, question, toolApproval, sessionStore, memoryEngine,
+        sessionCaptureRecordStore,
         memorySyncRunner, toolResultStore: runnerOffloadStore, sessionPolicyStore, runtimeCapsResolver, fileHistoryStore,
         legacyRewindBoundaryProbe: backend?.legacyRewindBoundaryProbe ? backend.legacyRewindBoundaryProbe.bind(backend) : undefined,
         permissionRuleStore: permissionRuleStores?.provider,
@@ -555,6 +563,7 @@ async function main() {
         posture: staticWiring.interaction.posture,
         streamApproval: streamApprovalGate.active ? "active" : streamApprovalGate.reason,
         subagentTranscripts: staticWiring.fleet.subagentTranscripts,
+        subagentTranscriptRetentionMs: config.backgroundAgentRetentionMs,
     });
     const stores = {
         runStore,
@@ -609,6 +618,7 @@ async function main() {
         memoryBundleImport: memoryBundleFaces ? memoryBundleFaces.importBundle : undefined,
         memoryCompliance: memoryComplianceFaces,
         memoryOriginFace: memoryOriginFaces,
+        sessionMemoryStatus: sessionMemoryStatusFace,
         memoryConsolidation: memoryConsolidationFaces,
         memoryOptOutGrant: memoryOptOutGrantStore,
         orgMemoryDirectory: orgMemoryAdmission.directory,
@@ -661,6 +671,7 @@ async function main() {
         mcpRevocations,
         mcpRevocationState: () => configCenter.mcpRevocationState(),
         configRefreshNow: () => configCenter.refreshNow(),
+        configCenterManagedKeys: () => configCenter.centerManagedKeys(),
         drainState,
         storeDegraded: storeBackendDegraded,
         storeLiveState: storeLiveProbe ? () => storeLiveProbe.state() : undefined,

package/dist/mcp-content-origin.d.ts

@@ -1,5 +1,5 @@
 /**
- * design/378(core 5.60.0)—— `McpServerSpec.contentOrigin` 的**闭词表单一属主**。
+ * [ref](core 5.60.0)—— `McpServerSpec.contentOrigin` 的**闭词表单一属主**。
  *
  * core 给 MCP 条目开了一个**内容出处声明**座位:一台 server 的整套工具的结果算 `"local"`(部署自己
  * 写的)/ `"execution"`(执行环境产物,`execIsExternalContent` 仍能收紧)/ `"external"`(第三方内容,

package/dist/memory-bundle-engine.d.ts

@@ -1,5 +1,5 @@
 /**
- * #264 v2-c —— `POST /v1/memory/{export,import}` 两口的**引擎接线**(core 5.40.0 design/178 v2-c)。
+ * [ref] v2-c —— `POST /v1/memory/{export,import}` 两口的**引擎接线**(core 5.40.0 [ref] v2-c)。
  *
  * ## 为什么需要这个模块(而不是在 main.ts 里直接 new)
  *
@@ -29,7 +29,7 @@
  * HTTP 面诚实 501。
  *
  * 🔴 首版把这件事当成**运行期**事实(照常挂载,让 core 每次抛 `memory.export_incomplete` / 422),
- * 被 codex 交叉复审驳倒(#277 提货批 [medium],验真后修):`typeof backend.exportSnapshotOf === "function"`
+ * 被 codex 交叉复审驳倒([ref] 提货批 [medium],验真后修):`typeof backend.exportSnapshotOf === "function"`
  * 是一次**属性检查**,boot 期就判得出;而且它是**永久**缺席(换后端才会变),不是瞬时状态。照旧挂着
  * 就成了「能力位说 yes、每一次调用都确定性失败」——本仓「says yes ⟺ route works」是结构性承诺,
  * 一个恒假的 yes 会让壳给用户开出一条走不通的迁移流程。
@@ -41,7 +41,7 @@
  * `memory.export_incomplete` —— 那是诚实的运行期拒,附录 A 单列一条。绝不在这里回落到「用通用读面拼
  * 一个包」:core 明写那正是它拒绝生产的形(a governance-less export is the laundering shape)。
  */
-import { type MemoryBackend, type MemoryExportBundle, type MemoryImportReport } from "@sema-agent/core";
+import { type MemoryBackend, type MemoryExportBundle, type MemoryImportReport, type SessionCaptureRecordStore } from "@sema-agent/core";
 /** 两口 HTTP 面消费的窄能力面(`ServiceDeps.memoryBundle{Export,Import}` 的实参来源)。 */
 export interface MemoryBundleFaces {
     exportScopes: (scopes: readonly string[]) => Promise<MemoryExportBundle>;
@@ -60,5 +60,7 @@ export interface MemoryBundleFaces {
 export declare function createMemoryBundleFaces(store: {
     backend: MemoryBackend;
     root: string;
+}, opts?: {
+    captureRecordStore?: SessionCaptureRecordStore;
 }): MemoryBundleFaces | undefined;
 //# sourceMappingURL=memory-bundle-engine.d.ts.map

package/dist/memory-bundle-engine.js

@@ -1,9 +1,9 @@
 import { MemoryEngine } from "@sema-agent/core";
-export function createMemoryBundleFaces(store) {
+export function createMemoryBundleFaces(store, opts) {
     const b = store.backend;
     if (typeof b.exportSnapshotOf !== "function" || typeof b.importBundleCommit !== "function")
         return undefined;
-    const engine = new MemoryEngine({ backend: store.backend, memoryDir: store.root });
+    const engine = new MemoryEngine({ backend: store.backend, memoryDir: store.root, ...(opts?.captureRecordStore !== undefined ? { captureRecordStore: opts.captureRecordStore } : {}) });
     return {
         exportScopes: (scopes) => engine.exportMemoryScopes(scopes),
         importBundle: (bundle, opts) => engine.importMemoryBundle(bundle, opts),

package/dist/memory-operator-faces.d.ts

@@ -1,6 +1,6 @@
 /**
- * design/316 件③ —— `GET /v1/memory/entries/:entryId/provenance` · `POST /v1/memory/erase` 两口的
- * **引擎接线**(core 5.57.0 `MemoryEngine.provenanceOf` / `eraseMemoryEntries`,design/178 v2-a/v2-b)。
+ * [ref] 件③ —— `GET /v1/memory/entries/:entryId/provenance` · `POST /v1/memory/erase` 两口的
+ * **引擎接线**(core 5.57.0 `MemoryEngine.provenanceOf` / `eraseMemoryEntries`,[ref] v2-a/v2-b)。
  *
  * ## 为什么是一个模块而不是 main.ts 里直接 new
  *
@@ -25,7 +25,7 @@
  * ⇒ 裁:`controlPlaneRoot` 缺席 ⇒ 本工厂返回 **undefined**,两口整个不挂载,HTTP 面诚实 501。今天满足这一
  * 条的只有 core 自带的 `FileMemoryEngineBackend`(它把控制面写死在 config-root 一侧);本仓两只 SQL 记忆
  * 孪生(`plugins/memory-engine-{pg,tidb}.ts`)没有这个面 ⇒ 在那些部署上两口不挂。SQL 控制面是 core 的候升件
- * (design/316 §0b-4 咨询单),**绝不**在本层为它们现造一个「够用的」控制面 —— 那是把一个 core 拒绝生产的
+ * ([ref] §0b-4 咨询单),**绝不**在本层为它们现造一个「够用的」控制面 —— 那是把一个 core 拒绝生产的
  * 半吊子治理面自己造出来,与 bundle 那条「a governance-less export is the laundering shape」同族。
  *
  * 🔴 这条判断是承重的,所以它有**机器钉**而不是只有这段注释:`test/memory-operator-faces.test.ts` 用一只
@@ -36,16 +36,16 @@
  *
  * 判据是一次**属性检查**、boot 期就判得出、而且是**永久**缺席(换后端才会变)——不是瞬时状态。照旧挂着
  * 就成了「能力位说 yes、每一次调用都确定性失败」,而本仓「says yes ⟺ route works」是结构性承诺。
- * (这条纪律是 #264 提货批被 codex 交叉复审驳倒后立的,见 memory-bundle-engine.ts 头注。)
+ * (这条纪律是 [ref] 提货批被 codex 交叉复审驳倒后立的,见 memory-bundle-engine.ts 头注。)
  *
  * ⚠️ **刻意不把审计/托管/证据三个可选面编进构造判定**:`committedSnapshotOf` / `custodyOf` 缺席时 core
  * 明写要诚实答 `binding:"unknown"` / `contentState:"capability-absent"` / `custody:"capability-absent"`
- * (#196 absence-reports-not-silent-green,engine.d.ts:748 逐字),那是一个**答得出话**的部署;把它们编进
+ * ([ref] absence-reports-not-silent-green,engine.d.ts:748 逐字),那是一个**答得出话**的部署;把它们编进
  * 构造判定会让这种部署整口消失,把 core 的诚实答案换成一句 501 谎话。`eraseWithEvidence` 同理:缺它时
  * core 自己响亮拒(`memory.erasure_evidence_unavailable`),那是**运行期**的诚实拒,与「换部署形态才行」
  * 不是一回事(附录 A 两条分列)。
  */
-import { type EntryProvenanceAccount, type MemoryBackend, type MemoryEntryOrigin, type MemoryErasureAttestation, type OriginClearanceRow } from "@sema-agent/core";
+import { type EntryProvenanceAccount, type MemoryBackend, type MemoryEntryOrigin, type MemoryErasureAttestation, type OriginClearanceRow, type SessionCaptureRecordStore, type SessionMemoryStatus } from "@sema-agent/core";
 /**
  * 控制面归属判据 —— 三个记忆操作面(合规两口 / 外源标记三口 / consolidation 阀门的 D1 拒启门)共用的
  * **同一只**谓词:backend 的面上带**非空** `controlPlaneRoot` 才算归属在案。空串与缺席同判「不归属」:
@@ -128,6 +128,7 @@ opts?: {
     onIncident?: (err: Error & {
         code?: string;
     }) => void;
+    captureRecordStore?: SessionCaptureRecordStore;
 }): MemoryComplianceFaces | undefined;
 /** 件② 三口 HTTP 面消费的窄能力面(`ServiceDeps.memoryOriginFace` 的实参来源)。 */
 export interface MemoryOriginFaces {
@@ -135,7 +136,7 @@ export interface MemoryOriginFaces {
      * §13-4① 视图面:点名 scope 里**每一条**带外源标记的条目 + 它的出处账。
      *
      * 🔴 `scopes` 由**调用方**给,本层不发明默认值:v1 本仓没有任何 scope 枚举读面(core 5.59.0 的
-     * `listMemoryScopes` 已到 File 腿、SQL 腿是 core 候升件 #437④,本仓尚未接线),而「空 scope 名单」
+     * `listMemoryScopes` 已到 File 腿、SQL 腿是 core 候升件 [ref]④,本仓尚未接线),而「空 scope 名单」
      * 与「查全店」在这条路上是两件事 —— 猜一个默认名单会让审计的**不完备变成静默的**(空数组与
      * 「这些 scope 干净」同形)。缺参时路由那侧 400 并指路,理由与文案同源于此。
      */
@@ -161,8 +162,8 @@ export interface MemoryOriginFaces {
     }>;
 }
 /**
- * design/316 件② —— 外源标记人面的**引擎接线**(core 5.59.0 `MemoryEngine.listExternalOriginEntries` /
- * `listOriginClearances` / `clearEntryOrigin`,design/336 §13-4①②)。
+ * [ref] 件② —— 外源标记人面的**引擎接线**(core 5.59.0 `MemoryEngine.listExternalOriginEntries` /
+ * `listOriginClearances` / `clearEntryOrigin`,[ref] §13-4①②)。
  *
  * ## 控制面归属:判据与合规两口**逐字同一条**(§1 F-9 裁),但理由更硬
  *
@@ -182,11 +183,11 @@ export interface MemoryOriginFaces {
  * 而且下一次 resume 调用大概率落到另一台副本、读不到那行 ⇒ 一条被清标的记忆连同它的托管字节一起消失。
  * 本仓是 stateless replicas(CLAUDE.md 首段)。所以判在**构造期**:工厂返 undefined、三口整个不挂、
  * HTTP 面诚实 501,与 `createMemoryComplianceFaces` 同形同码不同文案(要查的旋钮不是同一个)。
- * SQL 控制面是 core 的候升件(design/316 §0b-4 / #437④),**绝不**在本层为它现造一个。
+ * SQL 控制面是 core 的候升件([ref] §0b-4 / [ref]④),**绝不**在本层为它现造一个。
  *
  * ## 刻意不做的两件事
  *
- * ⚠️ **不把 `listScopes` 编进构造判定**:core 5.59.0 长出了 `listMemoryScopes`(#437③,File 腿在场、
+ * ⚠️ **不把 `listScopes` 编进构造判定**:core 5.59.0 长出了 `listMemoryScopes`([ref]③,File 腿在场、
  *    SQL 腿候升),但那是**发现链**的面,不是本族三口的执行前提 —— 把它编进来会让一个「scope 名由运维
  *    自己拿着」的部署整口消失。发现链的不完备由 `GET …/external` 缺参时的 400 文案如实说出来。
  * ⚠️ **不在 seam 里翻译拒因码**:core 的 origin-clear 族是**闭集**,翻译点只有一个(路由的 switch),
@@ -207,5 +208,34 @@ opts?: {
     onIncident?: (err: Error & {
         code?: string;
     }) => void;
+    captureRecordStore?: SessionCaptureRecordStore;
 }): MemoryOriginFaces | undefined;
+/** [ref] seam① 的窄能力面(`ServiceDeps.sessionMemoryStatus` 的实参来源)。 */
+export interface SessionMemoryStatusFace {
+    status: (sessionId: string) => Promise<SessionMemoryStatus>;
+}
+/**
+ * [ref] seam①([ref] §S-7,core 7.0.2 [ref] 件1)—— `GET /v1/sessions/:id/memory-status` 的引擎面。
+ * 命名照 CLAUDE.md 工厂律:返回带行为的活对象 ⇒ `create*`。
+ *
+ * 挂载判据与合规/清标两族**同一条 F-9 裁**(`backendOwnsControlPlane`,理由见文件头):
+ * `committedCount` / `foldedCount` / `lastCaptureAt` 读的是引擎控制面的 lineage 台账 ——
+ * 控制面归属缺席的部署上(两只 SQL 记忆孪生),core 会把控制面落到**副本本地盘**,一个「可读的空目录」
+ * 让 core 面答出 `committedCount: 0`(readLineageRecord 对空目录**不抛**,亲读 engine.js)——
+ * 那是**说谎的 0**,比缺席更坏(S-7 的诚实键律:可读零必须是真零)。⇒ 归属缺席 ⇒ 工厂返 undefined,
+ * HTTP 面诚实 501,与 erase/origin 同码同分支。
+ *
+ * `captureRecordStore` = [ref]② 的 SQL 载体(main.ts 单实例,与 Runner/其余引擎同源 —— 全站同批注入律,
+ * 机器钉 capture-optout-lane ②):`captureOptedOut` / `optOutSource` 两键经它读,多副本部署上答的才是
+ * 跨副本的真记录。缺席(local 车道)⇒ core 文件三腿,单机字节不变。
+ *
+ * 面**不抛**(core 契约:sessionMemoryStatus never throws —— 每个事实源各自 catch 折缺席键);
+ * 不接 onIncident:这条只读路径上今天零 sink 站点,而且缺席键本身就是它的披露形。
+ */
+export declare function createSessionMemoryStatusFace(store: {
+    backend: MemoryBackend;
+    root: string;
+}, opts?: {
+    captureRecordStore?: SessionCaptureRecordStore;
+}): SessionMemoryStatusFace | undefined;
 //# sourceMappingURL=memory-operator-faces.d.ts.map

package/dist/memory-operator-faces.js

@@ -43,6 +43,7 @@ export function createMemoryComplianceFaces(store, opts) {
         backend: store.backend,
         memoryDir: store.root,
         ...(opts?.onIncident !== undefined ? { onIncident: opts.onIncident } : {}),
+        ...(opts?.captureRecordStore !== undefined ? { captureRecordStore: opts.captureRecordStore } : {}),
     });
     return {
         provenanceOf: (entryId) => engine.provenanceOf(entryId),
@@ -66,6 +67,7 @@ export function createMemoryOriginFaces(store, opts) {
         backend: store.backend,
         memoryDir: store.root,
         ...(opts?.onIncident !== undefined ? { onIncident: opts.onIncident } : {}),
+        ...(opts?.captureRecordStore !== undefined ? { captureRecordStore: opts.captureRecordStore } : {}),
     });
     return {
         listExternal: (scopes) => engine.listExternalOriginEntries(scopes),
@@ -73,4 +75,14 @@ export function createMemoryOriginFaces(store, opts) {
         clear: (entryId, input) => engine.clearEntryOrigin(entryId, input),
     };
 }
+export function createSessionMemoryStatusFace(store, opts) {
+    if (!backendOwnsControlPlane(store.backend))
+        return undefined;
+    const engine = new MemoryEngine({
+        backend: store.backend,
+        memoryDir: store.root,
+        ...(opts?.captureRecordStore !== undefined ? { captureRecordStore: opts.captureRecordStore } : {}),
+    });
+    return { status: (sessionId) => engine.sessionMemoryStatus(sessionId) };
+}
 //# sourceMappingURL=memory-operator-faces.js.map

package/dist/memory-origin-fence.d.ts

@@ -1,42 +1,14 @@
-/**
- * design/383 S-6 / S-50 §三(S-49 F3)—— 带 `origin` 标的记忆条目在 wire 读口上的 **fence-or-refuse**。
- *
- * ## 病(S-6 禁形)
- * 记忆条目的 `origin` 标(design/336 provenance 标记族)是 additive 键。旧 SDK / 旧壳的 strict/strip parse 会
- * **静默剥掉**它 ⇒ 一条「外源已标」的条目摊平成无标文本,消费端再把它当洁净内容引用/回写 = 出处被洗掉。
- * core 无法在 wire 上强制(它不认识客户端),383 §3.4 显式授权 server 裁三点,S-50 §三裁定如下。
- *
- * ## 三点裁定(逐字)
- *  1. **判定点 = 端点级能力位,不猜客户端版本**:server 无 per-client 版本可见性。凡投影带标条目的读口,
- *     **缺省不投带标条目**;消费方以查询参数 `originAware=1` 声明「我认识 origin 键族」后才放行。参数缺席 =
- *     老客户端假定成立 ⇒ fence。
- *  2. **粒度 = 整条目扣留,不做字段降级**:字段级(剥 origin 只给文本)恰是被禁的摊平。整条目扣留 + 计数披露
- *     (`refusedUntrusted` 计数拒的既有先例形):响应带 `withheldOriginTagged: <n>`(additive,**只在 n>0 时铸**——
- *     只记真),消费端机读得出「有 n 条因我没声明能力而被围栏」。
- *  3. **能力位形 = 每请求查询参数,不是每客户端注册**:注册制引入一张会陈旧的表;查询参数让「谁认识键族」由
- *     当次调用自证,零状态。SDK 新版缺省带 `originAware=1`;旧 SDK 不带 ⇒ 结构性 fence。
- *
- * ## 判「带标」的谓词
- * 条目对象上 **own** `origin` 键且值非 `undefined`。不读 `origin` 的内部形(那是 core 的开放判别式),只判在场。
- *
- * ## 射程(S-50 §三.1 点名的读口,本仓现状三处)
- *  · `GET /v1/memory/export?scope=`(memory-policy.ts,属主自助条目读,分页/全量两腿)
- *  · `GET /v1/memory/origin/external?scopes=`(memory-origin.ts,外源标记人面 —— 它的每条都带标,缺省下
- *    全部扣留 + 计数:operator 的工具必须声明能力位才看得见,这正是「围栏」的意思,不是 bug)
- *  · `POST /v1/memory/export`(memory-bundle.ts,治理携出包 —— 包经 SDK 落盘再 import,旧 SDK 剥标后 import
- *    会把无标条目当洁净内容收进另一台 = 跨库洗出处;所以包也围栏,计数键落在包顶层)
- * 不围栏的:`GET /v1/memory/entries/:id/provenance`(单条出处账,消费它的人就是来读 origin 的,且响应根不是
- * 条目)、`GET /v1/memory/origin/clearances`(`buildClearanceRowWire` 深白名单投影,已是显式形)。
- *
- * ## 读面行为收窄 = L3(S-50 §三.3 成文)
- * 存量消费者若依赖读到带标条目(现状 = origin 键族尚未在这些读口上稳定出现;真实射程 = 蒸馏产物到货后的新条目),
- * 从本版起须带 `originAware=1`。判据入 383 片3 判据面。
- */
+import { type MemoryExportBundle } from "@sema-agent/core";
 /** 查询参数名与合法值(闭集:只认字面 `1`;`true`/`yes` 不认 —— 能力位不做宽松解析)。 */
 export declare const ORIGIN_AWARE_QUERY = "originAware";
 /** 从 `URLSearchParams` 读能力位:`originAware=1` ⇒ true;缺席/其它值 ⇒ false(老客户端假定)。 */
 export declare function readOriginAware(params: URLSearchParams): boolean;
-/** 「这条条目带 origin 标吗」—— own 键在场且非 undefined。纯谓词,不读 origin 的形。 */
+/** 「这条条目带 origin 标吗」—— 载体三形(G53 [ref] + codex R1-high 后齐):
+ *  ① 顶层 `origin`(listExternal 投影行)—— own 键在场且非 undefined 即带标(不读形;typed null/坏形也算:
+ *    core 读取器对 null 会抛,围栏对读不出的载体只许扣留不许放行);
+ *  ② `frontmatter.origin`(core `MemoryEntry`,138 S3)—— 同 own 键判;
+ *  ③ `frontmatter.extra` 的 origin 悬置形块 —— 单源直调 core 出口的 `committedOriginOf`(typed 缺席时读
+ *    extraOriginCarriers[0];退化形记 at:0 也算载体,过近似=安全方向),server 不自铸解析。 */
 export declare function isOriginTagged(entry: unknown): boolean;
 /**
  * 围栏(`build*`:纯数据)。`originAware=true` ⇒ 原数组同一引用、无计数键(零行为差);否则扣留带标条目,
@@ -47,4 +19,17 @@ export declare function buildOriginFence<T>(entries: readonly T[], originAware:
     entries: readonly T[];
     withheldOriginTagged?: number;
 };
+/**
+ * 治理携出包的围栏(`build*`:纯数据)。`originAware=true` ∨ 零扣留 ⇒ **原对象同一引用**(逐字节旧形,
+ * integrity 一个字不动);否则:扣留带标条目 + 顶层 `withheldOriginTagged`(只记真),并按扣留后内容重铸
+ * integrity —— `entryCount`=kept 数、`revs`=kept 的 id→rev(core 校验器要求 revs 基数≡条目 id 集,
+ * 只重算 entryCount/sectionHashes 而留旧 revs 同样过不了自校验)、`sectionHashes.entries`=kept 的
+ * canonical 哈希;meta/governance/residuals 三段内容未动 ⇒ 三段哈希原样。
+ * governance 行(challenges/lineage)**不**随条目扣留:它们不携 origin 键(无标可剥,S-6 的摊平病对它们
+ * 不成立),扣了反而是静默改写治理史;import 侧对超出 entries 的引用按 referentialOrphans 具名报告,
+ * 诚实方向一致。
+ */
+export declare function buildOriginFencedBundle(bundle: MemoryExportBundle, originAware: boolean): MemoryExportBundle & {
+    withheldOriginTagged?: number;
+};
 //# sourceMappingURL=memory-origin-fence.d.ts.map