@sema-agent/server 7.135.0 → 7.137.0

package/dist/broker/main.js

@@ -0,0 +1,20 @@
+import { BROKER_HOST, BROKER_LEASE_PATH, BROKER_LEASE_POLL_MS, BROKER_PORT, BROKER_PROBE_ARG } from "./constants.js";
+import { probeBroker, runBroker } from "./broker.js";
+const PROBE_TIMEOUT_MS = 2_000;
+async function main() {
+    if (process.argv.includes(BROKER_PROBE_ARG)) {
+        process.exit((await probeBroker(BROKER_HOST, BROKER_PORT, PROBE_TIMEOUT_MS)) ? 0 : 1);
+    }
+    await runBroker({
+        leasePath: BROKER_LEASE_PATH,
+        host: BROKER_HOST,
+        port: BROKER_PORT,
+        pollMs: BROKER_LEASE_POLL_MS,
+        log: (e) => void process.stdout.write(`${JSON.stringify(e)}\n`),
+    });
+}
+main().catch((e) => {
+    process.stderr.write(`${JSON.stringify({ event: "broker_failed", error: e instanceof Error ? e.message : String(e) })}\n`);
+    process.exit(1);
+});
+//# sourceMappingURL=main.js.map

package/dist/budget.d.ts

@@ -8,7 +8,7 @@
 import { type Model, type ModelPricing, type TracerHook } from "@sema-agent/core";
 import type { Metrics } from "./observability/metrics.js";
 import type { QuotaTracker } from "./observability/cost-quota.js";
-import type { FleetUsageAccumulator } from "./fleet-client.js";
+import type { FleetUsageBins } from "./fleet-client.js";
 import type { FleetLeaseManager } from "./fleet-lease.js";
 import { type PromptManifestTracker } from "./observability/prompt-manifest.js";
 /** ③ Per-model pricing keyed by model id (core falls back to each Model.cost when a model is absent).
@@ -108,7 +108,7 @@ export { type PromptManifestRecord, promptManifestRecordOf, configAssembledRecor
  * fires for EVERY call (top-level + async + council sub-tasks) → `model_cost_micro_usd_total` is the authoritative
  * spend, and (when a {@link ModelUsageTracker} is supplied) the per-task `modelUsage` echo's source.
  */
-export declare function createTracer(metrics: Pick<Metrics, "inc" | "observe">, costQuota?: QuotaTracker, modelUsage?: ModelUsageTracker, fleetUsage?: Pick<FleetUsageAccumulator, "record">, fleetLease?: Pick<FleetLeaseManager, "recordSpend">, quotaWeightFor?: (model: string) => number, promptManifests?: PromptManifestTracker): TracerHook;
+export declare function createTracer(metrics: Pick<Metrics, "inc" | "observe">, costQuota?: QuotaTracker, modelUsage?: ModelUsageTracker, fleetUsage?: Pick<FleetUsageBins, "record" | "pinExecution">, fleetLease?: Pick<FleetLeaseManager, "recordSpend" | "pinExecution">, quotaWeightFor?: (model: string) => number, promptManifests?: PromptManifestTracker): TracerHook;
 /**
  * [ref] side-query 记账 seam(codex R3 high:sideQuery 不走 core tracer——brain.stream 直调不发
  * brain.call——createTracer 的四路 sink(costQuota/model_cost 指标/fleetUsage 批报/fleetLease 本地扣减)
@@ -121,7 +121,7 @@ export declare function createTracer(metrics: Pick<Metrics, "inc" | "observe">,
  * (保守,绝不少收);根修=core 在 SideQueryResult 上回权威 costMicroUsd(已提货 core)。model 标签/
  * weight 键用**路由身份 r.model**(池配置有界)非 servedModel(provider 上报,无界)。
  */
-export declare function createSideQueryAccountant(metrics: Pick<Metrics, "inc">, costQuota?: QuotaTracker, fleetUsage?: Pick<FleetUsageAccumulator, "record">, fleetLease?: Pick<FleetLeaseManager, "recordSpend">, quotaWeightFor?: (model: string) => number): (principal: string | undefined, r: {
+export declare function createSideQueryAccountant(metrics: Pick<Metrics, "inc">, costQuota?: QuotaTracker, fleetUsage?: Pick<FleetUsageBins, "record">, fleetLease?: Pick<FleetLeaseManager, "recordSpend">, quotaWeightFor?: (model: string) => number): (principal: string | undefined, r: {
     model: string;
     usage?: {
         input?: number;

package/dist/budget.js

@@ -77,6 +77,10 @@ export function createTracer(metrics, costQuota, modelUsage, fleetUsage, fleetLe
     const modelId = cardinalityGuard(256, () => metrics.inc("metric_label_overflow_total", { label: "model" }));
     const providerName = cardinalityGuard(64, () => metrics.inc("metric_label_overflow_total", { label: "provider" }));
     return (e) => {
+        if (e.kind === "task.start") {
+            fleetUsage?.pinExecution();
+            fleetLease?.pinExecution();
+        }
         if (e.kind === "brain.call") {
             metrics.inc("brain_calls_total", { provider: providerName(e.provider ?? "unknown"), model: modelId(e.model) });
             if (e.costMicroUsd) {

package/dist/capabilities/composite-members.d.ts

@@ -38,7 +38,7 @@ import type { NamedKeysOf } from "../request-key-closure.js";
  * B.2b)与 CHANGELOG。present-iff 的位与成员照样登记(在场律写在附录的「在场律」列)。
  */
 export declare const COMPOSITE_CAPABILITY_MEMBERS: {
-    readonly deviceExecutor: readonly ["enabled", "protocolVersion", "maxInflightPerDevice", "wsPath", "management"];
+    readonly deviceExecutor: readonly ["enabled", "protocolVersion", "maxInflightPerDevice", "wsPath", "management", "relayUrl"];
     readonly fleet: readonly ["stream", "sessionScope", "observe", "resume", "bgNotifyFailClosed", "steerPriority", "hookFailureNotice", "leaseClient", "generationEcho"];
     readonly memoryEngine: readonly ["backend", "vectorMode"];
     readonly store: readonly ["declared", "backend", "durable", "degradedReason", "sql"];
@@ -55,6 +55,7 @@ export declare const COMPOSITE_CAPABILITY_MEMBERS: {
     readonly sealedKey: readonly ["alg", "publicKeyId", "publicKey"];
     readonly workspaceSync: readonly ["persist", "keep", "timeoutMs", "cache"];
     readonly userAttachments: readonly ["entries", "kinds", "supplies", "limits"];
+    readonly credentialPlane: readonly ["sandboxGit"];
 };
 type CompositeTable = typeof COMPOSITE_CAPABILITY_MEMBERS;
 /** 值的**具名成员对象臂**(标量 / 字面词 / `false` / `null` / `undefined` / 数组 / 函数臂剥掉)。 */

package/dist/capabilities/composite-members.js

@@ -1,5 +1,5 @@
 export const COMPOSITE_CAPABILITY_MEMBERS = {
-    deviceExecutor: ["enabled", "protocolVersion", "maxInflightPerDevice", "wsPath", "management"],
+    deviceExecutor: ["enabled", "protocolVersion", "maxInflightPerDevice", "wsPath", "management", "relayUrl"],
     fleet: ["stream", "sessionScope", "observe", "resume", "bgNotifyFailClosed", "steerPriority", "hookFailureNotice", "leaseClient", "generationEcho"],
     memoryEngine: ["backend", "vectorMode"],
     store: ["declared", "backend", "durable", "degradedReason", "sql"],
@@ -16,6 +16,7 @@ export const COMPOSITE_CAPABILITY_MEMBERS = {
     sealedKey: ["alg", "publicKeyId", "publicKey"],
     workspaceSync: ["persist", "keep", "timeoutMs", "cache"],
     userAttachments: ["entries", "kinds", "supplies", "limits"],
+    credentialPlane: ["sandboxGit"],
 };
 export function gateCompositeMembers(body) {
     return body;

package/dist/capabilities/engine-capabilities.js

@@ -3,6 +3,7 @@ import { ownCredentialsWithheld, ownCredentialValuesWithheld } from "../server-s
 const ENGINE_CAPABILITY_FACTS = {
     "inherit_env.own_credentials_withheld": ownCredentialsWithheld,
     "inherit_env.own_credential_values_withheld": ownCredentialValuesWithheld,
+    "mods.skill_seat": () => false,
 };
 export function engineCapabilityBits() {
     const out = {};

package/dist/capabilities/mcp-probe.d.ts

@@ -33,7 +33,7 @@
  *    在 core 那边没有任何期限(core `docs/KNOWN-LIMITS.md`)—— 那一形上本面同样没有期限,补偿只有限速与缓存。
  */
 import { type McpServerSpec } from "@sema-agent/core";
-import type { UrlCredentialFacts } from "../url-credential.js";
+import type { DeclarationRefusal } from "../request-declaration-refusal.js";
 /**
  * 本面的**拒码闭集**(设计稿 §2 的四枚)。闭集写成型,是为了让 {@link MCP_PROBE_HTTP_STATUS} 那张表
  * 「漏一枚 = 编译红」—— [ref] 的安全轴纪律:词表是闭集,未处置的成员必须是编译错误而不是运行期惊喜。
@@ -158,8 +158,9 @@ export interface McpProbeRefusal {
     readonly message: string;
     /** `request.body_shape` 专用:词表外 / 本面不接线的键,全路径形(已清洗+截断+排序+封顶)。 */
     readonly unknownKeys?: readonly string[];
-    /** [ref]:申报的 `transport.url` 带凭据 ⇒ `field` + `reason`(与提交腿同一只回答者交回的同一组机读位,原样转述)。 */
-    readonly facts?: UrlCredentialFacts;
+    /** 申报超上限 ⇒ 撞帽机读位一组键(`field` · `reason:"over_cap"` · `count` · `cap`);申报的 `transport.url` 带凭据 ⇒ `field` + `reason` ——
+     *  与提交腿同一只回答者交回的同一组机读位,原样转述。 */
+    readonly facts?: DeclarationRefusal["facts"];
 }
 /**
  * `POST …/probe` 的体读器:闭形、逐条点名、零静默丢。成功 ⇒ 交给 core 的 `specs`(**原样**转发被读出来的
@@ -167,7 +168,7 @@ export interface McpProbeRefusal {
  *
  * ## 申报「能不能原样用」:问提交腿 fresh 门**同一只**回答者,不另判
  * 本面只判自己那一层(体是对象、顶层只受理 `mcpServers`、这个键必填);`mcpServers` 本身 —— 列表的形、上限、每条的键名与键值 —— 全部交给
- * `task-mcp.ts` 的 `requestMcpDeclarationRefusal`,拒(码 + 句 + `unknownKeys` + url 带凭据那一形的 `field` / `reason`)原样转述:同一份申报在两扇门上只有一个答案,零拨号之前就给。
+ * `task-mcp.ts` 的 `requestMcpDeclarationRefusal`,拒(码 + 句 + `unknownKeys` + 撞帽 / url 带凭据两形的机读位)原样转述:同一份申报在两扇门上只有一个答案,零拨号之前就给。
  * 回答者受理的申报由**同一只**读器(`validateRequestMcp`)交回,读器的产物就是申报本身(只差判官自己的合法归一),经 `toCoreMcpServerSpec`
  * 得到的就是一条任务提交会交给引擎的那一份 —— 本面拨的正是它。读器只在回答者受理之后才跑,所以它对重放存量 body 才有的降级留痕
  * (`source` 写坏的 F 类丢弃)不会在一次被拒的探测上虚记。

package/dist/capabilities/scenarios.d.ts

@@ -2,7 +2,7 @@ import { type WebFetchConfig, type BackgroundAgentStore, type CheckpointStore, t
 import type { Logger } from "../observability/logger.js";
 import { type SubagentExtraToolSet } from "./builtin-tools.js";
 import { type RepoReadClient } from "./repo-tools.js";
-import { type LoadedSkill, type ScenarioSkillEntry } from "./skills.js";
+import { type LoadedSkill, type RunSkillEntry, type ScenarioSkillEntry, type SkillSource } from "./skills.js";
 import { type ScenarioHands } from "./hands-lane.js";
 import type { DelegationRootWitness } from "../delegated-session-owner.js";
 /**
@@ -315,14 +315,29 @@ export declare function centerScenarios(deps: ScenarioDeps, specs: CenterScenari
     shadows: string[];
 };
 /**
- * Personalization seam: merge the caller's own skills AFTER the scenario's, with
- * SCENARIO-WINS on a name clash — the scenario / center skills own the name (they are the deployment's baseline
- * wording, not an enforcement face: permissions / write gates / hooks do not ride on skills, and a caller may
- * unload the whole set with `disableSkills`, [ref]); user content never shadows them. Duplicate names within the user list keep the first. Clashes are logged for audit
- * (silent drops would make "my skill didn't fire" undebuggable). Input is already shape/size-validated
- * by the HTTP layer (validateUserSkills); this stays pure merge policy.
+ * 一条 run 的技能(交给引擎的 `TaskSpec.skills`)与它的名册(`wiring_manifest.skills`)—— **同一次合并的两个投影**,铸点只有 {@link buildRunSkills}。
+ *  · `specs`  —— 交给引擎的那一份(`undefined` = 一只都没有且没被关;`disable` ⇒ 显式 `[]`,引擎对空表零 `<skills>` 块、不挂 `Skill`);
+ *  · `roster` —— 同一组、同一个序,逐条带来处;零技能 ⇒ `[]`(零技能是一句陈述,不是缺席)。
  */
-export declare function mergeUserSkills(scenarioSkills: SkillSpec[] | undefined, userSkills: SkillSpec[] | undefined, logger?: Logger): SkillSpec[] | undefined;
+export interface RunSkills {
+    readonly specs: SkillSpec[] | undefined;
+    readonly roster: RunSkillEntry[];
+}
+/**
+ * Personalization seam + run 名册的**唯一铸点**:调用方自带的技能接在场景的之后,**同名场景赢**(场景 / 中心的技能拥有那个名字 —— 它们是部署的基线措辞,
+ * 不是执法面:权限 / 写门 / hook 都不骑在技能上,调用方要整组卸掉用 `disableSkills`,[ref]);用户内容永不遮住它们。用户表内重名留第一个。
+ * 被丢的名字落审计行(静默丢会让「我的技能没生效」查不出来)。形已由 HTTP 门判过(`validateUserSkills`);本函数只做合并政策与来处。
+ *
+ * 来处(`roster[].source`):场景那一半按**部署装载簿**的来处标(`deploymentSources`:装载腿写下的 `LoadedSkill.source`,名字在装载簿里唯一 ——
+ * 装载器同名即抛、配置源按名覆盖);场景里有、装载簿里没有的技能是嵌入方场景代码自带的 ⇒ `factory`(本部署自带,不是配置源交来的、也不是这次请求带的)。
+ * 请求那一半恒 `request`。`disable` ⇒ 两个投影都空(`specs: []`、`roster: []`)。
+ */
+export declare function buildRunSkills(args: {
+    readonly scenario: SkillSpec[] | undefined;
+    readonly request: readonly SkillSpec[] | undefined;
+    readonly disable: boolean;
+    readonly deploymentSources: ReadonlyMap<string, SkillSource>;
+}, logger?: Logger): RunSkills;
 /** center caps view 的解析结果两键(形状锚定)。`scenario` null = 三层皆未配。 */
 export interface ScenarioRuling {
     scenario: string | null;

package/dist/capabilities/scenarios.js

@@ -262,23 +262,28 @@ const REVIEWER_ROLE_TEXT = "You are a senior code reviewer. Call repo_tree to ma
     "the files in scope, then review them yourself. " +
     "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.";
-export function mergeUserSkills(scenarioSkills, userSkills, logger) {
-    if (!userSkills || userSkills.length === 0)
-        return scenarioSkills;
-    const reserved = new Set((scenarioSkills ?? []).map((s) => s.name));
-    const out = [...(scenarioSkills ?? [])];
+export function buildRunSkills(args, logger) {
+    if (args.disable)
+        return { specs: [], roster: [] };
+    const scenario = args.scenario ?? [];
+    const roster = scenario.map((s) => ({ name: s.name, description: s.description, source: args.deploymentSources.get(s.name) ?? "factory" }));
+    if (!args.request || args.request.length === 0)
+        return { specs: args.scenario, roster };
+    const reserved = new Set(scenario.map((s) => s.name));
+    const specs = [...scenario];
     const dropped = [];
-    for (const s of userSkills) {
+    for (const s of args.request) {
         if (reserved.has(s.name)) {
             dropped.push(s.name);
             continue;
         }
         reserved.add(s.name);
-        out.push(s);
+        specs.push(s);
+        roster.push({ name: s.name, description: s.description, source: "request" });
     }
     if (dropped.length > 0)
         logger?.warn("user_skills_dropped", { reason: "name reserved by scenario (or duplicate)", names: dropped });
-    return out;
+    return { specs, roster };
 }
 function registeredScenariosClause(known) {
     return `this deployment's scenarios are: ${known.join(", ")}`;

package/dist/capabilities/skills.d.ts

@@ -1,4 +1,4 @@
-import type { SkillSpec } from "@sema-agent/core";
+import type { SkillSpec, TaskSpec } from "@sema-agent/core";
 import type { RemoteExecProvider } from "../execution-lane-caps.js";
 import { type Logger } from "../observability/logger.js";
 /**
@@ -90,14 +90,37 @@ export declare function loadDeploymentSkills(config: {
 /** 一个技能范围交进 `TaskSpec` 的技能(场景工厂的 `skills`)。范围从哪来见 `scenarios.ts` 的 `BUILTIN_SCENARIO_SKILL_SCOPE`(center 场景 = 它自己的名字)。 */
 export declare function skillsForScenario(loaded: readonly LoadedSkill[], scope: string): SkillSpec[];
 /**
- * [ref] —— 场景卡技能清单的一条(`GET /v1/capabilities/scenarios/:name` 的 `skills[]`):名字 / 描述 / 来处,**不带正文**,也不带技能上的两只工具清单
- * (`allowedTools` / `disallowedTools`)。名字就是提交体 `userInvokedSkills` 点名时用的那个串。
+ * 技能清单的一条 —— **一张形,两个面**:场景卡(`GET /v1/capabilities/scenarios/:name` 的 `skills[]`,[ref])与 run 级名册
+ * (`wiring_manifest.skills[]`)。名字 / 描述 / 来处,**不带正文**,也不带技能上的两只工具清单(`allowedTools` / `disallowedTools`)。
+ * 名字就是提交体 `userInvokedSkills` 点名时用的那个串。两个面只差来处的值域(`S`):场景卡上只有部署两处,run 名册上多一个 `request`。
  */
-export interface ScenarioSkillEntry {
+export interface SkillListEntry<S extends string> {
     readonly name: string;
     readonly description: string;
-    readonly source: SkillSource;
+    readonly source: S;
 }
+/** 场景卡技能清单的一条(来处 = 部署两处)。 */
+export type ScenarioSkillEntry = SkillListEntry<SkillSource>;
+/** run 级技能来处的闭集 = 部署两处({@link SkillSource})∪ 本请求体 `skills`。 */
+export type RunSkillSource = SkillSource | "request";
+/** run 级名册的一条(`wiring_manifest.skills[]`)。铸点唯一:`capabilities/scenarios.ts` 的 `buildRunSkills`。 */
+export type RunSkillEntry = SkillListEntry<RunSkillSource>;
+/**
+ * run 级技能名册在 TaskSpec 上的**显式字段键** —— 与执行车道字段(`hands-lane.ts` 的 `HANDS_LANE_FIELD`,[ref])同一形:symbol 键随
+ * spread / rest 解构走(续跑腿的 `taskConfig` 就是 rest 解构出来的),对上游 core 的键面不可见(JSON / 结构化克隆跳过 symbol 键)。
+ * 铸点唯一 = `boot/resolve-spec.ts` 的 resolveSpec 出口({@link stampRunSkills});读点唯一 = {@link runSkillsOf}(每条投 `wiring_manifest` 的腿)。
+ */
+export declare const RUN_SKILLS_FIELD: unique symbol;
+/**
+ * 铸名册(**单一属主**:只许 resolveSpec 的出口调用)。字段 `enumerable`(复制得走)、`writable:false` + `configurable:false`(同一只 spec 被第二次铸 ⇒
+ * 当场 TypeError,两个写者是漂移的成因)。名册冻结一份拷贝(spec 与腿不共享可变引用)。
+ */
+export declare function stampRunSkills<T extends TaskSpec>(spec: T, roster: readonly RunSkillEntry[]): T;
+/**
+ * 读名册。`undefined` = 这只 spec 不是本仓装配出口产的(嵌入方自写 `resolveSpec` / 测试桩)⇒ 腿上没有关于技能的陈述(段缺席)。
+ * 不是保护型量(缺席只少一段披露,不放宽任何东西)⇒ 缺席照常跑,与车道字段的「缺席即拒」不同。入参收 `object`:续跑腿手里是 rest 解构出来的 taskConfig。
+ */
+export declare function runSkillsOf(spec: object): readonly RunSkillEntry[] | undefined;
 /** 一个技能范围的卡上清单 —— 与 {@link skillsForScenario} 同一只过滤、同一个序,只是投影不同。 */
 export declare function scenarioSkillEntries(loaded: readonly LoadedSkill[], scope: string): ScenarioSkillEntry[];
 /** {@link parseFrontmatter} 的三种读数(闭集):`absent` = 第一行不是围栏,没有 frontmatter(正当的全局技能)· `block` = 围栏收好了的块 · `unclosed` = 第一行是围栏而块没收好(读不了 —— 调用方拒载)。 */

package/dist/capabilities/skills.js

@@ -127,6 +127,14 @@ function skillsInScope(loaded, scope) {
 export function skillsForScenario(loaded, scope) {
     return skillsInScope(loaded, scope).map((k) => k.spec);
 }
+export const RUN_SKILLS_FIELD = Symbol("sema-server.runSkills");
+export function stampRunSkills(spec, roster) {
+    Object.defineProperty(spec, RUN_SKILLS_FIELD, { value: Object.freeze(roster.map((e) => Object.freeze({ ...e }))), enumerable: true, writable: false, configurable: false });
+    return spec;
+}
+export function runSkillsOf(spec) {
+    return spec[RUN_SKILLS_FIELD];
+}
 export function scenarioSkillEntries(loaded, scope) {
     return skillsInScope(loaded, scope).map((k) => ({ name: k.spec.name, description: k.spec.description, source: k.source }));
 }

package/dist/capability-facts.d.ts

@@ -23,6 +23,7 @@ import type { ServiceConfig } from "./config.js";
 import type { OwnerAwareSessionStore } from "./security.js";
 import type { ServiceFileHistoryStore } from "./plugins/store-backend.js";
 import { resolveStreamApprovalGate, type ApprovalFrameFamily } from "./tool-approval.js";
+import { type SyncBlobHistoryStore } from "./session-sync.js";
 import { type WorkspaceSyncCapability } from "./workspace-space.js";
 import type { WorkspaceCacheCapability } from "./workspace-cache.js";
 /** why 闭集:词 → 给运维看的一句义(诊断 / 测试读它;wire 上的拒句由各门自写)。 */
@@ -171,13 +172,8 @@ export declare function sessionSync(d: Pick<Deps, "backend" | "sessionStorage" |
     sessionStorage: SyncSessionStore;
     historyStore: ServiceFileHistoryStore;
 }>;
-/** blob 两面齐备的文件历史店(marker 门,不做名字探测:local 的引擎文件店带一只同名私有助手)。 */
-export type SyncBlobHistoryStore = ServiceFileHistoryStore & {
-    readonly syncBlobFaces: true;
-} & {
-    [P in "putBlob" | "getBlob"]-?: NonNullable<ServiceFileHistoryStore[P]>;
-};
-/** 会话同步的**文件历史半族**:对话半族 ∧ 文件历史店有 blob 搬运面(只有 SQL 两只店有)。 */
+/** 会话同步的**文件历史半族**:对话半族 ∧ 文件历史店有 blob 搬运面(只有 SQL 两只店有)。「店有没有 blob 两面」只在 `syncBlobFacesOf` 判一次(marker 门,不做名字探测),
+ *  blob 取值口 `blobGetterOf` 读的是同一只 —— 本事实为真 ⟺ 取值口通到 `historyStore.getBlob`。 */
 export declare function sessionSyncFileHistory(d: Pick<Deps, "backend" | "sessionStorage" | "fileHistoryStore" | "sessionPolicyStore">): Fact<SessionSyncWhy | "sync_blob_faces_absent", {
     historyStore: SyncBlobHistoryStore;
 }>;

package/dist/capability-facts.js

@@ -4,7 +4,7 @@ import { DEPLOYMENT_SHAPE_PREDICATES } from "./deployment-shape.js";
 import { presentedApprovalFrameFamily, resolveStreamApprovalGate } from "./tool-approval.js";
 import { selfOrchestrationDenial } from "./task-workflow.js";
 import { centerEntitlementSourceWired } from "./runtime-caps-resolver.js";
-import { overwriteWipeIncapable } from "./session-sync.js";
+import { overwriteWipeIncapable, syncBlobFacesOf } from "./session-sync.js";
 import { WORKSPACE_PERSIST_DEFAULT, WORKSPACE_SNAPSHOT_KEEP_DEFAULT, workspaceSnapshotTimeoutOf } from "./workspace-space.js";
 import { headReadOf } from "./session-incarnation.js";
 export const CAPABILITY_FACT_WHY = {
@@ -172,10 +172,8 @@ export function sessionSyncFileHistory(d) {
     const sync = sessionSync(d);
     if (!sync.available)
         return sync;
-    const fs = sync.historyStore;
-    return fs.syncBlobFaces === true && typeof fs.putBlob === "function" && typeof fs.getBlob === "function"
-        ? yes({ historyStore: fs })
-        : no("sync_blob_faces_absent");
+    const faces = syncBlobFacesOf(sync.historyStore);
+    return faces !== undefined ? yes({ historyStore: faces }) : no("sync_blob_faces_absent");
 }
 export function checkpointPark(d) {
     return d.checkpointStore !== undefined ? yes({ checkpointStore: d.checkpointStore }) : no("checkpoint_store_absent");

package/dist/center-credential-renewer.js

@@ -3,7 +3,7 @@ import { closeSync, fchmodSync, fsyncSync, openSync, readdirSync, readFileSync,
 import { basename, dirname, join } from "node:path";
 import { WEB_ADMIN_ENV, WebAdminCredentialEnvelope, parseWebAdminCredentialFile } from "@sema-agent/settings-schema";
 import { ACCESS_TOKEN_TTL_SECONDS, OAuthErrorResponse, TokenGrantResponse } from "@sema-agent/settings-schema/api/auth";
-import { CENTER_PULL_TIMEOUT_MS, centerTokenRefresh } from "./web-admin-client/center-request.js";
+import { CENTER_PULL_TIMEOUT_MS, CenterRedirectRefusedError, centerTokenRefresh } from "./web-admin-client/center-request.js";
 export const CENTER_CREDENTIAL_RENEW_LEAD_KEY = "CENTER_CREDENTIAL_RENEW_LEAD_MS";
 export const CENTER_CREDENTIAL_RENEW_LEAD_DEFAULT_MS = 5 * 60_000;
 export const CENTER_CREDENTIAL_RENEW_LEAD_MIN_MS = CENTER_PULL_TIMEOUT_MS;
@@ -277,6 +277,10 @@ export function createCenterCredentialRenewer(deps) {
             res = await centerTokenRefresh(envelope.issuer, envelope.refreshToken, { timeoutMs: CENTER_PULL_TIMEOUT_MS, ...(deps.fetchImpl ? { fetchImpl: deps.fetchImpl } : {}) });
         }
         catch (err) {
+            if (err instanceof CenterRedirectRefusedError) {
+                judgeRefusal(usedDigest, "rejected", { status: err.status });
+                return;
+            }
             settleRetrying("center_unavailable", usedDigest, { error: err instanceof Error ? err.name : "fetch error" });
             return;
         }

package/dist/center-credential.d.ts

@@ -97,9 +97,6 @@ export type CenterCredentialSourceSpec = Exclude<WebAdminCredentialDeclaration,
  * 路径(之后 cwd 变了也读同一个文件 —— 纯契约不碰 `node:path`,这一步归读方)。
  */
 export declare function readCenterCredentialDeclaration(env?: Readonly<Record<string, string | undefined>>): WebAdminCredentialDeclaration;
-/** 拉取令牌形的身份 = worker(拉取令牌代表 worker,不是人)。种类判别与 formatVersion 1 LKG 的一次性迁移
- *  (`config-lkg.ts` `migrateV1Lkg`:v1 信封只记 worker,只有这一形的身份推得出来)共用这一只。 */
-export declare function pullTokenIdentity(worker: string | undefined): string;
 /**
  * 凭证来源工厂(活对象:文件形每次取值读盘并记健康态)。`worker` = `SEMA_WEB_ADMIN_WORKER`(拉取令牌形的身份)。
  * `readFile` / `now` 只为测试注入。
@@ -161,6 +158,23 @@ export declare function answerStillCurrent(source: CenterCredentialSource, usedI
  *    中心答复;缓存 / 在飞 / 条件请求的校验子全在箱里,换了人结构上够不着上一个人的。
  *  · 请求发出之后才换人:答复到达时由 {@link answerStillCurrent} 判丢弃(请求装配侧,见 http-client.ts)。
  * 旧身份的箱不淘汰(量级 = 进程生命期内出现过的身份数):换回来的身份在 TTL 内照常命中它自己的缓存。
+ * 取箱口两只({@link IdentityBins}):`now`(此刻身份)与 `accounting`(记账身份:执行开始时钉下的那个,[ref])。
  */
-export declare function createIdentityBins<T>(source: CenterCredentialSource, make: (pinned: CenterCredentialSource) => T): () => T;
+export declare function createIdentityBins<T>(source: CenterCredentialSource, make: (pinned: CenterCredentialSource) => T): IdentityBins<T>;
+/**
+ * 同一只分箱规则的两个取箱口(箱表、钉住的凭证、惰建都只有一份):
+ *  · `now` —— 此刻凭证身份的箱(缓存 / 在飞去重 / 用量环上报这一类「此刻是谁就替谁办」的读者);
+ *  · `accounting` —— **记账身份**的箱([ref]:花费扣减、用量记账):这次执行开始时钉下的身份({@link pinAccountingIdentity});不在执行里 / 没钉 ⇒ 同 `now`。
+ *    在飞调用完成时凭证换了人或暂时读不到,都不改它记在谁的箱里。
+ */
+export interface IdentityBins<T> {
+    now(): T;
+    accounting(): T;
+}
+/**
+ * [ref] —— 把这次执行的**记账身份**钉在此刻(执行的第一帧 `task.start` 由 tracer 调;每个凭证来源每次执行至多钉一次,先到为准 ——
+ * 同一执行里子任务的 `task.start` 不改它)。此刻身份未知(凭证读不到)⇒ **不钉**:不把这次执行记到「身份未知」的无主箱,它的记账按记账那一刻的身份。
+ * 不在执行作用域里(`withPrincipal` 之外)⇒ 无动作。
+ */
+export declare function pinAccountingIdentity(source: CenterCredentialSource): void;
 //# sourceMappingURL=center-credential.d.ts.map

package/dist/center-credential.js

@@ -2,6 +2,7 @@ import { readFileSync } from "node:fs";
 import { createHash } from "node:crypto";
 import { resolve as resolvePath } from "node:path";
 import { looksLikeJwt } from "@sema-agent/settings-schema/api/auth-bridge";
+import { currentExecutionPins } from "./observability/principal-context.js";
 import { WEB_ADMIN_ENV, judgeWebAdminCredentialDeclaration, parseWebAdminCredentialFile } from "@sema-agent/settings-schema";
 export class CenterCredentialUnavailableError extends Error {
     reason;
@@ -37,7 +38,7 @@ function classify(bearer, worker) {
         return { ok: true, kind: "user-jwt", bearer, identity: userTokenIdentity(bearer) };
     return { ok: true, kind: "pull-token", bearer, identity: pullTokenIdentity(worker), workerScoped: bearer.startsWith("wpt_") };
 }
-export function pullTokenIdentity(worker) {
+function pullTokenIdentity(worker) {
     return `pull-token:${worker ?? "global"}`;
 }
 const NONE = { ok: true, kind: "none", identity: "none" };
@@ -178,14 +179,28 @@ export function answerStillCurrent(source, usedIdentity) {
 }
 export function createIdentityBins(source, make) {
     const bins = new Map();
-    return () => {
-        const identity = credentialIdentityNow(source);
+    const binOf = (identity) => {
         if (bins.has(identity))
             return bins.get(identity);
         const made = make(pinCredential(source, identity));
         bins.set(identity, made);
         return made;
     };
+    return {
+        now: () => binOf(credentialIdentityNow(source)),
+        accounting: () => binOf(accountingIdentityOf(source)),
+    };
+}
+export function pinAccountingIdentity(source) {
+    const pins = currentExecutionPins();
+    if (pins === undefined || pins.has(source))
+        return;
+    const identity = credentialIdentityNow(source);
+    if (identity !== undefined)
+        pins.set(source, identity);
+}
+function accountingIdentityOf(source) {
+    return currentExecutionPins()?.get(source) ?? credentialIdentityNow(source);
 }
 function pinCredential(source, identity) {
     return {

package/dist/checkpoint-ctx-seal-m28.d.ts

@@ -12,16 +12,9 @@
  * 本条在起服第 6 段 checkpoint 店建成、封签器的装配判(`CHECKPOINT_CTX_SEALING_REQUIRED`)过了之后调一次,早于任何路由装配(与 M10 / M19 / M25
  * 同为在迁移段之外跑的条目)。读数一行 info `checkpoint_ctx_credentials_sealed`,不进 `OneTimeMigrationReport`(登记行 `reportKeys` 空)。
  */
-import { type CheckpointCtxSealer, type SealedCheckpointCtx } from "./http/checkpoint-ctx.js";
+import { type CheckpointCtxSealer } from "./http/checkpoint-ctx.js";
 import { type OneTimeMigrationWindow } from "./plugins/one-time-migrations.js";
-import type { CtxRowsRewriteM28 } from "./plugins/checkpoint-store-sql.js";
-/** 两孪生的店腿(`SqlCheckpointStore` / `LocalCheckpointStore` 的 `rewriteCtxRowsM28`)。 */
-export interface CheckpointCtxRowsRewriterM28 {
-    rewriteCtxRowsM28(rewrite: (sessionId: string, ctx: object) => {
-        readonly ctx: SealedCheckpointCtx;
-        readonly values: number;
-    } | undefined): Promise<CtxRowsRewriteM28>;
-}
+import type { CheckpointCtxRowsRewriter } from "./plugins/checkpoint-store-sql.js";
 /** M28 一次起服的读数(起服 info 行逐键打出;测试按它断言)。`window: "closed"` ⇒ 一行都没读(其余全 0)。 */
 export interface CheckpointCtxSealM28Report {
     readonly window: "open" | "closed";
@@ -35,7 +28,7 @@ export interface CheckpointCtxSealM28Report {
  * 跑一次 M28(`today` = UTC 日历日 YYYY-MM-DD;`window` 缺省 = 登记表 M28 那一行 —— 只有测试递别的窗)。窗关 ⇒ 不扫。
  * 店腿的每一行:`sealStoredCheckpointCtxM28` 交回新体(凭据位上的明文封好)⇒ 回写;交回 `undefined`(没有明文)⇒ 不写。
  */
-export declare function sealCheckpointCtxCredentialsM28(store: CheckpointCtxRowsRewriterM28, sealer: CheckpointCtxSealer, opts: {
+export declare function sealCheckpointCtxCredentialsM28(store: CheckpointCtxRowsRewriter, sealer: CheckpointCtxSealer, opts: {
     readonly today: string;
     readonly window?: Pick<OneTimeMigrationWindow, "removableAfter">;
 }): Promise<CheckpointCtxSealM28Report>;

package/dist/checkpoint-ctx-seal-m28.js

@@ -10,7 +10,7 @@ export async function sealCheckpointCtxCredentialsM28(store, sealer, opts) {
     if (!migrationWindowOpen(opts.window ?? m28Window(), opts.today)) {
         return { window: "closed", rowsScanned: 0, rowsSealed: 0, valuesSealed: 0, rowsUnreadable: 0, rowsTooLarge: 0 };
     }
-    const r = await store.rewriteCtxRowsM28((sessionId, ctx) => {
+    const r = await store.rewriteCtxRows((sessionId, ctx) => {
         const out = sealStoredCheckpointCtxM28(ctx, sealer, sessionId);
         return out === undefined ? undefined : { ctx: out.ctx, values: out.valuesSealed };
     });

package/dist/checkpoint-identity.d.ts

@@ -7,13 +7,13 @@ export declare const MAX_CHECKPOINT_ID_CHARS = 128;
 export declare function withoutCheckpointToken(text: string, token: unknown): string;
 /** 持久层读出的 `checkpointId` 过信任边界:是串、非空、不超长、不含 token(大小写不敏感)⇒ 原值;否则 `undefined`。判据全文见本文件头注。 */
 export declare function trustedCheckpointId(raw: unknown, token: unknown): string | undefined;
-/** 带 `checkpointId` 当 join 键的两类 durable 读面(计数 detail 的 `face`)。 */
-export type DurableCheckpointFace = "approvals-queue" | "assistant-inbox";
+/** 带 `checkpointId` 当 join 键的 durable 面(计数 detail 的 `face`):运维队列行、停驻收件行,与 7.137.0 起的 park 账本行(`GET /v1/runs/:id/events` 的 `suspended` / `needs_review`,写时判一次)。 */
+export type DurableCheckpointFace = "approvals-queue" | "assistant-inbox" | "run-events-park";
 /**
  * durable 读面的一行 → 它的身份片段,**由调用方原样展开进行投影**(`...durableRowIdentity(face, raw, token)`):读得出可信值 ⇒ `{ checkpointId }`;
  * 读不出 ⇒ `{}`(这一行**照列**,键缺席)+ 计一次(见本文件头注「durable 面的 join 键」)。
  * `raw === undefined` = 行上没有这一格(`why=absent`,老行);在场却没过信任边界(非串 / 空串 / 超长 / 含 token / 读不出)= `why=untrusted`。
- * 三处读面(两只店的 `listPending` + 收件 handler)只经这一只 —— 读法、计数、缺席形各只有一份。
+ * 三处读面(两只店的 `listPending` + 收件 handler)与 park 账本行的唯一构造器(`trace/project.ts` 的 `parkEventData`)只经这一只 —— 读法、计数、缺席形各只有一份。
  */
 export declare function durableRowIdentity(face: DurableCheckpointFace, raw: unknown, token: unknown): {
     readonly checkpointId?: string;