@sema-agent/server 7.52.0 → 7.53.0

package/dist/plugins/local-checkpoint-store.d.ts

@@ -1,5 +1,5 @@
 import { type Checkpoint, type CheckpointSummary, type CheckpointToken, type PendingSteerInput, type ReopenReason, type ResolveExpectation, type ResumeOutcome, type StoreDurability, type StoreFidelity } from "@sema-agent/core";
-import { type DecidedApprovalRecord, type PendingCheckpoint } from "./checkpoint-store-sql.js";
+import { type DecidedApprovalRecord, type PendingCheckpoint, type PendingRowBinding } from "./checkpoint-store-sql.js";
 export interface LocalCheckpointStoreOptions {
     /** taskId join for the pending card (the local FileRunStore's `getActiveTaskId`). Absent ⇒ `taskId: null`. */
     getActiveTaskId?: (sessionId: string) => Promise<string | undefined>;
@@ -8,11 +8,11 @@ export interface LocalCheckpointStoreOptions {
     ownerOf?: (sessionId: string) => Promise<string | null | undefined>;
 }
 export declare class LocalCheckpointStore {
-    /** #270 车1:托管留存声明 —— **诚实的 none**(与 local session 店同一条判据:本店的行没有按期删除的腿;
+    /** [ref] 车1:托管留存声明 —— **诚实的 none**(与 local session 店同一条判据:本店的行没有按期删除的腿;
      *  留存三方法只实现在 SQL 聚合店上)。locked policy + 本店 ⇒ core 的门拒启,那是契约的正确行为。 */
     readonly retention: import("@sema-agent/core").RetentionDeclaration;
     /**
-     * `CheckpointStore.durability` 声明(#167 欠账,#168 件5)——**如实按内核判**:本类的内核是 core 的
+     * `CheckpointStore.durability` 声明([ref] 欠账,[ref] 件5)——**如实按内核判**:本类的内核是 core 的
      * `FileCheckpointStore`(crash-safe ledger + snapshot,自身声明 `"durable"`),本地 scope 注册表也落
      * 在同一个盘上目录里 ⇒ 进程重启后 park 全部还在、还赎得回,`"durable"` 是诚实读数而不是抬举。
      *
@@ -21,17 +21,17 @@ export declare class LocalCheckpointStore {
      */
     readonly durability: StoreDurability;
     /**
-     * `CheckpointStore.fidelity` 声明(core 5.17.0 [3052] 提货批 #172)——**如实按内核判**,与 durability
+     * `CheckpointStore.fidelity` 声明(core 5.17.0 [ref] 提货批 [ref])——**如实按内核判**,与 durability
      * 同一条判据:本类的读写内核是 core 的 `FileCheckpointStore`,它自己声明 `"json"`(盘上是 JSON 行),
      * 包装层只加 scope/session 索引与 ctx 附属文件,不改这条 round-trip 的宽度 ⇒ 抄内核的读数是诚实的。
      *
      * ⚠️ 包装类**不继承**被包装者的声明(本类是委派不是子类),所以这一格必须自己写。它与内核那一格
-     * 是否仍然一致由测试盯着(`wiring-governance-operator.test.ts` 的 #172 组直接读内核那一格对表)——
+     * 是否仍然一致由测试盯着(`wiring-governance-operator.test.ts` 的 [ref] 组直接读内核那一格对表)——
      * 内核哪天改宽度,包装层的声明会被那条钉当场揪出来,而不是靠人记得同步。
      */
     readonly fidelity: StoreFidelity;
     /**
-     * `CheckpointStore.redecision` 声明(core 5.22.0 F-012 L2/L3;[3342] clay 裁放行)——**如实按内核判**,
+     * `CheckpointStore.redecision` 声明(core 5.22.0 F-012 L2/L3;[ref] clay 裁放行)——**如实按内核判**,
      * 与 durability/fidelity 同一条判据:内核 core `FileCheckpointStore` **自己**声明 `{ reopen: true }`,
      * 本类的 {@link LocalCheckpointStore.reopen} 纯委派给它 ⇒ 抄内核的读数是诚实的。包装类**不继承**被
      * 包装者的声明(委派不是子类),所以这一格必须自己写。`validatingLease` 不声明(内核也没声明)。
@@ -46,7 +46,7 @@ export declare class LocalCheckpointStore {
     private readonly ctxDir;
     private readonly tmpDir;
     private readonly scopes;
-    /** [868] sessionId → every token ever put for it — the service-side index that stands in for the SQL twins'
+    /** [ref] sessionId → every token ever put for it — the service-side index that stands in for the SQL twins'
      *  `WHERE checkpoint.session_id = ?` on NON-pending rows (core's File store enumerates pending only via
      *  listByScope; get(token) is the sole read for resolved/expired rows, so cross-status session queries need
      *  this registry). Registered BEFORE the inner put (same crash direction as the scopes registry: a stale
@@ -63,7 +63,7 @@ export declare class LocalCheckpointStore {
     get(token: CheckpointToken): Promise<Checkpoint | null>;
     resolve(token: CheckpointToken, scope: string, outcome: ResumeOutcome, expect?: ResolveExpectation): Promise<boolean>;
     reopen(token: CheckpointToken, scope: string, reason: ReopenReason): Promise<boolean>;
-    /** core 5.14.0(#147):入参是 `PendingSteerInput`(text/trusted + 可选 actor/inputId/priority),不是
+    /** core 5.14.0([ref]):入参是 `PendingSteerInput`(text/trusted + 可选 actor/inputId/priority),不是
      *  两键单座 —— 形参窄成 `{text,trusted}` 会**静默丢掉**署名与幂等键(TS 的方法参数是双变的,窄形不
      *  报错,只是把三个可选键从类型上抹掉,调用点再也传不进来)。队列语义与边界全在被包的 core
      *  `FileCheckpointStore` 里,本 wrapper 只做转发。 */
@@ -81,21 +81,29 @@ export declare class LocalCheckpointStore {
     private pendings;
     /** Operator approval queue — the same NON-secret card as the SQL twins (never the token). */
     listPending(scope?: string): Promise<PendingCheckpoint[]>;
-    findPendingTokenBySession(sessionId: string, scope?: string): Promise<CheckpointToken | null>;
-    /** [868] read-only probe face: does this session have an EXPIRED checkpoint row? The local twin of the SQL
+    /**
+     * [ref]:与 SQL 孪生**同判**的 session 键读口 —— `binding.gateKinds` 过滤门型、序恒「最新优先,token 兜平局」
+     * ({@link pendingRowPrecedes} 是两 twin 共用的判据;语义全文见 SQL 侧 `PendingRowBinding` 顶注)。
+     * 修前是「扫描序里第一条 sessionId 相等的」:`pendings()` 按 scope 注册表 + `listByScope` 顺序走,同
+     * session 两条 pending 时答哪条取决于 sidecar 里 scope 的插入序 —— 与 SQL 无序 `LIMIT 1` 同病。
+     */
+    findPendingTokenBySession(sessionId: string, scope?: string, binding?: PendingRowBinding): Promise<CheckpointToken | null>;
+    /** [ref]:候选集 → 读口该答的那一条(过滤 sessionId + 门型,再取「最新优先」)。 */
+    private pickPendingRow;
+    /** [ref] read-only probe face: does this session have an EXPIRED checkpoint row? The local twin of the SQL
      *  `EXISTS (SELECT 1 FROM checkpoint ce WHERE ce.session_id = ? AND ce.status = 'expired')` that drives the
      *  run stores' failSuspendedWithExpiredCheckpoint. Scans the session→token index (get(token) is the only
      *  cross-status read core's File store offers); an index entry whose inner row vanished is pruned lazily.
      *  Backed by a persisted registry, so it stays honest — never a guessed "true".
      *  ⚠️ 存量限制(codex M2,如实):索引随 put 增量建立,无升级迁移——本版本部署前已存在的 checkpoint 不在
      *  索引里,其 expired 对本探针不可见(core File store 的 listByScope 是 pending-only,无法枚举历史行回填)。
-     *  旧存量锁死的恢复把手 = cancel verb([868]①,不依赖本索引);增量行全覆盖。 */
+     *  旧存量锁死的恢复把手 = cancel verb([ref]①,不依赖本索引);增量行全覆盖。 */
     hasExpiredBySession(sessionId: string): Promise<boolean>;
     /**
-     * #368 件1 —— SQL 孪生 `findDecidedApprovalsForBinding` 的本地形(判据、词表、失败方向逐条同源;
+     * [ref] 件1 —— SQL 孪生 `findDecidedApprovalsForBinding` 的本地形(判据、词表、失败方向逐条同源;
      * 那处顶注是唯一真源,这里只记两处**本地形自己的**差别)。
      *
-     *  · 枚举面走 [868] 的 `sessionTokens` 索引 —— 与 `hasExpiredBySession` 同一条路(core 的 File store
+     *  · 枚举面走 [ref] 的 `sessionTokens` 索引 —— 与 `hasExpiredBySession` 同一条路(core 的 File store
      *    只能 pending-only 枚举,跨态读只有 `get(token)`),所以它那条**存量限制**在这里逐字同样成立:
      *    索引建立之前 park 的老行对本口不可见 ⇒ 回放判别不出 ⇒ 调用方逐字回落 404(保守方向)。
      *  · **没有排序**:本口交出全部命中行,由调用方按「判词一致才回放」判(理由见 SQL 孪生顶注的
@@ -104,16 +112,17 @@ export declare class LocalCheckpointStore {
      *    投了就是「SQL 车道有、local 车道没有」的键集分岔。
      */
     findDecidedApprovalsForBinding(sessionId: string, boundCallId: string): Promise<DecidedApprovalRecord[]>;
-    /** `undefined` = no pending row; else the owner scope (local scopes are always strings — never null). */
-    peekPendingScope(sessionId: string): Promise<string | null | undefined>;
+    /** `undefined` = no pending row; else the owner scope (local scopes are always strings — never null).
+     *  [ref]:与 `findPendingTokenBySession` 同一个 {@link pickPendingRow}(同 binding ⇒ 同一行)。 */
+    peekPendingScope(sessionId: string, binding?: PendingRowBinding): Promise<string | null | undefined>;
     /**
-     * design/80 D-D global expiry sweep — same kind-split as the TiDB twin: the deadline branch abort-expires
+     * [ref] D-D global expiry sweep — same kind-split as the TiDB twin: the deadline branch abort-expires
      * every kind EXCEPT a human/irreversible_ask approval gate (those get the graceful resolve-DENY via
      * listExpiredApprovalGates), with the AskUserQuestion carve-back (denying a question is incoherent → expire);
      * the terminal_at_ms branch (derived read-time via the SAME formula the TiDB put stamps) abort-expires ANY kind.
      */
     reapExpired(cutoff: number): Promise<number>;
-    /** design/80 D-D SLA deny-sweep input — pending human/irreversible_ask gates past deadline (excl. AskUserQuestion). */
+    /** [ref] D-D SLA deny-sweep input — pending human/irreversible_ask gates past deadline (excl. AskUserQuestion). */
     listExpiredApprovalGates(cutoff: number, limit?: number): Promise<Array<{
         sessionId: string;
         scope: string;

package/dist/plugins/local-checkpoint-store.js

@@ -3,7 +3,7 @@ import { existsSync, readFileSync, readdirSync, renameSync, unlinkSync, mkdirSyn
 import { join } from "node:path";
 import { isApprovalGateKind } from "../tool-approval.js";
 import { FileCheckpointStore, atomicWriteFile, sanitizePathComponent, } from "@sema-agent/core";
-import { approvalDecisionOfWinner, approvalPayloadFingerprint, boundedRuleOffers, boundedToolInput, TERMINAL_BACKSTOP_MS, TERMINAL_GRACE_MS } from "./checkpoint-store-sql.js";
+import { approvalDecisionOfWinner, approvalPayloadFingerprint, boundedRuleOffers, boundedToolInput, pendingRowPrecedes, TERMINAL_BACKSTOP_MS, TERMINAL_GRACE_MS } from "./checkpoint-store-sql.js";
 import { UNMANAGED_RETENTION } from "./retention-store-sql.js";
 function terminalAtOf(cp) {
     return Math.max(cp.createdAt + TERMINAL_BACKSTOP_MS, (cp.deadline ?? 0) + TERMINAL_GRACE_MS);
@@ -159,15 +159,28 @@ export class LocalCheckpointStore {
                     const rs = boundedRuleOffers(pa?.ruleOffers);
                     return rs !== undefined ? { ruleOffers: rs } : {};
                 })(),
+                ...(pa?.hasBidiControls === true ? { hasBidiControls: true } : {}),
             });
         }
         return rows.sort((a, b) => (b.riskDescriptor?.severity ?? 0) - (a.riskDescriptor?.severity ?? 0) || a.createdAt - b.createdAt);
     }
-    async findPendingTokenBySession(sessionId, scope) {
-        for (const { token, cp } of await this.pendings(scope))
-            if (cp.sessionId === sessionId)
-                return token;
-        return null;
+    async findPendingTokenBySession(sessionId, scope, binding) {
+        return this.pickPendingRow(await this.pendings(scope || undefined), sessionId, binding)?.token ?? null;
+    }
+    pickPendingRow(rows, sessionId, binding) {
+        let best;
+        for (const row of rows) {
+            if (row.cp.sessionId !== sessionId)
+                continue;
+            if (binding?.gateKinds !== undefined) {
+                const kind = row.cp.gate?.kind;
+                if (kind === undefined || !binding.gateKinds.includes(kind))
+                    continue;
+            }
+            if (best === undefined || pendingRowPrecedes({ createdAt: row.cp.createdAt, token: row.token }, { createdAt: best.cp.createdAt, token: best.token }, binding?.pick))
+                best = row;
+        }
+        return best;
     }
     async hasExpiredBySession(sessionId) {
         const tokens = this.sessionTokens.get(sessionId);
@@ -216,11 +229,8 @@ export class LocalCheckpointStore {
         }
         return out;
     }
-    async peekPendingScope(sessionId) {
-        for (const { cp } of await this.pendings())
-            if (cp.sessionId === sessionId)
-                return cp.scope;
-        return undefined;
+    async peekPendingScope(sessionId, binding) {
+        return this.pickPendingRow(await this.pendings(), sessionId, binding)?.cp.scope;
     }
     async reapExpired(cutoff) {
         let n = 0;

package/dist/plugins/local-session-store.d.ts

@@ -3,7 +3,7 @@ import type { SessionSummary } from "./store-contracts.js";
 import { type StagingHandle } from "../session-sync-kernel.js";
 export declare class LocalSessionStore implements SessionStore {
     private readonly repo;
-    /** #270 车1:托管留存声明 —— **诚实的 none**。本店的行没有任何按期删除的腿(留存 lane 的三方法只实现在
+    /** [ref] 车1:托管留存声明 —— **诚实的 none**。本店的行没有任何按期删除的腿(留存 lane 的三方法只实现在
      *  SQL 聚合店上),所以 locked policy + 本店 ⇒ core 的 `assertRetentionCapability` 拒启,这是契约的
      *  **正确行为**不是缺口(要留存治理先上 DB 后端;设计稿 §1「不做清单」逐字)。缺席也会被读成 none,
      *  显式写出来是文档义务:沉默表达不出「我核对过我的介质就是删不了」。 */
@@ -53,7 +53,7 @@ export declare class LocalSessionStore implements SessionStore {
      *  lastActivity sidecar ON PURPOSE (that format is a #10 clobber area); titles are write-once + ultra-low-rate
      *  (one per session, ever), so a plain read-modify-write with tmp+rename per write is enough — no debounce.
      *
-     *  🔴 CROSS-INSTANCE (fixed 2026-07-25, blackboard [1684] — core's "per-instance state" defect class):
+     *  🔴 CROSS-INSTANCE (fixed 2026-07-25, blackboard [ref] — core's "per-instance state" defect class):
      *  these three used to be INSTANCE fields, which is exactly the shape core described — «the backend is shared
      *  more widely than the object, but the state and the lock hang off the object». Two `LocalSessionStore`s over
      *  the SAME dataDir each held their own `titles` map and their own write chain, so a real concurrency probe
@@ -124,7 +124,7 @@ export declare class LocalSessionStore implements SessionStore {
      *  现在 Map miss 时探 repo:盘上在 ⇒ 按 load() 两处懒回填早已写下的同一判据回填 `null`(registered
      *  ownerless);repo 真没有才 `undefined`。SQL 孪生无此形(owner 在 session_meta 行,重启无损)。 */
     ownerOf(sessionId: string): Promise<string | null | undefined>;
-    /** [1196] 六轮复审:owner+leafId 原子快照——单线程 JS 内两同步/顺序读之间无 await 打断 owner 判定
+    /** [ref] 六轮复审:owner+leafId 原子快照——单线程 JS 内两同步/顺序读之间无 await 打断 owner 判定
      *  (owner 先取快照,leaf 读后 owner 复核,变了=undefined 视作删除中,调用方按删处理)。 */
     getHead(sessionId: string): Promise<{
         owner: string | null;
@@ -161,7 +161,7 @@ export declare class LocalSessionStore implements SessionStore {
      */
     listSessions(opts: {
         owner?: string;
-        /** [4198] 窄互认第二臂的第三条件(SQL 孪生里是 `owner IS NULL` 谓词;此处是同义的 `owner === null` 放行)。 */
+        /** [ref] 窄互认第二臂的第三条件(SQL 孪生里是 `owner IS NULL` 谓词;此处是同义的 `owner === null` 放行)。 */
         includeUnowned?: boolean;
         cursor?: {
             lastActivityAt: string;
@@ -173,7 +173,7 @@ export declare class LocalSessionStore implements SessionStore {
     /** K-5c (core 1.155 SessionStore seam): core's Runner calls this at runTask START with the run's taskId, so the
      *  latest run surfaces as `lastRunId` on listSessions even while it is still running/suspended (the local backend
      *  has no runs ledger to derive it from, unlike the TiDB/PG twins). In-memory, last-write-wins per session.
-     *  #499(core 5.65 增量批,**有意缓议**):core 的第三参 engine runId 在此**尚未消费**——它唯一的
+     *  [ref](core 5.65 增量批,**有意缓议**):core 的第三参 engine runId 在此**尚未消费**——它唯一的
      *  合法出口是 listSessions 行上的 `lastTaskRunId`,而 `SessionSummary` 是 canonical spec 的**闭集**
      *  (sema-sdk spec/openapi.yaml `additionalProperties:false`,producer-contract sessionsList 格咬着),
      *  加键是跨仓 spec 节拍的事。spec 开键那一批再落:map 值扩成 `{taskId, runId?}` + 两座同动清座语义

package/dist/plugins/mailbox-store-sql.d.ts

@@ -1,9 +1,9 @@
 /**
- * MailboxStore SQL twins(design/151 S3c server pg 半场,[1530] 提货单①)——core teammate 信箱
+ * MailboxStore SQL twins([ref] S3c server pg 半场,[ref] 提货单①)——core teammate 信箱
  * (SendMessage 链)的 TiDB/PG 双方言实现。挂载缝 = S3c 行为车的 `RunnerDeps.mailboxStore`(core
- * 命名预告,[1530]§三);本文件先就绪 store 半场,行为车到货接线。
+ * 命名预告,[ref]§三);本文件先就绪 store 半场,行为车到货接线。
  *
- * 语义真源 = core `InMemoryMailboxStore`(dist/core/mailbox-store.js)+ [1530] 定谳(core 1.372
+ * 语义真源 = core `InMemoryMailboxStore`(dist/core/mailbox-store.js)+ [ref] 定谳(core 1.372
  * 终版文本,conformance 无两可):
  *  1. **同主重 claim = 续期 + 纳新**(crash-retry 正形):活 lease 只挡**别的** owner;同 owner 任意
  *     时刻重 claim 重设 TTL 并拿到当前全部未 ack 消息(maxSeq 随最新行走)。
@@ -13,12 +13,12 @@
  *     时顺带清 lease(全量 ack = 释放)。
  *  4. **lease 过期判 = 严格 `expiresAt > now` 才挡**;`releaseLease` 只在 owner 匹配时清。
  *  5. `peekCount` 含已 lease 消息(可见性 ≠ lease 态);空盒 claim = null(box 行在而消息 0 也 null)。
- *  6. **reap = SQL 全量真扫**(core File 实现只扫已加载盒 = 进程内 backstop,[1530] 确认 SQL 是全量
+ *  6. **reap = SQL 全量真扫**(core File 实现只扫已加载盒 = 进程内 backstop,[ref] 确认 SQL 是全量
  *     真扫的正确层):`maxAgeMs` 缺省 → 0;按盒 newest `sentAt < now - maxAgeMs` 删整盒;空盒(有
  *     box 行无消息)不删(InMemory 同形——`newest === undefined` 不删)。
  *
  * 键列 = 字节等价(TiDB VARBINARY / PG COLLATE "C",roster F2 案):scope/handle/lease_owner 的
- * `=` 必须纯字节——PAD SPACE 近撞不得穿隔离/抢别人 lease。PG unstorable bytes([1439] 三层定谳):
+ * `=` 必须纯字节——PAD SPACE 近撞不得穿隔离/抢别人 lease。PG unstorable bytes([ref] 三层定谳):
  * `content` 是消息**内容面**(收件人将读到、注入对话)→ 与 PG 转录 payload 同族 lossy(pgSanitizeText,
  * U+FFFD 标记,内容不失行);**身份键 scope/handle/owner/from 拒绝式**(pgHasUnstorable →
  * PgUnstorableError fail-loud——attribution/路由键清洗形变 = 行与查询键错位,协议数据同向)。TiDB
@@ -61,7 +61,7 @@ export declare class PgMailboxStore implements MailboxStore {
     private readonly pool;
     constructor(pool: PgPool);
     private tx;
-    /** 身份键拒绝式([1439] 协议纪律):scope/handle/owner/from 清洗形变 = 路由/attribution 错位。 */
+    /** 身份键拒绝式([ref] 协议纪律):scope/handle/owner/from 清洗形变 = 路由/attribution 错位。 */
     private assertIdentity;
     append(scope: string, handle: string, msg: MailboxAppendMessage): Promise<number>;
     claimLease(scope: string, handle: string, owner: string, ttlMs: number, now?: number): Promise<MailboxLease | null>;

package/dist/plugins/memory-embedder-fingerprint.d.ts

@@ -1,5 +1,5 @@
 /**
- * design/234 —— embedder **指纹门**(清空重建形,clay 终裁 [3647]⑤ 方向;稿=sema-internal
+ * [ref] —— embedder **指纹门**(清空重建形,clay 终裁 [ref]⑤ 方向;稿=sema-internal
  * `server/design/design-234-embedder-fingerprint-20260812.md` v1+v2)。
  *
  * ## 病灶
@@ -71,7 +71,7 @@
  * 主动回填件(清空后不回填,行被 patch 时自然重嵌)/ 行级 embedder 记账列(结构性根治滚动窗)/
  * pgvector 接线件的列 dim 校验 / TiDB 向量面(v1 lexical only)。
  *
- * 🔴 **不回填的真代价(#234 定界车 2026-08-14 实测更正,稿 §4/§V3 说轻了一档)**:稿把代价写成「那些行
+ * 🔴 **不回填的真代价([ref] 定界车 2026-08-14 实测更正,稿 §4/§V3 说轻了一档)**:稿把代价写成「那些行
  * 长期停留 lexical 档」,读起来像**排序退化**;真码是**可达性悬崖**——`memory-engine-pg.ts` 的进程内腿
  * 对无向量行落 `jaccardDistance`,core 的该函数在**零词交集**时返回 `null`,`search` 当场 `continue`,
  * 行被**丢出结果集**;仍有向量的行则走余弦、不被这道门丢(前提是查询侧也嵌得出来——embedder 故障那一

package/dist/plugins/memory-engine-pg.d.ts

@@ -50,7 +50,7 @@ export declare class PgMemoryEngineBackend implements MemoryBackend {
     private readonly history?;
     /** Cumulative lost-row count — audit-line breakage must itself be auditable. */
     private historyRowsLost;
-    /** design/81 rung indicator — same semantics as PgMemoryStore.vectorMode. */
+    /** [ref] rung indicator — same semantics as PgMemoryStore.vectorMode. */
     get vectorMode(): "native" | "portable" | "lexical";
     constructor(query: PgQueryFn, opts?: PgMemoryEngineBackendOptions);
     /** The embed/search haystack — BYTE-EQUAL to FileBackend's lexical haystack (file-backend search). */

package/dist/plugins/memory-engine-tidb.d.ts

@@ -38,7 +38,7 @@ export declare class TiDBMemoryEngineBackend implements MemoryBackend {
     private readonly history?;
     /** Cumulative lost-row count — audit-line breakage must itself be auditable. */
     private historyRowsLost;
-    /** design/81 rung indicator — TiDB v1 sits on the lexical floor (Pg twin parity surface). */
+    /** [ref] rung indicator — TiDB v1 sits on the lexical floor (Pg twin parity surface). */
     get vectorMode(): "lexical";
     constructor(pool: Pool, opts?: TiDBMemoryEngineBackendOptions);
     private selectRows;

package/dist/plugins/memory-key-guards.d.ts

@@ -1,11 +1,11 @@
-/** R5(车A [3191] 欠账,批γ 落地;#271 件1 补齐写口):memory 面的键宽写前守卫。
+/** R5(车A [ref] 欠账,批γ 落地;[ref] 件1 补齐写口):memory 面的键宽写前守卫。
  *  列宽收窄后,模型/调用方可控的键(条目名 slug、租户盘 scope)超宽此前落裸 SQL 错(PG
  *  `value too long`)或非严格 MySQL 静默截断(截断=两个不同的键折叠成同一行=**条目互串 / 两个租户
  *  的盘塌成一个**,最危险形)。写前响亮拒,错误可分类。
  *  列宽同源门=test/key-width-guards.test.ts(守卫常量 vs 两方言 DDL 逐字对表);写口在场门=同文件
- *  「#271 件1」组(超宽键一条写语句都不许发出 seam)。
+ *  「[ref] 件1」组(超宽键一条写语句都不许发出 seam)。
  *
- *  **本文件是这两个宽度的唯一属主**(#271 件1):scope 守卫此前住在 `src/memory-scope.ts`,只被
+ *  **本文件是这两个宽度的唯一属主**([ref] 件1):scope 守卫此前住在 `src/memory-scope.ts`,只被
  *  `memoryScopeFor` 的产出处消费,而 store 写口全无——同一个列宽有两个居所、两半消费面,正是
  *  「守卫在位≠写口接上」那类缺口的温床。`memory-scope.ts` 现在只**再导出**本文件的这两个符号
  *  (旧 import 路径逐字不变)。 */

package/dist/plugins/memory-optout-grant-store-sql.d.ts

@@ -1,11 +1,11 @@
 /**
- * design/383 §3.1 / S-50 §一(S-49 S-2)—— per-principal **memory-capture opt-out 授权表**
+ * [ref] §3.1 / [ref] §一([ref] S-2)—— per-principal **memory-capture opt-out 授权表**
  * `memory_optout_grant`:`RuntimeCaps.allowMemoryOptOut` 的本地 verdict 源 + operator 管理面的持久层。
- * SINGLE-FILE DUAL-DIALECT(design/158 A12 形,照 approval-ask-store-sql.ts:一个 `SqlMemoryOptOutGrantStore`
+ * SINGLE-FILE DUAL-DIALECT([ref] A12 形,照 approval-ask-store-sql.ts:一个 `SqlMemoryOptOutGrantStore`
  * 接 `SqlDriver`,两个薄 ctor 子类落方言绑定)。
  *
- * ── 数据形(S-50 §1.1 的施工形;**稿偏离如实记**)────────────────────────────────────────────────
- * S-50 稿写的是 `PRIMARY KEY (org_id, principal)` + `principal=''` 为 org 级缺省哨兵行。亲读本仓
+ * ── 数据形([ref] §1.1 的施工形;**稿偏离如实记**)────────────────────────────────────────────────
+ * [ref] 稿写的是 `PRIMARY KEY (org_id, principal)` + `principal=''` 为 org 级缺省哨兵行。亲读本仓
  * (侦察 2026-08-30):server **没有 org 身份维** —— 租户维 = 单 `principal`(`gatedPrincipal` 供给),
  * `org` 只是记忆 scope 目录里的一个词(`org-memory-admission.ts`:授权目录三态,不是 principal 的属性),
  * 任何 SQL 表都没有 `org_id` 列。给表铸一根没人能填的 `org_id` 就是编数据(「不编」律)。所以:
@@ -21,7 +21,7 @@
  *   updated_at_ms  BIGINT NOT NULL   审计:何时
  *   updated_by     VARCHAR(190)      审计:谁改的(operator principal,恒在场 —— 四端点都过 operator 门)
  *   note           VARCHAR(500) NULL 审计:为何(可缺席,不编)
- * 审计**行内**,不另建审计表(S-50 §1.3 v1 体量裁定;变更史需求真出现再升 retention 面同族表)。
+ * 审计**行内**,不另建审计表([ref] §1.3 v1 体量裁定;变更史需求真出现再升 retention 面同族表)。
  *
  * ── 方言差异(显式写在调用点,A12 doctrine)──────────────────────────────────────────────────────
  *   · `?` vs `$n` 占位符;
@@ -31,7 +31,7 @@
  *     本键最怕的方向)。
  *
  * ── 缓存姿态 ────────────────────────────────────────────────────────────────────────────────────
- * **零缓存直读**(S-50 §1.4 撤销窗:server 只保证 resolver 下一次读到新 verdict)。core 每任务 prepare 调
+ * **零缓存直读**([ref] §1.4 撤销窗:server 只保证 resolver 下一次读到新 verdict)。core 每任务 prepare 调
  * 一次 resolver;本表两行以内的 PK 点查在任何 SQL 后端都是亚毫秒级,加缓存 = 为不存在的负载引入一致性窗
  * (若未来实测成压力源,升级形 = TTL ≤ 60s 且写穿,稿已裁)。
  */
@@ -41,9 +41,9 @@ import type { PgQueryFn } from "./pg-query.js";
 import { type SqlDriver, type SqlDialect } from "./sql-driver.js";
 import type { MemoryOptOutVerdictSource } from "../runtime-caps-resolver.js";
 export declare const MEMORY_OPTOUT_GRANT_TABLE = "memory_optout_grant";
-/** 部署缺省哨兵行的 principal 值(S-50 §1.1;'' 是**真值**不是缺席 —— NOT NULL PK)。 */
+/** 部署缺省哨兵行的 principal 值([ref] §1.1;'' 是**真值**不是缺席 —— NOT NULL PK)。 */
 export declare const MEMORY_OPTOUT_DEFAULT_PRINCIPAL = "";
-/** 一行的读投影(wire 形逐字:S-50 §1.3 的 `{principal, allow, updatedAtMs, updatedBy, note?}`)。 */
+/** 一行的读投影(wire 形逐字:[ref] §1.3 的 `{principal, allow, updatedAtMs, updatedBy, note?}`)。 */
 export interface MemoryOptOutGrantRow {
     principal: string;
     allow: boolean;
@@ -59,7 +59,7 @@ export interface MemoryOptOutGrantFoldRow {
 }
 export type MemoryOptOutVerdictSourceKind = "principal" | "deployment-default" | "code-default";
 /**
- * S-50 §1.1 **F6 折叠律**(纯函数,`build*`:产纯数据):per-principal 行 → 部署缺省哨兵行 → 代码缺省 allow。
+ * [ref] §1.1 **F6 折叠律**(纯函数,`build*`:产纯数据):per-principal 行 → 部署缺省哨兵行 → 代码缺省 allow。
  * 三层折叠后**恒能给显式 verdict**。`principal` 缺席(匿名/系统 run)只看缺省行 —— 别人的覆盖行绝不算到
  * 匿名头上。rows 里不相干的 principal 行被忽略(SQL 层已按 `IN (?, '')` 收窄,这里再判一次是让纯函数对
  * 任意输入都正确,不依赖调用方的查询形)。
@@ -68,7 +68,7 @@ export declare function buildMemoryOptOutVerdict(rows: readonly MemoryOptOutGran
     allow: boolean;
     source: MemoryOptOutVerdictSourceKind;
 };
-/** 管理面(S-50 §1.3 四端点)+ resolver 面(S-1)共用的店接口。 */
+/** 管理面([ref] §1.3 四端点)+ resolver 面(S-1)共用的店接口。 */
 export interface MemoryOptOutGrantStore extends MemoryOptOutVerdictSource {
     /** 全表读投影:缺省行(缺席 ⇒ null,不编)+ 全部覆盖行(按 principal 升序,稳定)。 */
     list(): Promise<{

package/dist/plugins/memory-origin-law.d.ts

@@ -1,19 +1,19 @@
 /**
- * #307 件6(core 5.46.0 提货批,design/336 §2.3-2)—— **external-origin 标记不可变律**的 SQL 孪生实现。
+ * [ref] 件6(core 5.46.0 提货批,[ref] §2.3-2)—— **external-origin 标记不可变律**的 SQL 孪生实现。
  *
  * ## 这条法是什么、为什么落在本仓
  *
- * design/336 slice 1 给「已暴露会话」的普通记忆写打上引擎铸的 `frontmatter.origin` 标记(taint +
- * 成因闭集 + 铸造时刻),取代 design/178 那种「整条隔离」的全禁。标记的全部价值来自**不可洗白**:
+ * [ref] slice 1 给「已暴露会话」的普通记忆写打上引擎铸的 `frontmatter.origin` 标记(taint +
+ * 成因闭集 + 铸造时刻),取代 [ref] 那种「整条隔离」的全禁。标记的全部价值来自**不可洗白**:
  * 一旦某个 id 的**已提交**状态带了标记,之后**任何**写法(update / 裸 add / `guard:"absent"` add /
  * 同批 delete+re-add)都必须把它 DEEP-EQUAL 地带下去,否则拒绝。合法出口只有一个 —— **已提交的**
  * 墓碑(上一批真的 delete 掉了),那之后这个 id 开始一段未标记的新生命。
  *
  * core 5.46.0 把这条法写进了**记忆后端契约试剂盒**
  * (`dist/core/memory-engine/memory-backend-contract.js`,新增一条必跑条目),而该契约**压在本仓身上**:
- * core 只养 File backend,Pg / TiDB 两方言归 server。提货当天真双库实跑的红读数(A-002.21 教训的
+ * core 只养 File backend,Pg / TiDB 两方言归 server。提货当天真双库实跑的红读数([ref] 教训的
  * 直接兑现,不是自我声明「本批无 SQL 面」):
- *   `[engine=tidb] contract case "design/336: origin marker round-trips; …":
+ *   `[engine=tidb] contract case "[ref]: origin marker round-trips; …":
  *    an origin-stripping update must not apply — 1 !== 0`
  * ⇒ 两只 SQL 孪生此前**没有**这条法:一条被标记为外部来源的记忆条目,可以被后续一次普通 update
  * 悄悄抹掉标记(洗白),而 File backend 会拒。这是安全轴上的真缺口,不是「新契约还没接」。
@@ -38,7 +38,7 @@
  */
 import { type MemoryEntryFrontmatter, type MemoryEntryHeader } from "@sema-agent/core";
 /**
- * #319 增量(sema-comms [4768] 勘误 + core 仓 `1a5ebaa1`,conformance 30→31)—— **歧义 origin 表示**
+ * [ref] 增量(sema-comms [ref] 勘误 + core 仓 `1a5ebaa1`,conformance 30→31)—— **歧义 origin 表示**
  * 的拒绝门,与不可变律同批、同一个写路径上。
  *
  * ## 病
@@ -58,8 +58,8 @@ import { type MemoryEntryFrontmatter, type MemoryEntryHeader } from "@sema-agent
  * ## 判据禁手抄
  *
  * 谓词一律用 core 导出的 {@link ambiguousOriginRepresentation}:它要解 `extra` 里的 origin 形块
- * (跨块字段组合、解析期块重排都算歧义),自己写一份近似的等于给洗白开口子 —— 这条在 #307 就写死过。
- * core 5.47.0 起该谓词进公开导出面([4698] 请托兑现),本仓的「撤除条件钉」也因此在 5.47 提货当天
+ * (跨块字段组合、解析期块重排都算歧义),自己写一份近似的等于给洗白开口子 —— 这条在 [ref] 就写死过。
+ * core 5.47.0 起该谓词进公开导出面([ref] 请托兑现),本仓的「撤除条件钉」也因此在 5.47 提货当天
  * 准时翻红,本批就是那条钉指定的兑现动作。
  *
  * ## 文案与 File 逐字同
@@ -75,7 +75,7 @@ import { type MemoryEntryFrontmatter, type MemoryEntryHeader } from "@sema-agent
  */
 export declare function ambiguousOriginRefusal(fm: MemoryEntryFrontmatter): string | undefined;
 /**
- * #319(core 5.47/5.48 契约冻结面,design/336 §5.2)—— **头面 exposure 事实**的同一份归一化。
+ * [ref](core 5.47/5.48 契约冻结面,[ref] §5.2)—— **头面 exposure 事实**的同一份归一化。
  *
  * 契约逐字:`listHeaders` 与 `search` 两个头面都要携带 `exposure`,且**同一条归一化**
  * (`committedOriginOf`:typed `frontmatter.origin` 与 legacy 的 `extra` origin 形字节块两种承载,
@@ -109,7 +109,7 @@ export declare function originMarkedSqlPredicate(column: string): string;
 /**
  * 本批次的「已提交 frontmatter」基线:id → 本批**第一次**触碰它时库里那一份(无行 ⇒ `undefined`)。
  *
- * #337(core 5.55.0 conformance c35-c40,design/339)从「只记 origin」升为记**整份** committed
+ * [ref](core 5.55.0 conformance c35-c40,[ref])从「只记 origin」升为记**整份** committed
  * frontmatter:origin 不可变律与 distilled 不可变律读的是同一份基线,将来第三个不可变 frontmatter
  * 字段进契约时零基线改动 —— 两只平行 Map 就是 F1a(姊妹腿)的温床,一只忘了在 delete 腿记账,
  * 那一律的「同批 delete+re-add 拒」就静默失效。
@@ -136,14 +136,14 @@ export declare function rememberBatchCommitted(baseline: BatchCommittedBaseline,
  *
  * 今日可达性(如实):本仓唯一的调用点 `src/memory-sync.ts` 自己铸 op(基线有 ⇒ update、无 ⇒ add),
  * 词表外的值到不了。所以这条是**加固**而不是在修一次已发生的事故 —— 但它落在安全轴(白洗守卫的
- * 有效性完全依赖「op 只有三种」这个未被检查的前提),按 CLAUDE.md #157「闭集 + 不可避免的运行期
+ * 有效性完全依赖「op 只有三种」这个未被检查的前提),按 CLAUDE.md [ref]「闭集 + 不可避免的运行期
  * miss 臂必须说出来」补一道显式拒绝:未知 op **零写**,报 `malformed patch refused`(与本仓既有的
  * id-mismatch 拒绝同族文案,消费方按同一条正则分类)。
  */
 export declare function unknownPatchOpRefusal(op: string): string | undefined;
 export declare function originWhitewashRefusal(op: "add" | "update", committedFm: MemoryEntryFrontmatter | undefined, next: MemoryEntryFrontmatter): string | undefined;
 /**
- * #337(core 5.55.0 conformance c36/c37,design/339)—— **distilled 血统不可变律**的判据,与 origin
+ * [ref](core 5.55.0 conformance c36/c37,[ref])—— **distilled 血统不可变律**的判据,与 origin
  * 律同族同基线同判位:一旦某 id 的已提交状态带 `frontmatter.distilled` 块(consolidation 蒸馏产物的
  * 血统:planId/at/carrierRev/inputs),任何 update / 裸 add / guard add / 同批 delete+re-add 都必须把
  * 它 DEEP-EQUAL 地带下去,否则拒 —— 合法出口只有已提交的墓碑(c36 逐字)。判序:**先于 rev CAS**
@@ -153,7 +153,7 @@ export declare function originWhitewashRefusal(op: "add" | "update", committedFm
  */
 export declare function distilledWhitewashRefusal(op: "add" | "update", committedFm: MemoryEntryFrontmatter | undefined, next: MemoryEntryFrontmatter): string | undefined;
 /**
- * #337(conformance c38)—— **distilled 事实的头面携带**,与 {@link exposureCarriage} 同住同因:
+ * [ref](conformance c38)—— **distilled 事实的头面携带**,与 {@link exposureCarriage} 同住同因:
  * `listHeaders` 与 `search` 两个头面都携带 `{ carrierRev, supersedes }` 投影(supersedes = inputs 中
  * `superseded === true` 的行,形状与 core File backend 的 header 投影逐字同);无块条目两面都不携带。
  * 蒸馏产物的「取代了哪些输入行」必须在检索面可见,否则被取代的旧行与蒸馏产物在读侧无从判序。

package/dist/plugins/memory-run-store.d.ts

@@ -15,13 +15,13 @@ import type { TaskResult, TaskStatus } from "@sema-agent/core";
 import type { RunRecord, SessionSummary, RunEvent } from "./store-contracts.js";
 import type { LedgerEventType } from "../trace/ledger-events.js";
 /**
- * [868] P0 — the local lane's stand-in for the SQL twins' checkpoint-table JOIN. The file/memory run stores
+ * [ref] P0 — the local lane's stand-in for the SQL twins' checkpoint-table JOIN. The file/memory run stores
  * cannot JOIN `checkpoint` (separate store, separate files), so the suspended-run reapers were NO-OPs — which
  * left a durable HITL park whose approval was never answered holding the task_active claim FOREVER (the
  * "suspended run locks the session" incident: every later submit 409s and no reaper path releases it).
  * The backend assembly (store-backend.ts local lane, where checkpoint + run store are built side by side)
  * injects this probe so the reapers get the SAME two predicates the SQL twins express as EXISTS subqueries:
- *  - hasPending  = EXISTS (checkpoint c WHERE c.session_id = ? AND c.status = 'pending')  — the design/80 D-D
+ *  - hasPending  = EXISTS (checkpoint c WHERE c.session_id = ? AND c.status = 'pending')  — the [ref] D-D
  *    NOT-EXISTS-pending guard: a row whose checkpoint is STILL pending is owned by the checkpoint-state-driven
  *    sweeps and must NEVER be time-reaped (else two-runs-one-session, see run-store-sql.ts reapSuspended doc).
  *  - hasExpired  = EXISTS (checkpoint ce WHERE ce.session_id = ? AND ce.status = 'expired') — the
@@ -39,9 +39,9 @@ export declare class MemoryRunStore {
     private readonly active;
     /** taskId → events (kept seq-sorted on read). */
     private readonly events;
-    /** [868] the checkpoint-table stand-in (see {@link RunStoreCheckpointProbe}); absent ⇒ reapers NO-OP. */
+    /** [ref] the checkpoint-table stand-in (see {@link RunStoreCheckpointProbe}); absent ⇒ reapers NO-OP. */
     private checkpointProbe?;
-    /** [868] wire the checkpoint probe (backend assembly, where checkpoint + run store are built together). */
+    /** [ref] wire the checkpoint probe (backend assembly, where checkpoint + run store are built together). */
     setCheckpointProbe(probe: RunStoreCheckpointProbe): void;
     private toRecord;
     /** Create a run iff the session has no active run (the task_active unique-key claim). */
@@ -64,15 +64,15 @@ export declare class MemoryRunStore {
     maxSeq(taskId: string): Promise<number>;
     retainedFrom(taskId: string): Promise<number>;
     getEvents(taskId: string, afterSeq: number): Promise<RunEvent[]>;
-    /** [888] FIRST terminal writer wins(SQL 孪生同款正向 CAS on running/suspended/needs_review,
+    /** [ref] FIRST terminal writer wins(SQL 孪生同款正向 CAS on running/suspended/needs_review,
      *  [1.207 codex M1] 负向形漏 blocked/timeout);claim 释放保持无条件(幂等)。 */
     setTerminal(taskId: string, status: TaskStatus, result: TaskResult | null, error: string | null): Promise<void>;
     /** Durable F4: park NON-terminal `suspended`, KEEP the task_active claim. CAS on running/suspended (reaper-revert guard). */
     setSuspended(taskId: string): Promise<void>;
-    /** design/80 D-B: park NON-terminal `needs_review`, KEEP the claim. CAS on running/needs_review. */
+    /** [ref] D-B: park NON-terminal `needs_review`, KEEP the claim. CAS on running/needs_review. */
     setNeedsReview(taskId: string): Promise<void>;
     /** Durable F4 resume: flip suspended/needs_review → running (CAS) + reset cancel/preempt flags.
-     *  S-51(codex R1 [medium]):认领 = 接管 `instanceId`(= 当前持有副本;SQL 孪生同注)。CAS 输不改。 */
+     *  [ref](codex R1 [medium]):认领 = 接管 `instanceId`(= 当前持有副本;SQL 孪生同注)。CAS 输不改。 */
     markResuming(taskId: string, instanceId: string): Promise<boolean>;
     getActiveTaskId(sessionId: string): Promise<string | undefined>;
     getRun(taskId: string): Promise<RunRecord | undefined>;
@@ -130,25 +130,25 @@ export declare class MemoryRunStore {
     }>>;
     /** Fail stale `running` rows (crashed-run backstop) + release task_active for any now-terminal row. */
     reapStale(olderThanMs: number): Promise<number>;
-    /** [868] shared tail of both suspended-run reapers: flip one parked row → failed('approval.expired'), the
+    /** [ref] shared tail of both suspended-run reapers: flip one parked row → failed('approval.expired'), the
      *  in-memory twin of the SQL UPDATE (`error`/`error_code` set directly — no result blob to derive from). */
     private failExpiredPark;
     /** Release the claim for TERMINAL rows only — suspended/needs_review keep it (the `DELETE ta … WHERE tr.status
-     *  NOT IN ('running','suspended','needs_review')` twin, shared by reapStale + the [868] suspended reapers). */
+     *  NOT IN ('running','suspended','needs_review')` twin, shared by reapStale + the [ref] suspended reapers). */
     private releaseTerminalClaims;
     /**
-     * [868] Durable F4 expiry — the local twin of TiDBRunStore.reapSuspended, driven by the injected checkpoint
+     * [ref] Durable F4 expiry — the local twin of TiDBRunStore.reapSuspended, driven by the injected checkpoint
      * probe instead of a SQL JOIN (formerly a NO-OP, which was one of the five closed doors in the "suspended run
      * locks the session forever" incident). Semantics verbatim from the SQL twin: suspended ∧ updatedAt < cutoff
      * ∧ NOT probe.hasPending(session) → failed 'approval expired before decision' / error_code 'approval.expired'
-     * + release the task_active claim. The NOT-pending clause is the design/80 D-D blocker guard
+     * + release the task_active claim. The NOT-pending clause is the [ref] D-D blocker guard
      * (SQL 孪生现在的真身:`run-store-sql.ts` 的 `reapSuspended`;`tidb-run-store.ts` 该壳文件已删(5.0.0)): a row whose checkpoint is STILL pending belongs to the checkpoint-state
      * sweeps (SLA deny-sweep / failSuspendedWithExpiredCheckpoint) — time-reaping it here would orphan a model
      * leg on a now-unlocked session. Probe absent ⇒ honest NO-OP (never kill a park without the guard).
      */
     reapSuspended(olderThanMs: number): Promise<number>;
     /**
-     * [868] design/80 §3 inv#3 crash-safe backstop — the local twin of TiDBRunStore.failSuspendedWithExpiredCheckpoint
+     * [ref] [ref] §3 inv#3 crash-safe backstop — the local twin of TiDBRunStore.failSuspendedWithExpiredCheckpoint
      * (checkpoint-STATE-driven, not time-driven; runs UNCONDITIONALLY every reaper tick, no APPROVAL_TIMEOUT_SEC gate).
      * Semantics verbatim from the SQL twin: (suspended ∨ needs_review) ∧ probe.hasExpired(session) ∧ NOT
      * probe.hasPending(session) → same fail + claim release. The NOT-pending clause covers a re-suspended session

package/dist/plugins/outcome-ledger-sql.d.ts

@@ -49,7 +49,7 @@ export interface TaskOutcome {
     signatureInputs: SignatureInputs;
     mechanical: MechanicalOutcome;
     llmAssisted?: LlmAssistedOutcome;
-    /** design/73 §1 consumption: the VERBATIM core `TaskOutcome` fact this row was derived from (status/
+    /** [ref] §1 consumption: the VERBATIM core `TaskOutcome` fact this row was derived from (status/
      *  errorCode/oracleHadRedRun/oracle blob — fields the v1 columns predate). Stored as-is in `core_outcome`
      *  so red-line ② (`oracleHadRedRun`) and the free-form oracle survive lossless; the mapped mechanical
      *  columns stay the aggregate/query surface. */
@@ -67,7 +67,7 @@ export declare function taskSignature(s: SignatureInputs): string;
  */
 export declare function deriveOutcome(m: MechanicalOutcome, runStatus?: RunStatus): "pass" | "partial" | "fail" | "aborted";
 /**
- * design/73 §1 → §7 bridge: project one CORE `TaskOutcome` fact (the `RunnerDeps.onTaskOutcome` seam,
+ * [ref] §1 → §7 bridge: project one CORE `TaskOutcome` fact (the `RunnerDeps.onTaskOutcome` seam,
  * core 1.226) onto a v1 ledger row. Lossless: the verbatim fact rides `core` → the `core_outcome` JSON
  * column (red-line ② `oracleHadRedRun` + the free-form oracle blob have no v1 columns); the mapped
  * mechanical fields keep the existing aggregate surface working. Mapping rules:
@@ -103,7 +103,7 @@ export declare class SqlOutcomeLedger {
     private json;
     /** Record one graded task run. Idempotent only by row id; callers pass distinct runs. */
     record(o: TaskOutcome): Promise<string>;
-    /** design/73 §1 seam consumption: record one CORE outcome fact (see {@link coreOutcomeToLedgerRow}). */
+    /** [ref] §1 seam consumption: record one CORE outcome fact (see {@link coreOutcomeToLedgerRow}). */
     recordCore(o: CoreTaskOutcome): Promise<void>;
     /**
      * Read-only aggregate for the dashboard / offline backtest: pass-rate + mean cost per (signature, model).

package/dist/plugins/permission-rule-store-file.d.ts

@@ -58,12 +58,12 @@ export declare class FileRuleImportTicketStore {
      *  (理由逐字见 SQL 侧 `release` 的头注:承诺一次必然兑现不了的重试比不承诺更坏)。
      *  `claimId` = A7 的认领围栏(R1-F1):被顶替的旧持有者动不了现持有者的认领。 */
     release(ticketId: string, principal: string, claimId: string, mustRemainValidMs?: number, opts?: RuleTicketDecisionClock): Promise<boolean>;
-    /** #265 A7 CLAIMED → **SETTLED**。判据与 SQL 孪生逐字同源(持有**这一代**认领 ∧ 未落定;过期
+    /** [ref] A7 CLAIMED → **SETTLED**。判据与 SQL 孪生逐字同源(持有**这一代**认领 ∧ 未落定;过期
      *  **刻意不设门** —— 理由逐字见 SQL 侧 `settle` 的头注:拒绝记录一件已经发生的事只会把真相丢掉)。 */
     settle(ticketId: string, principal: string, claimId: string, outcome: unknown): Promise<boolean>;
-    /** #265 A7 三态快照。属主门与车道门同源(别人的票 / 别条车道的票 / 不存在的票一律 `undefined`)。 */
+    /** [ref] A7 三态快照。属主门与车道门同源(别人的票 / 别条车道的票 / 不存在的票一律 `undefined`)。 */
     peek(ticketId: string, principal: string, purpose: RuleTicketPurpose): Promise<RuleTicketSnapshot | undefined>;
-    /** #265 A7 崩溃窗恢复:抢过一次**可证陈旧**的认领(判据与 SQL 孪生逐字同源 —— 含"过期刻意不设门"
+    /** [ref] A7 崩溃窗恢复:抢过一次**可证陈旧**的认领(判据与 SQL 孪生逐字同源 —— 含"过期刻意不设门"
      *  那一条:过期只挡开始一次兑付,不挡做完一次已经开始的)。抢到之后**换一代认领**。 */
     reclaim(ticketId: string, principal: string, purpose: RuleTicketPurpose, minClaimAgeMs: number): Promise<RuleTicketReclaimResult>;
 }