@sema-agent/server 7.52.0 → 7.53.0

package/dist/memory-origin-fence.js

@@ -1,9 +1,28 @@
+import { createHash } from "node:crypto";
+import { committedOriginOf } from "@sema-agent/core";
+import { canonicalJson } from "./canonical-json.js";
 export const ORIGIN_AWARE_QUERY = "originAware";
 export function readOriginAware(params) {
     return params.get(ORIGIN_AWARE_QUERY) === "1";
 }
 export function isOriginTagged(entry) {
-    return typeof entry === "object" && entry !== null && Object.prototype.hasOwnProperty.call(entry, "origin") && entry.origin !== undefined;
+    if (typeof entry !== "object" || entry === null)
+        return false;
+    if (Object.prototype.hasOwnProperty.call(entry, "origin") && entry.origin !== undefined)
+        return true;
+    const fm = entry.frontmatter;
+    if (typeof fm !== "object" || fm === null)
+        return false;
+    if (Object.prototype.hasOwnProperty.call(fm, "origin") && fm.origin !== undefined)
+        return true;
+    const extra = fm.extra;
+    if (extra === undefined)
+        return false;
+    if (!Array.isArray(extra))
+        return true;
+    if (!extra.every((l) => typeof l === "string"))
+        return true;
+    return committedOriginOf({ extra }) !== undefined;
 }
 export function buildOriginFence(entries, originAware) {
     if (originAware)
@@ -12,4 +31,25 @@ export function buildOriginFence(entries, originAware) {
     const withheld = entries.length - kept.length;
     return withheld > 0 ? { entries: kept, withheldOriginTagged: withheld } : { entries: kept };
 }
+function sha256Line(text) {
+    return createHash("sha256").update(`${text}\n`, "utf8").digest("hex");
+}
+export function buildOriginFencedBundle(bundle, originAware) {
+    if (originAware)
+        return bundle;
+    const kept = bundle.entries.filter((e) => !isOriginTagged(e));
+    const withheld = bundle.entries.length - kept.length;
+    if (withheld === 0)
+        return bundle;
+    return {
+        ...bundle,
+        entries: kept,
+        integrity: {
+            entryCount: kept.length,
+            revs: Object.fromEntries(kept.map((e) => [e.id, e.rev])),
+            sectionHashes: { ...bundle.integrity.sectionHashes, entries: sha256Line(canonicalJson(kept)) },
+        },
+        withheldOriginTagged: withheld,
+    };
+}
 //# sourceMappingURL=memory-origin-fence.js.map

package/dist/memory-posture.d.ts

@@ -1,5 +1,5 @@
 /**
- * #252 件2/件3 —— 记忆面**姿态**的单一推导点。
+ * [ref] 件2/件3 —— 记忆面**姿态**的单一推导点。
  *
  * ## 病
  *
@@ -16,7 +16,7 @@
  *
  * ## 两条诚实纪律
  *
- * ① **档位取实例真值,不按后端推断**([3590] 裁①/[3606]①的延续):`vectorMode` 是「后端上限 × embedder
+ * ① **档位取实例真值,不按后端推断**([ref] 裁①/[ref]①的延续):`vectorMode` 是「后端上限 × embedder
  *    在场」的推断结果,两支 SQL 后端各自的实例 getter 才是真值;file 引擎**根本没有**这个指示面
  *    (core 的 `MemoryBackend` 契约里没有 `vectorMode`,亲验),所以它报 `null` —— 「没有这个指示面」与
  *    「档位是词面」是两件事,折成一件就是编一个数出来。
@@ -51,20 +51,20 @@ export interface MemoryPosture {
         dimensions: number;
     } | null;
     /**
-     * #299(core 5.45.0 design/324):本部署给委派臂设的**证据标准**(`MEMORY_DELEGATION_EVIDENCE`)。
+     * [ref](core 5.45.0 [ref]):本部署给委派臂设的**证据标准**(`MEMORY_DELEGATION_EVIDENCE`)。
      *
      * 🔴 `null` = **本部署没设这个键** ⇒ 引擎按它自己的缺省跑。**不是**「等于 static-face」—— 那句话是
      *    关于 core 缺省的知识声明,本读面不替 core 宣布它(`vectorMode: null` 同一条诚实纪律:
      *    「没有这个指示面」与「档位是词面」是两件事)。运维要知道「实际生效的是哪一档」,读这一位 +
      *    实装 core 的契约,两件事分开摆。
      *
-     * 受众 = **operator 面独占**:与 `darkReason`/`multiTenant`/embedder 身份同判(#252 件3 的分界),
+     * 受众 = **operator 面独占**:与 `darkReason`/`multiTenant`/embedder 身份同判([ref] 件3 的分界),
      * 刻意**不**进 `GET /v1/capabilities` 的窄投影 —— 证据标准回答的是「这台机器怎么判污染」,是运维
      * 诊断料,不是任何持凭证调用方该读的位。
      */
     delegationEvidence: "static-face" | "attested-only" | null;
     /**
-     * #307 件4(core 5.46.0 design/336 §13-3):本部署的 **provenance 姿态**(`MEMORY_PROVENANCE`)——
+     * [ref] 件4(core 5.46.0 [ref] §13-3):本部署的 **provenance 姿态**(`MEMORY_PROVENANCE`)——
      * 一个会话被判为已暴露之后,它的记忆写是**带标收录**(`carry`)还是**整体隔离**(`off`)。
      *
      * 🔴 `null` = **本部署没设这个键** ⇒ 引擎按它自己的缺省跑。**不是**「等于 carry」——
@@ -75,7 +75,7 @@ export interface MemoryPosture {
      */
     provenance: "off" | "carry" | null;
     /**
-     * design/383 §3.1(core 7.0.0 片3,S-49 S-1b):本部署的 **capture 姿态**(`MEMORY_CAPTURE_POLICY`)——
+     * [ref] §3.1(core 7.0.0 片3,[ref] S-1b):本部署的 **capture 姿态**(`MEMORY_CAPTURE_POLICY`)——
      * per-principal `allowMemoryOptOut` verdict 被读进的那个框(`open` fail-safe / `governed` fail-closed /
      * `capture-required` 全拒)。
      *

package/dist/memory-scope.d.ts

@@ -11,7 +11,7 @@ export declare const V2_SCOPE_PREFIXES: readonly string[];
  * 校验点 fail-loud。
  */
 export declare function isV2ScopeKey(key: string): boolean;
-/** Resolve the memory scope for a request (design/138 S1 — the file-based memory engine is the only plane).
+/** Resolve the memory scope for a request ([ref] S1 — the file-based memory engine is the only plane).
  *
  *  SINGLE-USER (REQUIRE_PRINCIPAL !== "true"): ONE shared scope — `config.memoryScope` (default "local"),
  *  regardless of any principal label the caller self-reports (a single-user worker's `anon:*` / ad-hoc
@@ -26,12 +26,12 @@ export declare function isV2ScopeKey(key: string): boolean;
  *  security.ts 把身份轴守住了,但 `formatUserScope`/`formatProjScope` 的段编码(百分号转义)会
  *  **膨胀**——非 ASCII principal 编码后可超列宽,此前落裸 SQL 错。产出处响亮拒,错误可分类。
  *
- *  #271 件1:定义**搬去** `plugins/memory-key-guards.ts`(列宽与 store 写口同源单一属主),此处
+ *  [ref] 件1:定义**搬去** `plugins/memory-key-guards.ts`(列宽与 store 写口同源单一属主),此处
  *  只再导出——旧 import 路径(本文件)逐字不变,`memoryScopeFor` 的产出处消费点也不变。 */
 export { MEMORY_SCOPE_COLUMN_CHARS, assertMemoryScopeWidth } from "./plugins/memory-key-guards.js";
 export declare function memoryScopeFor(config: ServiceConfig, principal?: string, projectId?: string): string | undefined;
 /**
- * N0 (通宵测试 2026-07-09,三重坐实 e2b+kata+代码): the file memory engine (core design/138) materializes and
+ * N0 (通宵测试 2026-07-09,三重坐实 e2b+kata+代码): the file memory engine (core [ref]) materializes and
  * harvests via `node:fs` on the WORKER's local fs, while a remote exec lane routes the model's file tools to
  * the SANDBOX fs — the planes never meet: materialized memory is invisible inside the sandbox (the injected
  * instructions burn failing Write turns) and sandbox writes are never harvested (add=0). Until core defines
@@ -67,7 +67,7 @@ engineWired: boolean): {
     effect: string;
 } | undefined;
 /**
- * design/138 S1 wiring gate (pure — unit-testable without booting main): build the file-based memory-engine
+ * [ref] S1 wiring gate (pure — unit-testable without booting main): build the file-based memory-engine
  * backend for this deployment, or `undefined` when memory must stay dark.
  *
  *  - SINGLE-USER TURNKEY ONLY (`requirePrincipal !== true`): the engine's file basement
@@ -91,13 +91,13 @@ export declare function memoryEngineBackendFor(config: ServiceConfig, fallbackRo
 /**
  * MF-30 memory PAUSE (option B, per-request — clay 2026-06-27): build the `TaskSpec.memory` spec for ONE run from
  * the resolved memory `scope` + the request's `memoryWrite` toggle. `memoryWrite === false` ⇒ `writeScope: null`
- * (design/138 engine read-only: normalizeMemorySpec's writeScope:null — materialize/read still works, harvest
+ * ([ref] engine read-only: normalizeMemorySpec's writeScope:null — materialize/read still works, harvest
  * commits nothing). Absent/true ⇒ normal read+write. No scope (engine off / multi-tenant dark) ⇒ undefined
  * (memory feature off for this run). Pure (testable in isolation) — main.ts's resolveSpec composes it with the
  * engine-backend presence guard.
  */
 export declare function memorySpecForRequest(scope: string | undefined, memoryWrite: boolean | undefined, defaultScopes?: string[], 
-/** design/170 件A(#148 件3④):origin 盖章的部署形态维(N2)。`multiTenant=true`(requirePrincipal)
+/** [ref] 件A([ref] 件3④):origin 盖章的部署形态维(N2)。`multiTenant=true`(requirePrincipal)
  *  ⇒ 登记簿 defaultScopes 的 org 键按 **request** 盖章(条目由调用方 projectId 选定=caller 可影响的
  *  选择器,core 准入门据此过目录判决);单用户 ⇒ 一律 deployment(operator 登记簿条目归 deployment,
  *  否则单用户部署被自家规则整拒——v4 §0 伤害①的成立前提)。缺参=旧调用形,不盖章(整键缺席=
@@ -105,7 +105,7 @@ export declare function memorySpecForRequest(scope: string | undefined, memoryWr
 originPolicy?: {
     multiTenant: boolean;
 }, 
-/** design/383 §2.1(S-49):请求的 `memoryCapture:"off"` 声明 ⇒ `TaskSpec.memory.capture:"off"`(单成员闭集,
+/** [ref] §2.1([ref]):请求的 `memoryCapture:"off"` 声明 ⇒ `TaskSpec.memory.capture:"off"`(单成员闭集,
  *  拼写门在 prepareSpec 的 400 门 + core 的 `config.memory_capture_spelling`)。缺席 ⇒ 键不铸(缺席就是照常采集
  *  的唯一形)。与 `memoryWrite` 正交:那是「本 run 只读平面」,这是「本会话永远不进长期记忆」。 */
 memoryCapture?: "off"): {

package/dist/model-select.d.ts

@@ -10,7 +10,7 @@
  * untrusted body/text can pick WHICH configured model but can never inject a baseUrl/apiKey (parseModelMention
  * only ever returns an allow-listed catalog name).
  *
- * [865]②(生产实锤:面板上选了 A 模型,实际跑的是目录里的另一个):
+ * [ref]②(生产实锤:面板上选了 A 模型,实际跑的是目录里的另一个):
  *  - explicit ref 走 name+id 双键索引({@link matchCatalogModel})——壳 boot 回读的 mainLoopModel 是 **id 形**,
  *    目录键是 **name 形**,单键索引把 id 形请求当「未知」静默落 default = session 中途静默换模型(最恶性的
  *    上下文污染路径)。
@@ -29,7 +29,7 @@ export declare function resolveTaskModel(bodyModel: unknown, objective: string,
     unknownExplicit?: string;
     notAllowed?: ModelNotAllowed;
 };
-/** #233 判别式拒因:名单在场且这次**用户选择**落在名单外。`resolved` 已是目录 name 形(归一后)。 */
+/** [ref] 判别式拒因:名单在场且这次**用户选择**落在名单外。`resolved` 已是目录 name 形(归一后)。 */
 export interface ModelNotAllowed {
     /** 调用方发来的原始 ref(name / 档位词 / 别名 / id / `@name`),已做过日志安全的 repr 归一。 */
     requested: string;
@@ -39,7 +39,7 @@ export interface ModelNotAllowed {
     source: "explicit" | "mention";
 }
 /**
- * #233 / A-002.8 —— **归一条款**:membership 判定前把 ref 归一到**终端 catalog 条目**再比。
+ * [ref] / [ref] —— **归一条款**:membership 判定前把 ref 归一到**终端 catalog 条目**再比。
  *
  * 为什么不能拿字符串直接跟名单比:`expandTiers` 的增广目录里,档位词(`pro`)与 CC 别名(`sonnet`)
  * 的值与 `config.models[<name>]` 是**同一个对象引用**——裸串比较会让 `@pro` 跳过一张按 name 写的名单
@@ -62,7 +62,7 @@ export interface ModelNotAllowed {
  */
 export declare function isModelAllowlisted(ref: string, catalog: Record<string, unknown>, allowlist: readonly string[] | undefined): boolean;
 /**
- * #233 —— ref → **终端 catalog name**(拒因/日志的可读形)。
+ * [ref] —— ref → **终端 catalog name**(拒因/日志的可读形)。
  *
  * 为什么不是 `matchCatalogModel` 的返回值:增广目录里 `pro`/`opus`/`default` 都是**真实存在的键**,
  * 于是 `matchCatalogModel("pro")` 回的就是 `"pro"` —— 那是用户点的那个别名,不是他真会跑的模型。
@@ -71,7 +71,7 @@ export declare function isModelAllowlisted(ref: string, catalog: Record<string,
  */
 export declare function terminalCatalogName(ref: string, catalog: Record<string, unknown>): string | undefined;
 /**
- * [865]② name+id 双键目录索引:返回 ref 命中的目录 **name 键**(spec.model 的规范形),未知 → undefined。
+ * [ref]② name+id 双键目录索引:返回 ref 命中的目录 **name 键**(spec.model 的规范形),未知 → undefined。
  *  - name 命中用 Object.hasOwn(🔴 不用真值索引:Object.prototype 继承键 "constructor"/"__proto__" 等在裸
  *    索引下是真值,会跳过 allow-list——沿袭原实现的纪律)。
  *  - id 命中扫目录值(`Model.id`),跳过 "default" 别名键(它与其指向的真身共享 id,解析到别名会让 /model

package/dist/observability/cost-quota.d.ts

@@ -1,5 +1,5 @@
 /**
- * Per-principal CUMULATIVE cost quota (design/21/27 follow-up). The per-task `maxCostUsd` gate caps a
+ * Per-principal CUMULATIVE cost quota ([ref]/27 follow-up). The per-task `maxCostUsd` gate caps a
  * SINGLE task; this caps a principal's spend ACROSS tasks within a rolling fixed window. Spend is the
  * authoritative integer `costMicroUsd` accumulated by the tracer (so it includes council/team
  * sub-tasks, via the principal ALS context). A new task is REFUSED once the window's accumulated cost
@@ -19,8 +19,8 @@ export interface QuotaDecision {
 }
 /** The hot-path surface shared by the in-memory {@link CostQuota} (single replica) and the cross-replica
  *  {@link import("../plugins/tidb-cost-quota.js").TiDBCostQuota}. `key` is opaque (principal today;
- *  principal/team/feature later — design/30 N3), so both stores are key-based. */
-/** #322 批1:配额的**值换代**入参(四实现类同一形;单位与构造参数一致 —— USD/秒 → micro/ms 的换算
+ *  principal/team/feature later — [ref] N3), so both stores are key-based. */
+/** [ref] 批1:配额的**值换代**入参(四实现类同一形;单位与构造参数一致 —— USD/秒 → micro/ms 的换算
  *  只有一处,`boot/limit-sync.ts` 的 `buildQuotaBounds`)。`limitMicroUsd <= 0` = **关断哨兵**。 */
 export interface QuotaLimits {
     limitMicroUsd: number;
@@ -29,20 +29,20 @@ export interface QuotaLimits {
 export interface QuotaTracker {
     check(key: string): QuotaDecision;
     add(key: string, micro: number): void;
-    /** #322:值换代座位。**接口级**声明——新实现漏掉它 = 编译红,而不是热更新在那条腿上静默失效。 */
+    /** [ref]:值换代座位。**接口级**声明——新实现漏掉它 = 编译红,而不是热更新在那条腿上静默失效。 */
     setLimits(next: QuotaLimits): void;
 }
 export declare class CostQuota implements QuotaTracker {
     private readonly now;
     private windows;
-    /** 🔴 不再 `readonly`:限额/窗长是比较参数,换代只动它们,窗内已累计的花费一个不动(design/322 §5)。 */
+    /** 🔴 不再 `readonly`:限额/窗长是比较参数,换代只动它们,窗内已累计的花费一个不动([ref] §5)。 */
     private limitMicroUsd;
     private windowMs;
     /** @param limitMicroUsd ceiling per window (integer micro-USD; `<=0` = OFF sentinel). @param windowMs rolling window. */
     constructor(limitMicroUsd: number, windowMs: number, now?: () => number);
     /**
      * 值换代。两件事**语义不同**,别混:
-     *  · **限额**换代 = 纯比较参数 ⇒ 窗内已累计的花费一个不动(design/322 §5 定案:调小当场更严)。
+     *  · **限额**换代 = 纯比较参数 ⇒ 窗内已累计的花费一个不动([ref] §5 定案:调小当场更严)。
      *  · **窗长**换代 = 换**记账周期** ⇒ 当代累计重开。
      *
      * 🔴 后者是 codex R1-F4(真 finding,红先):SQL 腿的窗长是**桶键的一部分**(`floor(now/windowMs)`),

package/dist/observability/cost-taxonomy.d.ts

@@ -1,8 +1,8 @@
 /**
- * design/80 b (item 3) — the INFRA cost axes the SERVICE owns, composed with core's LLM-family `costBreakdown`
+ * [ref] b (item 3) — the INFRA cost axes the SERVICE owns, composed with core's LLM-family `costBreakdown`
  * for the supervisor cost surface.
  *
- * (design/158 N24: moved here from the single-file `src/finance/` directory — lens4 §4.4 flagged the "cost"
+ * ([ref] N24: moved here from the single-file `src/finance/` directory — lens4 §4.4 flagged the "cost"
  * concept as split across `finance/cost-taxonomy.ts` + `observability/cost-quota.ts` + `budget.ts`. Chose
  * "dissolve finance/, fold into observability/" over "collect all three into finance/": this module + the
  * quota tracker are both cost REPORT/GUARD layers that feed metrics/decisions (observability's existing

package/dist/observability/fail-open.d.ts

@@ -81,10 +81,6 @@ export declare const FAIL_OPEN_TAGS: {
         readonly cls: "P-DEBT";
         readonly note: "跨副本赎回 parked 审批时,祖先层在 park 时是 **auto-mode 武装**的,但那只分类器是祖先任务上的活闭包(绑着它自己的转写窗+brain),跨进程重建不出来 ⇒ 本仓交一只如实拒答的 decider,core 收到 `unavailable` 后**不产生任何自动裁决**、原样落到祖先冻结审批席那条链(本腿的席位又是无 ALS 的降级形 ⇒ 再 park 给人)。方向:分类器本会 allow 的改成问人(更严),本会 block 的也改成问人(**不是自动放行**,但比自动拒松一档)⇒ 记债不当合法兜底。计数 = 「丢了祖先分类器判决的继承 ask」次数。收口件二选一:core 把分类器判据持久进链条目,或让祖先 decider 有可跨进程重建的形。";
     };
-    readonly "server.hitl.row-derived-approve-drops-updated-input": {
-        readonly cls: "P-DEBT";
-        readonly note: "A-054.15:一条**持久 ask 行**上的 `DECIDED=approve` 被回放成裸 `true` 交给 core —— 而人当时可能是带 **ctrl+g 编辑**批的(`updatedInput`)。持久层没有该列(`AskRow`/`DecideAskInput` 皆无),行读不出「这次批准是否改写过实参」,于是 core 的 `d.updatedInput === undefined` 分支落回**原始未改写**实参执行:人批的是改写后的命令,真跑的是原命令 —— 一次**执行面宽于人所批准**的扩权,方向错的一侧,故记债不当合法兜底。四个同形站点全部计在本 tag 下(只在真把 `true` 交出去时计,不在读到行时计):`replayTerminalAskRow` 的三个消费点(`ensureAsk` 幂等回放 / `convergeFromDurableState` / 店报错臂的 `readDecidedForRecovery`)与 `runs.ts` 的 `syncLiveFromDecidedRow`(settled>0 才算)。⚠️ 计数是**上限**不是实数:分不出这次 approve 原本带没带编辑(能分出来就不用记债了),真丢的是其中带编辑的那一部分。补偿:回体在这条路上**省略** `updatedInputForwarded`(从不发 false = 成文的否定信号)。终局收口 = 给 ask 行加 `updated_input` 列(店语义级,须本模块属主立件),届时本 tag 同批销。";
-    };
     readonly "server.e2b.orphan-skip-unknown": {
         readonly cls: "F";
         readonly note: "#242 E2B 孤儿回收对一只沙盒**判不了属主/活性**(metadata 缺 taskId 的病态形 / run 行状态词在 LIVE 与 TERMINAL 两表之外 / getRun 抛错)⇒ 恒不杀,本轮跳过。方向纪律:回收是清理型能力,缺席判据=不动作——误杀是杀活任务的手,漏杀只是钱;但每次跳过必须计数,否则「回收在跑却总有几只杀不掉」的病灶(店故障/新状态词未收编/别家部署共用 key)永不显形。";
@@ -163,7 +159,7 @@ export type FailOpenTag = keyof typeof FAIL_OPEN_TAGS;
  * 断连会让保护型计数涨两次(open 一次、complete 又一次),真正的 open 失败率被面包屑的假阳性盖住。
  * 只有 open 帧是"人在环这道门被跳过"的证据,其余都是体验损失。
  *
- * ⚠️ **两条 question 臂在生产上已不可达**(#173 之后,2026-08-07):本函数唯一的生产调用点是
+ * ⚠️ **两条 question 臂在生产上已不可达**([ref] 之后,2026-08-07):本函数唯一的生产调用点是
  * `routes/tasks.ts` 的 `emitAsk` 断流臂,而 question 与 question_complete 两型帧都先过同文件
  * `emitQuestion` 的断流守卫(两道守卫同步相邻、其间无 await)并在断流时 throw,永不抵达这里;另一条
  * question 路(`runs.ts` 的 durable append)根本不经 emitAsk。在产的只剩 elicitation 族与 default。

package/dist/observability/fail-open.js

@@ -72,10 +72,6 @@ export const FAIL_OPEN_TAGS = {
         cls: "P-DEBT",
         note: "跨副本赎回 parked 审批时,祖先层在 park 时是 **auto-mode 武装**的,但那只分类器是祖先任务上的活闭包(绑着它自己的转写窗+brain),跨进程重建不出来 ⇒ 本仓交一只如实拒答的 decider,core 收到 `unavailable` 后**不产生任何自动裁决**、原样落到祖先冻结审批席那条链(本腿的席位又是无 ALS 的降级形 ⇒ 再 park 给人)。方向:分类器本会 allow 的改成问人(更严),本会 block 的也改成问人(**不是自动放行**,但比自动拒松一档)⇒ 记债不当合法兜底。计数 = 「丢了祖先分类器判决的继承 ask」次数。收口件二选一:core 把分类器判据持久进链条目,或让祖先 decider 有可跨进程重建的形。",
     },
-    "server.hitl.row-derived-approve-drops-updated-input": {
-        cls: "P-DEBT",
-        note: "A-054.15:一条**持久 ask 行**上的 `DECIDED=approve` 被回放成裸 `true` 交给 core —— 而人当时可能是带 **ctrl+g 编辑**批的(`updatedInput`)。持久层没有该列(`AskRow`/`DecideAskInput` 皆无),行读不出「这次批准是否改写过实参」,于是 core 的 `d.updatedInput === undefined` 分支落回**原始未改写**实参执行:人批的是改写后的命令,真跑的是原命令 —— 一次**执行面宽于人所批准**的扩权,方向错的一侧,故记债不当合法兜底。四个同形站点全部计在本 tag 下(只在真把 `true` 交出去时计,不在读到行时计):`replayTerminalAskRow` 的三个消费点(`ensureAsk` 幂等回放 / `convergeFromDurableState` / 店报错臂的 `readDecidedForRecovery`)与 `runs.ts` 的 `syncLiveFromDecidedRow`(settled>0 才算)。⚠️ 计数是**上限**不是实数:分不出这次 approve 原本带没带编辑(能分出来就不用记债了),真丢的是其中带编辑的那一部分。补偿:回体在这条路上**省略** `updatedInputForwarded`(从不发 false = 成文的否定信号)。终局收口 = 给 ask 行加 `updated_input` 列(店语义级,须本模块属主立件),届时本 tag 同批销。",
-    },
     "server.e2b.orphan-skip-unknown": {
         cls: "F",
         note: "#242 E2B 孤儿回收对一只沙盒**判不了属主/活性**(metadata 缺 taskId 的病态形 / run 行状态词在 LIVE 与 TERMINAL 两表之外 / getRun 抛错)⇒ 恒不杀,本轮跳过。方向纪律:回收是清理型能力,缺席判据=不动作——误杀是杀活任务的手,漏杀只是钱;但每次跳过必须计数,否则「回收在跑却总有几只杀不掉」的病灶(店故障/新状态词未收编/别家部署共用 key)永不显形。",

package/dist/observability/metrics.d.ts

@@ -18,7 +18,7 @@ export declare class Metrics {
     setGauge(name: string, value: number, labels?: Labels): void;
     addGauge(name: string, delta: number, labels?: Labels): void;
     observe(name: string, value: number, labels?: Labels): void;
-    /** [2557] 2-j:dynamic gauge 求值抛错不再折成 0 —— 0 是该 gauge 的合法读数,折 0 让故障态与真实 0
+    /** [ref] 2-j:dynamic gauge 求值抛错不再折成 0 —— 0 是该 gauge 的合法读数,折 0 让故障态与真实 0
      *  在 wire 上逐字节不可区分(与上方 inc 静默 no-op 同族:观测面的 fail-silent 正是观测要消灭的东西)。
      *  披露方向:错帧**不发样本行**(缺席=读数未知,面板显示 no data 而非假 0)+ 计
      *  `metric_gauge_eval_errors_total{name}`(响亮、可告警)。每次求值(每次刮取/snapshot)错一次计一次;

package/dist/observability/prompt-manifest.d.ts

@@ -1,4 +1,4 @@
-/** The whitelisted projection of core's `prompt.assembled` trace event ([998]② web observability slice A:
+/** The whitelisted projection of core's `prompt.assembled` trace event ([ref]② web observability slice A:
  *  the manifest reaches the durable run event log + turns/stream). Built FIELD-BY-FIELD at record time
  *  (never a spread — the 1.72 task_progress lesson: a future core field must not ride the durable wire raw).
  *  Carries ONLY ids/digests/counts by core's manifest contract (no prompt bodies; hashes are core-salted) —
@@ -10,7 +10,7 @@ export interface PromptManifestRecord {
         chars: number;
         hash: string;
     }>;
-    /** `contentHash`(core 1.315 [1062]①):operator 声明 section 的**非盐化**对账锚(core 已对 text 校验
+    /** `contentHash`(core 1.315 [ref]①):operator 声明 section 的**非盐化**对账锚(core 已对 text 校验
      *  后透传)——盐化 `hash` 恒在旁;端到端对账链(center 发布→manifest)经本投影,必须透传不可吞。 */
     sections?: Array<{
         id: string;
@@ -31,7 +31,7 @@ export interface PromptManifestRecord {
         shapeDigest: string;
         wireSchemaDigest: string;
     }>;
-    /** core 5.15.0(#181):deferred 披露策略自证三键(诊断值,零内容)。缺席=core <5.15 或无 deferred。 */
+    /** core 5.15.0([ref]):deferred 披露策略自证三键(诊断值,零内容)。缺席=core <5.15 或无 deferred。 */
     toolDisclosure?: {
         deferredTools: number;
         strategy: string;
@@ -67,7 +67,7 @@ export declare function promptManifestRecordOf(e: {
         shapeDigest: string;
         wireSchemaDigest: string;
     }>;
-    /** core 5.15.0(#181,[2872] 提货②):deferred 工具的披露策略自证——{deferredTools(数), strategy
+    /** core 5.15.0([ref],[ref] 提货②):deferred 工具的披露策略自证——{deferredTools(数), strategy
      *  ("static"|"swap"), source(四值:`spec` / `env` / `default` / `degraded_no_direct_lane`)}。
      *  诊断三键(数 + 两闭集词,零内容)。词表属主是 core(`core/trace.d.ts` 的 `source` 联合),本仓宽收
      *  ⇒ 词错不会红,所以照抄时务必对表:`degraded_no_direct_lane` = 直呼车道联锁把 `static` 请求收窄成
@@ -81,7 +81,7 @@ export declare function promptManifestRecordOf(e: {
     totalChars: number;
 }): PromptManifestRecord;
 /**
- * [998]② per-task prompt-manifest accumulator — the `ModelUsageTracker`(budget.ts)pattern: the
+ * [ref]② per-task prompt-manifest accumulator — the `ModelUsageTracker`(budget.ts)pattern: the
  * `prompt.assembled` tracer hook is SYNC/no-IO, so it cannot persist; it RECORDS here (registered
  * top-level runs only — the same leak fence: sub-task manifests are never registered, never leak), and
  * the durable run lifecycle DRAINS the pending records into `prompt_assembled` events. Two departures
@@ -95,7 +95,7 @@ export declare function promptManifestRecordOf(e: {
  *    delete the NEW leg's registration/pending manifest. Identity-guarded like the sibling
  *    inflight/steerable teardowns.
  */
-/** [1301]③ — `config.assembled` 的白名单投影(core 1.346 trace:catalogVersion/fields[来源标注]/
+/** [ref]③ — `config.assembled` 的白名单投影(core 1.346 trace:catalogVersion/fields[来源标注]/
  *  overrideReasons)。fields 已是 core 精选的观测形(digest-free、有界);32KiB 罩防未来膨胀。 */
 export declare function configAssembledRecordOf(e: {
     catalogVersion?: unknown;
@@ -105,7 +105,7 @@ export declare function configAssembledRecordOf(e: {
 }): Record<string, unknown> | undefined;
 export declare class PromptManifestTracker {
     private readonly byTask;
-    /** [1301]③:config.assembled 的同生命周期伴随记录(register 同门、drainConfig 同拍)。队列形
+    /** [ref]③:config.assembled 的同生命周期伴随记录(register 同门、drainConfig 同拍)。队列形
      *  (codex F2):cascade 每 rung 独立解析配置,后到覆盖会把先前已计费 rung 的生效配置抹掉——与
      *  prompt manifests 同姿势逐条保序。 */
     private readonly configByTask;
@@ -116,7 +116,7 @@ export declare class PromptManifestTracker {
     register(taskId: string): number;
     /** Queue this prepare's manifest — ONLY for a registered top-level run (else a no-op). Sync, never throws. */
     record(taskId: string, m: PromptManifestRecord): void;
-    /** [1301]③:队一条 config.assembled 投影(同 register 门;逐条保序——cascade 每 rung 各留其形)。 */
+    /** [ref]③:队一条 config.assembled 投影(同 register 门;逐条保序——cascade 每 rung 各留其形)。 */
     recordConfig(taskId: string, rec: Record<string, unknown>): void;
     /** Return-and-clear ALL pending config records in emission order; `undefined` when none. */
     drainConfig(taskId: string): Array<Record<string, unknown>> | undefined;

package/dist/observability/rate-limit.d.ts

@@ -10,7 +10,7 @@ export interface RateDecision {
     retryAfterSec: number;
     remaining: number;
 }
-/** #322 批1:限额的**值换代**入参(六实现类同一形)。语义定案(design/322 §5):窗口内计数**不清零**,
+/** [ref] 批1:限额的**值换代**入参(六实现类同一形)。语义定案([ref] §5):窗口内计数**不清零**,
  *  新限额即时用于比较 —— 调小 = 窗内立刻更严(可能当场 429,符合运营意图),调大 = 立刻放宽。 */
 export interface RateLimits {
     /** 每窗请求上限;`<= 0` = **关断哨兵**(恒放行、不记账、SQL 腿不起刷新环)。 */
@@ -21,7 +21,7 @@ export interface RateLimits {
 export interface RateGate {
     check(key: string): RateDecision;
     sweep(now?: number): void;
-    /** #322:值换代座位。**接口级**声明(不是各类自选):新实现漏掉它 = 编译红,而不是热更新在那条腿上静默失效。 */
+    /** [ref]:值换代座位。**接口级**声明(不是各类自选):新实现漏掉它 = 编译红,而不是热更新在那条腿上静默失效。 */
     setLimits(next: RateLimits): void;
 }
 export declare class RateLimiter implements RateGate {

package/dist/observability/secret-env-scrub.d.ts

@@ -1,5 +1,5 @@
 /**
- * A-033.3(#256)—— **密钥形 env 剥除的留痕面**(core D1 `scrubSecretEnv` 的可观测半场)。
+ * [ref]([ref])—— **密钥形 env 剥除的留痕面**(core D1 `scrubSecretEnv` 的可观测半场)。
  *
  * ## 它解决的问题
  * `scrubSecretEnv` 是本仓两条 shell/子进程腿的**安全默认**:模型可驱动的 shell(`inheritEnv:"scrub"`)与

package/dist/observability/tool-trace.d.ts

@@ -16,7 +16,7 @@ export declare function isKnownDenySource(v: unknown): v is PermissionDeniedSour
  */
 export declare function createPermissionDeniedMeter(metrics: Pick<Metrics, "inc">): Hooks;
 /**
- * prove-before-scale stopgap (design/50): a no-op observer hook that logs every tool call (pre + post)
+ * prove-before-scale stopgap ([ref]): a no-op observer hook that logs every tool call (pre + post)
  * to the worker log — INCLUDING resumed legs that `GET /v1/runs/:id/events` does NOT surface (the
  * streaming-resume observability gap, service[15] API request #2). Gated by `TOOL_TRACE=true`; OFF by
  * default (no prod noise).

package/dist/orchestration/hardened-vm-runner.d.ts

@@ -40,7 +40,7 @@ import { type WorkflowScriptRunner, type WorkflowPrimitives } from "@sema-agent/
  *   timer nor the abort listener fires → it hangs the process. The worker-isolated runner (`terminate()`)
  *   pre-empts that — use it for genuinely-untrusted multi-tenant scripts where resource isolation matters.
  *
- * 🔴 Silent-hang class ([1818]§二, clay live incident 2026-07-26): a script whose promise graph can NEVER settle
+ * 🔴 Silent-hang class ([ref]§二, clay live incident 2026-07-26): a script whose promise graph can NEVER settle
  *   (an un-awaited `phase(...)` whose body returns its own promise) used to burn the full totalTimeoutMs blind
  *   and then blame the timeout. The quiescence detector in {@link runHardened} fail-fasts it with a diagnosis:
  *   inside the membrane the bridge is the ONLY async host seam, so bridge-quiescent + both queues drained +
@@ -62,20 +62,20 @@ export interface HardenedVmLimits {
      *  A script exceeding it OOMs the WORKER (killed), never the shared main process. Default 128. */
     maxHeapMb?: number;
 }
-/** [5434]①(clay 亲机四 run 三次恰在 600s 整点全灭):workflow 总超时默认与旋钮的**单点**。
+/** [ref]①(clay 亲机四 run 三次恰在 600s 整点全灭):workflow 总超时默认与旋钮的**单点**。
  *  旧默认 600_000(10 分钟)对真实 workflow(验证 agent 逐条重跑清单/任何带审批等待的车)结构性不够——
  *  默认抬到 **1 小时**;部署经 `WORKFLOW_TOTAL_TIMEOUT_MS` 显式配,域 [60_000, 86_400_000](1 分钟..24h),
- *  坏值**响亮拒**(#210 立律:旋钮坏值禁静默回默认)。0/负数不是「禁用」:无界 runaway 脚本会吞掉共享
+ *  坏值**响亮拒**([ref] 立律:旋钮坏值禁静默回默认)。0/负数不是「禁用」:无界 runaway 脚本会吞掉共享
  *  副本的事件循环/堆,禁用臂刻意不提供——要更久就把值配大。模块加载时读一次(坏 env = boot fail-loud)。
- *  超时终态分型(partial vs failed,[5434]① 后半)涉 wire status 语义,与 core workflow 终态形另批对表。 */
+ *  超时终态分型(partial vs failed,[ref]① 后半)涉 wire status 语义,与 core workflow 终态形另批对表。 */
 export declare function workflowTotalTimeoutMsDefault(): number;
 /**
  * The realm test itself, exported so there is exactly ONE ruler for "did this rejection come from an untrusted
  * script?" in the process. A promise minted INSIDE a vm context fails `instanceof` against the HOST `Promise`
  * (different intrinsic per realm) — that is the whole judgement.
  *
- * 🔴 Why it is exported (A-070 二轮重扫, lifecycle-pairing, double-opus CONFIRMED): the guard below is NOT the
- * only `unhandledRejection` listener in a real boot. `src/boot/shutdown.ts` installs one at boot (#320① crash
+ * 🔴 Why it is exported ([ref] 二轮重扫, lifecycle-pairing, double-opus CONFIRMED): the guard below is NOT the
+ * only `unhandledRejection` listener in a real boot. `src/boot/shutdown.ts` installs one at boot ([ref]① crash
  * last words) that exits(1); Node walks EVERY listener for the event, so containment cannot be expressed by
  * one listener returning early — whoever exits wins regardless of registration order. The containment DECISION
  * therefore lives in the boot handler, and it must use this same ruler rather than minting a second one.

package/dist/orchestration/hardened-vm-worker-runner.d.ts

@@ -1,7 +1,7 @@
 import { type WorkflowScriptRunner } from "@sema-agent/core";
 import { type HardenedVmLimits } from "./hardened-vm-runner.js";
 /**
- * Worker-isolated S8 hard runner (design/98 v2). Runs the hardened-vm membrane inside a `worker_thread`, adding
+ * Worker-isolated S8 hard runner ([ref] v2). Runs the hardened-vm membrane inside a `worker_thread`, adding
  * RESOURCE isolation on top of the in-process {@link import("./hardened-vm-runner.js").createHardenedVmRunner}'s
  * BOUNDARY isolation:
  *   - HEAP cap (`resourceLimits.maxOldGenerationSizeMb`): a runaway-allocation script OOMs the WORKER (an `error`

package/dist/orchestration/subagent-steer.d.ts

@@ -1,6 +1,6 @@
 import type { SubagentSteerHandle } from "@sema-agent/core";
 /**
- * C2 (core 1.219) + design/122 (core 1.225) — the SERVICE-side registry for
+ * C2 (core 1.219) + [ref] (core 1.225) — the SERVICE-side registry for
  * STEERING and RESUMING a Task SUB-AGENT (a sync delegation spawned by the `Agent` tool), the sibling of
  * {@link import("./workflow-agent-steer.js").WorkflowAgentRegistry} for workflow agents.
  *
@@ -10,7 +10,7 @@ import type { SubagentSteerHandle } from "@sema-agent/core";
  * Delivery is replica-local (the handle is an in-memory bridge, like `steerableRuns`); a cross-replica
  * steer/resume is an honest 409, never a silent drop.
  *
- * 🔴 LIFECYCLE (design/122 item ③ — the "不改必踩" change): handles are NO LONGER evicted on child settle.
+ * 🔴 LIFECYCLE ([ref] item ③ — the "不改必踩" change): handles are NO LONGER evicted on child settle.
  * `resume` is only legal AFTER the child settled (core rejects `steering.still_running` before), so a
  * settle-evicted registry would make resume structurally unreachable. Instead:
  *   - one handle PER parentToolCallId, NEWEST WINS (core D2: each resume re-emits a FRESH handle under the
@@ -41,7 +41,7 @@ export declare class SubagentSteerRegistry {
     /** Register a child handle under its parent run. SAME parentToolCallId replaces (core D2: a resume
      *  re-emits a fresh handle for the revived run — newest wins). Returns an IDENTITY-GUARDED unregister
      *  thunk: it removes the entry only while it still holds THIS handle (a fresh sibling-leg registration
-     *  under the same id survives the old leg's teardown). Call it at LEG END, not on settle (design/122 ③). */
+     *  under the same id survives the old leg's teardown). Call it at LEG END, not on settle ([ref] ③). */
     register(runId: string, handle: SubagentSteerHandle): () => void;
     /** Resolve `runId` + `target` to its handle on this replica. Exact `parentToolCallId` match wins (unique —
      *  newest-per-id by construction → count is 0|1); otherwise match by `agentName` (count may be >1 →

package/dist/orchestration/workflow-agent-steer.d.ts

@@ -34,7 +34,7 @@ export declare class WorkflowAgentRegistry {
  *   · **「被截断过」仍有信号**:超界时正文段尾出现 `…`(未超界时不出现)⇒ 消费方能判断"这不是全文";
  *   · **「截了多少」不再披露**:`[+N chars]` 在**所有**档位都没有了(实测 +1 / +10 / +100 / +5000 / +50000
  *     全部无披露,输出长度恒 4103)。所以一个超出 5 万字符的输入与只超 1 个字符的输入,**外观完全相同**。
- *  ⚠️ core [1707]⑤ 的措辞是「**刚过界**的输入现在是裸 `…` 结尾」,而实测是**全档位**都没有披露 —— 范围比
+ *  ⚠️ core [ref]⑤ 的措辞是「**刚过界**的输入现在是裸 `…` 结尾」,而实测是**全档位**都没有披露 —— 范围比
  *  它描述的宽。已带实测数据上黑板问 core 这是否是有意的(可能只是描述省略,也可能是它没注意到)。
  *  在得到答复前**不改行为**:core 的截断器是它那侧的安全件,server 不该自己在外面补一层"+N chars"去顶
  *  ——那会变成两处各说一套。 */

package/dist/orchestration/workflow-completion-inbox.d.ts

@@ -69,7 +69,7 @@ export declare const PURGE_FENCE_MS: number;
  *  to swallow any realistic notify lag incl. a boot-recovery re-fire racing a fresh poll; per-runId scoped, so
  *  it can never starve a DIFFERENT workflow's push. In-memory only (see {@link PURGE_FENCE_MS} rationale). */
 export declare const SERVED_FENCE_MS: number;
-/** design/144 §4 server 折叠键:`JSON([域, taskId, RAW status])[#seq]`。域=external 帧独立 lane(task_id 是
+/** [ref] §4 server 折叠键:`JSON([域, taskId, RAW status])[#seq]`。域=external 帧独立 lane(task_id 是
  *  调用方自由串,不分域可预占内部帧键把真实子代 settle 帧吞掉)/其余内部帧统一 "task" 域。
  *
  *  三路复审修1(MED):status 保留 RAW,不再归一 completed/failed —— 归一让同 id 无 seq 的两条 external
@@ -91,15 +91,15 @@ export declare function taskNotificationFoldKey(n: {
     status: string;
     seq?: number;
 }): string;
-/** design/144 stream 侧去重键(core [784]④a + codex 1.189 前双审 F2)= `域:taskId:status[#seq]`。
+/** [ref] stream 侧去重键(core [ref]④a + codex 1.189 前双审 F2)= `域:taskId:status[#seq]`。
  *  与 {@link taskNotificationFoldKey} 同族,域二分也一致(codex F2 HIGH:external 通知的 task_id 是
  *  POST /v1/sessions/:id/notify 调用方自由串——同一条腿上,drain 出的 external 帧可与内部任务帧同形
  *  `task_id:status:seq` 撞键互吞,per-leg 键集并不豁免这个面,旧注释「没有跨调用方预占面」判错);
  *  仍与 fold key 有意不同的一点:status 保留 RAW(killed/cancelled/event 不归一 failed)——归一会让同
  *  task 的 Monitor event 批与 failed 终态在一条腿上互吞;wire 去重要的是逐帧身份,不是 inbox 的双终态列。
  *  `seq` 折入 = 停→唤→停的第二周期同 status 帧各自成键(core 1.283 起 background_agent 四腿 notify 铸
- *  cycleSeq;缺 seq 时旧键曾把二周期 completed 帧在 observer 臂反向吞掉——core [784]④a);无 seq 的帧
- *  (bash/monitor terminal/retain 降级)保持单周期旧键=同键第二帧吞,诚实语义。[2373]B-10:core 4.0.0 起
+ *  cycleSeq;缺 seq 时旧键曾把二周期 completed 帧在 observer 臂反向吞掉——core [ref]④a);无 seq 的帧
+ *  (bash/monitor terminal/retain 降级)保持单周期旧键=同键第二帧吞,诚实语义。[ref]B-10:core 4.0.0 起
  *  task_type 是必填闭合枚举——`task_type?` 可选性**不再对应旧 core 帧**,它活着只为家族前缀构造
  *  (server.ts fleet 腿 `taskNotificationFoldKey({task_id,status})` 同款用法);缺席归 "task" 域的语义
  *  只在前缀用途下生效。external 帧三来源齐备(notify 端点 core 铸 / inbox entry extras 存 / drain 帧
@@ -257,7 +257,7 @@ export declare function taskNotificationInboxEntry(sessionId: string, owner: str
         edits: number;
     }>;
     resumable?: boolean;
-    /** core 1.353([1412]):诊断槽(journal 坐标+教句,引擎值单源)——park 透传,drain 帧原样带。 */
+    /** core 1.353([ref]):诊断槽(journal 坐标+教句,引擎值单源)——park 透传,drain 帧原样带。 */
     diagnostics?: string;
 }, enqueuedAt: number, 
 /** lead-b (dual-ID audit): the PARENT run's durable taskId (the uuid the shell's footer rows
@@ -265,7 +265,7 @@ export declare function taskNotificationInboxEntry(sessionId: string, owner: str
  *  parent row without a side lookup. */
 parentTaskId?: string, 
 /**
- * design/373 §3.6(core 5.61.0,#366 / codex R1[high]):core 在 `onTaskNotification` 的**第二参**上报的
+ * [ref] §3.6(core 5.61.0,[ref] / codex R1[high]):core 在 `onTaskNotification` 的**第二参**上报的
  * 投递档位。park 是**跨 run** 的那条投递路径 —— 不带过去,档位就在最常走的一条路上恒缺席。
  *
  * 🔴 只在 core **真的给了**档位时传:缺席原样缺席(与 live 投影同一条「缺席≠later」纪律)。

package/dist/orchestration/workflow-notify-journal.d.ts

@@ -152,7 +152,7 @@ export declare class WorkflowNotifyGate {
      *
      * BOTH abandoned arms (boot-orphan + stale-past-grace) flip the DURABLE row to `failed` FIRST (CAS on rev),
      * so the run store, the fleet panel and the delivered notify give ONE answer — previously the notify said
-     * `failed` while `/workflows` kept saying `running` forever ([2999]: republishing without finalizing would
+     * `failed` while `/workflows` kept saying `running` forever ([ref]: republishing without finalizing would
      * have turned "panel empty" into "panel shows a row that never moves"). A lost CAS means the run moved under
      * the sweep (e.g. its real terminal landed concurrently) — skip this pass; the entry stays pending and the
      * next sweep handles the NEW state.
@@ -175,14 +175,14 @@ export declare class WorkflowNotifyGate {
         /** Replica-local (File/in-memory) journal ONLY: a pending entry recorded BEFORE this timestamp belongs to
          *  a previous incarnation of THIS process — workflow executors are in-process, so they died with it and a
          *  still-`running` run is a boot-orphan: finalize it NOW instead of leaving the user's "Waiting for
-         *  workflow" pointed at a run that can never finish for the whole grace window ([2995] 顺带①/[3000]§二).
+         *  workflow" pointed at a run that can never finish for the whole grace window ([ref] 顺带①/[ref]§二).
          *  NEVER pass this for a cross-replica (SQL) journal — there a pending running run may be genuinely alive
          *  on another replica, and age (`orphanGraceMs`) is the only sound orphan proxy.
          *  ⚠️ This wall-clock cutoff is a NECESSARY, not sufficient, condition — {@link recordedThisIncarnation}
          *  is the authoritative one (a clock rollback after boot would otherwise stamp THIS process's own new
          *  entries below the cutoff and finalize live runs). */
         finalizeStartedBeforeMs?: number;
-        /** Retire a fleet row for a run this sweep just finalized ([2995]/[2999]): called ONLY with a TERMINAL run,
+        /** Retire a fleet row for a run this sweep just finalized ([ref]/[ref]): called ONLY with a TERMINAL run,
          *  so the {@link JournalingWorkflowRunStore} projection publishes the final frame and then removes the row —
          *  the store, the panel and the notify end up saying the same thing. Never called with a `running` run (see
          *  the single-writer invariant above). Late-bound because the wrapper is constructed after this gate. */
@@ -264,7 +264,7 @@ export declare class InMemoryWorkflowNotifyJournalStore implements WorkflowNotif
  */
 export declare class JournalingWorkflowRunStore implements WorkflowRunStore {
     private readonly inner;
-    /** [1262] optional since the fleet decoupling: undefined ⇒ no start-time journal (ephemeral memory
+    /** [ref] optional since the fleet decoupling: undefined ⇒ no start-time journal (ephemeral memory
      *  backend has nothing to recover), the FLEET half still publishes — the panel is replica-local UI
      *  state and must not be gated on the durable-notify machinery (the regression that emptied clay's
      *  workflow panel on memory-backend deployments). */
@@ -273,7 +273,7 @@ export declare class JournalingWorkflowRunStore implements WorkflowRunStore {
      *  point as the notify journal). Optional — undefined ⇒ no fleet publish. */
     private readonly fleetBus?;
     constructor(inner: WorkflowRunStore, 
-    /** [1262] optional since the fleet decoupling: undefined ⇒ no start-time journal (ephemeral memory
+    /** [ref] optional since the fleet decoupling: undefined ⇒ no start-time journal (ephemeral memory
      *  backend has nothing to recover), the FLEET half still publishes — the panel is replica-local UI
      *  state and must not be gated on the durable-notify machinery (the regression that emptied clay's
      *  workflow panel on memory-backend deployments). */
@@ -284,7 +284,7 @@ export declare class JournalingWorkflowRunStore implements WorkflowRunStore {
     /** Derive + publish the MF-Fleet workflow row from a WorkflowRun (doneCount/totalCount from agents, tokens from
      *  stats); a terminal workflow LEAVES the fleet (publish terminal then remove), a running one stays/updates. */
     private publishFleet;
-    /** [2995] recovery projection seam: the same fleet projection as the put/update observation points, exposed so
+    /** [ref] recovery projection seam: the same fleet projection as the put/update observation points, exposed so
      *  the recovery sweep can RETIRE a row for a run it just finalized (terminal input ⇒ final frame, then remove).
      *  Wire it as `recover`'s `publishTerminalFleetRow` hook — and only ever hand it a TERMINAL run: a `running`
      *  row published from outside the wrapper's own write path has no guaranteed retirement (see the invariant on

package/dist/parent-watch.d.ts

@@ -1,5 +1,5 @@
 /**
- * #219(黑板 [3617]):引擎 **parent 监视**。
+ * [ref](黑板 [ref]):引擎 **parent 监视**。
  *
  * ## 防的是什么
  *