@sema-agent/server 7.2.0 → 7.4.0

package/dist/plugins/pg-resume-anchor-store.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation moved to the single-file
+ * dual-dialect `resume-anchor-store-sql.ts` (shared with the TiDB twin via `SqlDriver`). Kept so
+ * consumers importing this path (store-backend.ts, the resume-anchor integration suite) don't move.
+ */
+export { PgResumeAnchorStore } from "./resume-anchor-store-sql.js";
+//# sourceMappingURL=pg-resume-anchor-store.d.ts.map

package/dist/plugins/pg-resume-anchor-store.js

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation moved to the single-file
+ * dual-dialect `resume-anchor-store-sql.ts` (shared with the TiDB twin via `SqlDriver`). Kept so
+ * consumers importing this path (store-backend.ts, the resume-anchor integration suite) don't move.
+ */
+export { PgResumeAnchorStore } from "./resume-anchor-store-sql.js";
+//# sourceMappingURL=pg-resume-anchor-store.js.map

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

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 定型半场 collapse): the real implementation now lives in
+ * `run-store-sql.ts` (single-file dual-dialect — TiDB + PG share one `SqlRunStore` body, dialect deltas
+ * kept EXPLICIT per statement). `PgRunStore`'s class name/ctor arity is unchanged so every existing
+ * consumer (store-backend.ts, the reaper/session integration suites) needs ZERO changes. New code
+ * should import from `run-store-sql.ts` directly.
+ */
+export { PgRunStore } from "./run-store-sql.js";
+//# sourceMappingURL=pg-run-store.d.ts.map

package/dist/plugins/pg-run-store.js

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 定型半场 collapse): the real implementation now lives in
+ * `run-store-sql.ts` (single-file dual-dialect — TiDB + PG share one `SqlRunStore` body, dialect deltas
+ * kept EXPLICIT per statement). `PgRunStore`'s class name/ctor arity is unchanged so every existing
+ * consumer (store-backend.ts, the reaper/session integration suites) needs ZERO changes. New code
+ * should import from `run-store-sql.ts` directly.
+ */
+export { PgRunStore } from "./run-store-sql.js";
+//# sourceMappingURL=pg-run-store.js.map

package/dist/plugins/pg-session-policy-store.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation lives in the single-file
+ * dual-dialect `session-policy-store-sql.ts` (`SqlSessionPolicyStore` + this file's historical
+ * `PgSessionPolicyStore` ctor subclass). Kept so every consumer's import path is untouched.
+ */
+export { PgSessionPolicyStore } from "./session-policy-store-sql.js";
+//# sourceMappingURL=pg-session-policy-store.d.ts.map

package/dist/plugins/pg-session-policy-store.js

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation lives in the single-file
+ * dual-dialect `session-policy-store-sql.ts` (`SqlSessionPolicyStore` + this file's historical
+ * `PgSessionPolicyStore` ctor subclass). Kept so every consumer's import path is untouched.
+ */
+export { PgSessionPolicyStore } from "./session-policy-store-sql.js";
+//# sourceMappingURL=pg-session-policy-store.js.map

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

@@ -0,0 +1,12 @@
+/**
+ * Compatibility re-export shim — the PG Session event-log center (L1).
+ *
+ * 🔴 SINGLE SOURCE OF TRUTH: the real PG twin (PgSessionStorage + PgSessionStore + PG_SESSION_SCHEMA +
+ * ensureSchema) lives in {@link ./pg-session-storage.ts}. This file previously carried a SECOND, byte-for-byte
+ * copy of that same code — a dual source of truth that would silently drift (a fix to one copy leaving the
+ * other stale, defeating the very twin/lock-step invariant the integration suite exists to protect). The
+ * duplicate has been collapsed: everything is now re-exported from the one storage module so there is exactly
+ * ONE PG implementation and the two integration suites both exercise it.
+ */
+export { PgSessionStorage, PgSessionStore, PG_SESSION_SCHEMA, ensureSchema, } from "./pg-session-storage.js";
+//# sourceMappingURL=pg-session-store.d.ts.map

package/dist/plugins/pg-session-store.js

@@ -0,0 +1,12 @@
+/**
+ * Compatibility re-export shim — the PG Session event-log center (L1).
+ *
+ * 🔴 SINGLE SOURCE OF TRUTH: the real PG twin (PgSessionStorage + PgSessionStore + PG_SESSION_SCHEMA +
+ * ensureSchema) lives in {@link ./pg-session-storage.ts}. This file previously carried a SECOND, byte-for-byte
+ * copy of that same code — a dual source of truth that would silently drift (a fix to one copy leaving the
+ * other stale, defeating the very twin/lock-step invariant the integration suite exists to protect). The
+ * duplicate has been collapsed: everything is now re-exported from the one storage module so there is exactly
+ * ONE PG implementation and the two integration suites both exercise it.
+ */
+export { PgSessionStorage, PgSessionStore, PG_SESSION_SCHEMA, ensureSchema, } from "./pg-session-storage.js";
+//# sourceMappingURL=pg-session-store.js.map

package/dist/plugins/pg-tool-result-store.d.ts

@@ -0,0 +1,9 @@
+/**
+ * PostgreSQL `ToolResultStore` — the implementation now lives in the single-file dual-dialect
+ * `tool-result-store-sql.ts` (design/158 A12 定型半场), the TiDB twin's sibling
+ * (src/plugins/tidb-tool-result-store.ts). This file is the historical import path: the class name, ctor
+ * shape, and the PG-only schema helpers (`PG_TOOL_RESULT_SCHEMA` / `ensureSchema`, consumed by pg-pool.ts's
+ * central schema apply) are re-exported unchanged, so every consumer and suite is untouched.
+ */
+export { PgToolResultStore, PG_TOOL_RESULT_SCHEMA, ensureSchema } from "./tool-result-store-sql.js";
+//# sourceMappingURL=pg-tool-result-store.d.ts.map

package/dist/plugins/pg-tool-result-store.js

@@ -0,0 +1,9 @@
+/**
+ * PostgreSQL `ToolResultStore` — the implementation now lives in the single-file dual-dialect
+ * `tool-result-store-sql.ts` (design/158 A12 定型半场), the TiDB twin's sibling
+ * (src/plugins/tidb-tool-result-store.ts). This file is the historical import path: the class name, ctor
+ * shape, and the PG-only schema helpers (`PG_TOOL_RESULT_SCHEMA` / `ensureSchema`, consumed by pg-pool.ts's
+ * central schema apply) are re-exported unchanged, so every consumer and suite is untouched.
+ */
+export { PgToolResultStore, PG_TOOL_RESULT_SCHEMA, ensureSchema } from "./tool-result-store-sql.js";
+//# sourceMappingURL=pg-tool-result-store.js.map

package/dist/plugins/pg-workflow-journal-store.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 collapse). The real implementation is the single-file dual-dialect
+ * {@link import("./workflow-journal-store-sql.js").SqlWorkflowJournalStore} — see that file for the durable
+ * {@link WorkflowJournalStore} contract, the schema, and the TiDB/PG dialect-delta ledger. This name (and ctor
+ * arity: `(pool: PgPool)`) survives unchanged so every consumer (store-backend.ts, the extreme/integration/
+ * resume-fork-probe suites) is untouched.
+ */
+export { PgWorkflowJournalStore } from "./workflow-journal-store-sql.js";
+//# sourceMappingURL=pg-workflow-journal-store.d.ts.map

package/dist/plugins/pg-workflow-journal-store.js

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 collapse). The real implementation is the single-file dual-dialect
+ * {@link import("./workflow-journal-store-sql.js").SqlWorkflowJournalStore} — see that file for the durable
+ * {@link WorkflowJournalStore} contract, the schema, and the TiDB/PG dialect-delta ledger. This name (and ctor
+ * arity: `(pool: PgPool)`) survives unchanged so every consumer (store-backend.ts, the extreme/integration/
+ * resume-fork-probe suites) is untouched.
+ */
+export { PgWorkflowJournalStore } from "./workflow-journal-store-sql.js";
+//# sourceMappingURL=pg-workflow-journal-store.js.map

package/dist/plugins/pg-workflow-run-store.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 扇出): the PG `WorkflowRunStore`/`WorkflowCompletionInbox`/
+ * `WorkflowNotifyJournalStore` twins now live collapsed with their TiDB dialect siblings in the
+ * single-file dual-dialect `workflow-run-store-sql.ts` (design doc + dialect-delta ledger there).
+ * Class names and ctor arity stay EXACTLY as they were — every consumer (store-backend.ts, the
+ * DB-integration suite) imports from THIS path unchanged.
+ */
+export { PgWorkflowRunStore, PgWorkflowCompletionInbox, PgWorkflowNotifyJournalStore } from "./workflow-run-store-sql.js";
+//# sourceMappingURL=pg-workflow-run-store.d.ts.map

package/dist/plugins/pg-workflow-run-store.js

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 扇出): the PG `WorkflowRunStore`/`WorkflowCompletionInbox`/
+ * `WorkflowNotifyJournalStore` twins now live collapsed with their TiDB dialect siblings in the
+ * single-file dual-dialect `workflow-run-store-sql.ts` (design doc + dialect-delta ledger there).
+ * Class names and ctor arity stay EXACTLY as they were — every consumer (store-backend.ts, the
+ * DB-integration suite) imports from THIS path unchanged.
+ */
+export { PgWorkflowRunStore, PgWorkflowCompletionInbox, PgWorkflowNotifyJournalStore } from "./workflow-run-store-sql.js";
+//# sourceMappingURL=pg-workflow-run-store.js.map

package/dist/plugins/store-backend.d.ts

@@ -8,6 +8,7 @@ import { FileRunStore } from "./file-run-store.js";
 import { LocalCheckpointStore } from "./local-checkpoint-store.js";
 import { FileResumeAnchorStore } from "./file-resume-anchor-store.js";
 import { type ApprovalExemptionStore } from "./approval-exemption-store.js";
+import { type ApprovalAskStore as ApprovalAskStoreType } from "./approval-ask-store-sql.js";
 import { type SendFileLedger } from "./send-file-ledger.js";
 import { TiDBResumeAnchorStore, PgResumeAnchorStore } from "./resume-anchor-store-sql.js";
 import type { ServiceConfig } from "../config-types.js";
@@ -27,6 +28,9 @@ export type RunStore = TiDBRunStore | PgRunStore | FileRunStore;
  *  FileResumeAnchorStore is the FILE-backed local twin (P0.5 variant-1; survives restart). */
 export type ResumeAnchorStore = TiDBResumeAnchorStore | PgResumeAnchorStore | FileResumeAnchorStore;
 export type { ApprovalExemptionStore } from "./approval-exemption-store.js";
+/** #151(design/172 v3.1 §3.0-§3.2 流内审批协议持久层):`ApprovalAskStore` 接口 + 行/补丁类型。
+ *  车3 刀 3a 起 `StoreBackend.approvalAsk()` 已在(见接口体的那条注)。 */
+export type { ApprovalAskStore, AskRow, NewAskRow, AskTransitionPatch, DecideAskInput, DecideResult, ExpireResult, BindGateInput, BatchRow, AskDecision } from "./approval-ask-store-sql.js";
 /** E6 SessionPolicyStore — core's interface PLUS the service `deleteBySession` (E21 purge; only the durable twins carry
  *  it, core's InMemory omits it → optional). tidb/pg = durable twins; local = core's InMemorySessionPolicyStore (works
  *  local — rules need no cloud-only infra). The shared env-gated equivalence suite keeps the twins byte-matched to InMemory. */
@@ -107,6 +111,20 @@ export interface StoreBackend {
     /** Per-session per-toolName approval exemption ("本会话不再询问") — an approval MEMORY the F4
      *  ask-gate consults after deny/neverAuto. REQUIRED on all backends (works local, like resumeAnchor). */
     approvalExemption(): ApprovalExemptionStore;
+    /** #151(design/172 §3.0-§3.2)流内审批协议持久层:每个流内工具调用一行的 ask 状态机 + 批行。
+     *  REQUIRED on all backends — tidb/pg = SQL 双方言 twin;local = {@link InMemoryApprovalAskStore}。
+     *
+     *  🔴 local 形的代价必须在这里说清楚(而不是留给读者自己发现):InMemory 的 STREAM_PENDING/DECIDED/
+     *  PARKING 全在两个进程内 Map 里 ⇒ **重启同时丢重放基准、丢已接受的决议、丢审计**——「一次真实的人类
+     *  批准凭空消失」和「对账便利丢失」不是一个量级。因此协议在 local 车道**默认不上场**:能力面
+     *  (`streamApproval`)的判据带一条「ask 账必须是持久的」合取项,local 不报 true(诚实缺席,同
+     *  `park 设施缺席 ⇒ 协议不上场` 的姿势)。要在 local 真上协议,先落 File 形(现成模子 =
+     *  {@link FileApprovalExemptionStore}:core `AppendLog`/`readJsonlRecords`,内存索引 + 追加日志即可
+     *  满足单实例 boot-lock 下的 CAS),那时这里换成 File twin、能力面自然翻真。
+     *
+     *  无 backend 的 env-only worker 压根没有 `StoreBackend` ⇒ 协调器拿到 undefined askStore ⇒ 车2 的
+     *  D1 逐字现行为(store 缺席 = 现行 `tool_approval` 活卡腿一字不变)。 */
+    approvalAsk(): ApprovalAskStoreType;
     /** SendUserFile scope↔object ledger (multi-tenant list/revoke handle; the hashed key segment hides the
      *  mapping from URLs). REQUIRED on all backends (works local — one JSONL, like approvalExemption). */
     sendFileLedger(): SendFileLedger;

package/dist/plugins/store-backend.js

@@ -18,6 +18,8 @@ import { LocalSessionStore } from "./local-session-store.js";
 import { LocalCheckpointStore } from "./local-checkpoint-store.js";
 import { FileResumeAnchorStore } from "./file-resume-anchor-store.js";
 import { TiDBApprovalExemptionStore, PgApprovalExemptionStore, FileApprovalExemptionStore } from "./approval-exemption-store.js";
+import { TiDBApprovalAskStore, PgApprovalAskStore } from "./approval-ask-store-sql.js";
+import { InMemoryApprovalAskStore } from "./approval-ask-store-memory.js";
 import { TiDBSendFileLedger, PgSendFileLedger, FileSendFileLedger } from "./send-file-ledger.js";
 import { TiDBResumeAnchorStore, PgResumeAnchorStore } from "./resume-anchor-store-sql.js";
 import { TiDBSessionPolicyStore, PgSessionPolicyStore } from "./session-policy-store-sql.js";
@@ -94,6 +96,7 @@ class TiDBBackend {
     run() { return new TiDBRunStore(this.pool); }
     resumeAnchor() { return new TiDBResumeAnchorStore(this.pool); }
     approvalExemption() { return new TiDBApprovalExemptionStore(this.pool); }
+    approvalAsk() { return new TiDBApprovalAskStore(this.pool); } // #151 流内审批协议持久层(无状态 store,每次新建同兄弟)
     sendFileLedger() { return new TiDBSendFileLedger(this.pool); }
     sessionPolicy() { return new TiDBSessionPolicyStore(this.pool); }
     fileSnapshot() { return new TiDBFileSnapshotStore(this.pool, snapshotBlobBackend(this.config, "tidb", this.pool), snapshotBoundsFromConfig(this.config)); }
@@ -127,6 +130,7 @@ class PgBackend {
     run() { return new PgRunStore(this.pool); }
     resumeAnchor() { return new PgResumeAnchorStore(this.pool); }
     approvalExemption() { return new PgApprovalExemptionStore(this.pool); }
+    approvalAsk() { return new PgApprovalAskStore(this.pool); } // #151 流内审批协议持久层(SQL twin)
     sendFileLedger() { return new PgSendFileLedger(this.pool); }
     sessionPolicy() { return new PgSessionPolicyStore(this.pool); }
     fileSnapshot() { return new PgFileSnapshotStore(this.pool, snapshotBlobBackend(this.config, "pg", this.pool), snapshotBoundsFromConfig(this.config)); }
@@ -178,6 +182,8 @@ class LocalBackend {
     sessionStore;
     resumeAnchorStore;
     approvalExemptionStore;
+    /** #151 —— 进程内易失(见 approvalAsk() 的注);File 形落地前它就是 local 车道的占位。 */
+    approvalAskStore = new InMemoryApprovalAskStore();
     sendFileLedgerStore;
     // SVC-2: FILE-backed durable journal (was core's InMemory — a TOC restart silently resolved
     // resumeFromRunId to an empty journal → full live re-run). Now restart-durable on one box; crash-safe JSONL,
@@ -223,6 +229,10 @@ class LocalBackend {
     run() { return this.runStore; }
     resumeAnchor() { return this.resumeAnchorStore; } // singleton — state lives in the instance (mirrors run()/session())
     approvalExemption() { return this.approvalExemptionStore; } // singleton — same posture
+    /** #151 流内审批协议持久层的 local 形。**必须**是 singleton:状态全在实例的两个 Map 里,每次
+     *  new 一个就等于每个消费者各拿一份互不可见的账(而 SQL twin 天然共享一张表)。易失代价 +
+     *  「local 车道默认不上协议」的裁定见 StoreBackend.approvalAsk() 的接口注。 */
+    approvalAsk() { return this.approvalAskStore; }
     sendFileLedger() { return this.sendFileLedgerStore; } // singleton — append fd lives in the instance
     /** Durable HITL / plan-review parking on the LOCAL lane. Lazy singleton (the inner core store holds
      *  an append fd). taskId join ← FileRunStore; E21 owner guard ← LocalSessionStore.ownerOf (same root). */

package/dist/plugins/tidb-approval-store.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Thin re-export shim (design/158 A12 收编 — see src/plugins/approval-store-sql.ts for the
+ * implementation, now SINGLE-FILE DUAL-DIALECT). Class name, ctor arity, and every exported
+ * type/helper stay EXACTLY as they were so no consumer (store-backend.ts, src/index.ts, the
+ * approval/audit/security-coverage suites) has to move.
+ */
+export { TiDBApprovalStore, mapRow, type ApprovalRow, type ApprovalStatus, } from "./approval-store-sql.js";
+//# sourceMappingURL=tidb-approval-store.d.ts.map

package/dist/plugins/tidb-approval-store.js

@@ -0,0 +1,8 @@
+/**
+ * Thin re-export shim (design/158 A12 收编 — see src/plugins/approval-store-sql.ts for the
+ * implementation, now SINGLE-FILE DUAL-DIALECT). Class name, ctor arity, and every exported
+ * type/helper stay EXACTLY as they were so no consumer (store-backend.ts, src/index.ts, the
+ * approval/audit/security-coverage suites) has to move.
+ */
+export { TiDBApprovalStore, mapRow, } from "./approval-store-sql.js";
+//# sourceMappingURL=tidb-approval-store.js.map

package/dist/plugins/tidb-breaker-state.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Re-export shim (design/158 A12 收编) — the real implementation moved to breaker-state-sql.ts
+ * (single-file dual-dialect: `SqlBreakerState` + the `TiDBBreakerState`/`PgBreakerState` ctor subclasses).
+ * Kept so every consumer's `from "./tidb-breaker-state.js"` import keeps working unchanged.
+ */
+export { TiDBBreakerState } from "./breaker-state-sql.js";
+//# sourceMappingURL=tidb-breaker-state.d.ts.map

package/dist/plugins/tidb-breaker-state.js

@@ -0,0 +1,7 @@
+/**
+ * Re-export shim (design/158 A12 收编) — the real implementation moved to breaker-state-sql.ts
+ * (single-file dual-dialect: `SqlBreakerState` + the `TiDBBreakerState`/`PgBreakerState` ctor subclasses).
+ * Kept so every consumer's `from "./tidb-breaker-state.js"` import keeps working unchanged.
+ */
+export { TiDBBreakerState } from "./breaker-state-sql.js";
+//# sourceMappingURL=tidb-breaker-state.js.map

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

@@ -0,0 +1,9 @@
+/**
+ * MySQL-protocol (TiDB) `CheckpointStore` — the implementation now lives in the single-file dual-dialect
+ * `checkpoint-store-sql.ts` (design/158 A12 定型半场). This file is the historical import path: the class
+ * name, ctor shape and the backend-NEUTRAL helpers the LOCAL twin shares (TERMINAL_BACKSTOP_MS /
+ * TERMINAL_GRACE_MS / tokenFingerprint / boundedToolInput / PendingCheckpoint) are re-exported unchanged,
+ * so local-checkpoint-store.ts, store-backend.ts, the dogfood script and every suite are untouched.
+ */
+export { TiDBCheckpointStore, SqlCheckpointStore, TERMINAL_BACKSTOP_MS, TERMINAL_GRACE_MS, tokenFingerprint, boundedToolInput, type PendingCheckpoint, } from "./checkpoint-store-sql.js";
+//# sourceMappingURL=tidb-checkpoint-store.d.ts.map

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

@@ -0,0 +1,9 @@
+/**
+ * MySQL-protocol (TiDB) `CheckpointStore` — the implementation now lives in the single-file dual-dialect
+ * `checkpoint-store-sql.ts` (design/158 A12 定型半场). This file is the historical import path: the class
+ * name, ctor shape and the backend-NEUTRAL helpers the LOCAL twin shares (TERMINAL_BACKSTOP_MS /
+ * TERMINAL_GRACE_MS / tokenFingerprint / boundedToolInput / PendingCheckpoint) are re-exported unchanged,
+ * so local-checkpoint-store.ts, store-backend.ts, the dogfood script and every suite are untouched.
+ */
+export { TiDBCheckpointStore, SqlCheckpointStore, TERMINAL_BACKSTOP_MS, TERMINAL_GRACE_MS, tokenFingerprint, boundedToolInput, } from "./checkpoint-store-sql.js";
+//# sourceMappingURL=tidb-checkpoint-store.js.map

package/dist/plugins/tidb-file-snapshot-store.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Thin re-export shim (design/158 A12 定型半场) — the real implementation collapsed into
+ * `file-snapshot-store-sql.ts` (single file, dual dialect). Kept so every existing import path
+ * (store-backend.ts, the migration script, the contract/integration/minio-equivalence suites) is
+ * untouched: same class name, same ctor arity, same exported surface.
+ */
+export { TiDBFileSnapshotStore } from "./file-snapshot-store-sql.js";
+//# sourceMappingURL=tidb-file-snapshot-store.d.ts.map

package/dist/plugins/tidb-file-snapshot-store.js

@@ -0,0 +1,8 @@
+/**
+ * Thin re-export shim (design/158 A12 定型半场) — the real implementation collapsed into
+ * `file-snapshot-store-sql.ts` (single file, dual dialect). Kept so every existing import path
+ * (store-backend.ts, the migration script, the contract/integration/minio-equivalence suites) is
+ * untouched: same class name, same ctor arity, same exported surface.
+ */
+export { TiDBFileSnapshotStore } from "./file-snapshot-store-sql.js";
+//# sourceMappingURL=tidb-file-snapshot-store.js.map

package/dist/plugins/tidb-image-bake.d.ts

@@ -0,0 +1,12 @@
+/**
+ * MySQL-protocol (TiDB) BAKE store — the implementation now lives in the single-file dual-dialect
+ * `image-bake-store-sql.ts` (design/158 A12 定型半场). This file is the historical import path: the
+ * class name, ctor shape and every re-exported contract are unchanged, so no consumer moved.
+ *
+ * New code should import from `./image-bake-store-sql.js` (both dialects) and take its CONTRACTS from
+ * `./store-contracts.js` (backend-neutral, design/158 A3 沉底).
+ */
+export { TiDBImageBake, SqlImageBake } from "./image-bake-store-sql.js";
+export type { BakeStatus, BakeState, BakeErrorCode, BakeRecord, BakeEvent, CreateBakeInput, BakeTerminal, BakeRow, } from "./store-contracts.js";
+export { mapBakeRow as mapRow, BAKE_SELECT_COLS as SELECT_COLS } from "./store-contracts.js";
+//# sourceMappingURL=tidb-image-bake.d.ts.map

package/dist/plugins/tidb-image-bake.js

@@ -0,0 +1,11 @@
+/**
+ * MySQL-protocol (TiDB) BAKE store — the implementation now lives in the single-file dual-dialect
+ * `image-bake-store-sql.ts` (design/158 A12 定型半场). This file is the historical import path: the
+ * class name, ctor shape and every re-exported contract are unchanged, so no consumer moved.
+ *
+ * New code should import from `./image-bake-store-sql.js` (both dialects) and take its CONTRACTS from
+ * `./store-contracts.js` (backend-neutral, design/158 A3 沉底).
+ */
+export { TiDBImageBake, SqlImageBake } from "./image-bake-store-sql.js";
+export { mapBakeRow as mapRow, BAKE_SELECT_COLS as SELECT_COLS } from "./store-contracts.js";
+//# sourceMappingURL=tidb-image-bake.js.map

package/dist/plugins/tidb-image-index.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Sandbox-image-pool INDEX store (IMAGE-API-DESIGN.md §1, pool design §8).
+ *
+ * Thin re-export shim (design/158 A12 定型半场): the real implementation is the single-file dual-dialect
+ * `image-index-sql.ts` (`SqlImageIndex` + this file's `TiDBImageIndex` ctor subclass). Class name, ctor
+ * arity, and the exported type/helper surface are UNCHANGED — every consumer (store-backend.ts, the unit +
+ * real-DB integration suites) imports from here exactly as before.
+ */
+export { TiDBImageIndex } from "./image-index-sql.js";
+export type { ImageNestedBuildMode, ImageCapabilities, ImagePodContract, ImageStatus, ImageVisibility, ImageIndexEntry, ImageIndexUpsert, ImageViewer, ImageListFilter, ImageRow, } from "./store-contracts.js";
+export { mapImageRow as mapRow } from "./store-contracts.js";
+//# sourceMappingURL=tidb-image-index.d.ts.map

package/dist/plugins/tidb-image-index.js

@@ -0,0 +1,11 @@
+/**
+ * Sandbox-image-pool INDEX store (IMAGE-API-DESIGN.md §1, pool design §8).
+ *
+ * Thin re-export shim (design/158 A12 定型半场): the real implementation is the single-file dual-dialect
+ * `image-index-sql.ts` (`SqlImageIndex` + this file's `TiDBImageIndex` ctor subclass). Class name, ctor
+ * arity, and the exported type/helper surface are UNCHANGED — every consumer (store-backend.ts, the unit +
+ * real-DB integration suites) imports from here exactly as before.
+ */
+export { TiDBImageIndex } from "./image-index-sql.js";
+export { mapImageRow as mapRow } from "./store-contracts.js";
+//# sourceMappingURL=tidb-image-index.js.map

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

@@ -0,0 +1,12 @@
+/**
+ * MySQL-protocol (TiDB) outcome ledger — the implementation now lives in the single-file dual-dialect
+ * `outcome-ledger-sql.ts` (design/158 A12 定型半场), alongside its PG twin so the dialect deltas
+ * (placeholders, JSON encode, the AVG boolean-coercion divergence) read side by side instead of
+ * drifting across two files.
+ *
+ * This file is the historical import path: class name, ctor shape, the shared types and the pure
+ * helpers (`taskSignature` / `deriveOutcome` / `coreOutcomeToLedgerRow`) are unchanged, so
+ * store-backend.ts, the pg twin, and every suite are untouched.
+ */
+export { TiDBOutcomeLedger, taskSignature, deriveOutcome, coreOutcomeToLedgerRow, type MechanicalOutcome, type LlmAssistedOutcome, type SignatureInputs, type RunStatus, type TaskOutcome, } from "./outcome-ledger-sql.js";
+//# sourceMappingURL=tidb-outcome-ledger.d.ts.map

package/dist/plugins/tidb-outcome-ledger.js

@@ -0,0 +1,12 @@
+/**
+ * MySQL-protocol (TiDB) outcome ledger — the implementation now lives in the single-file dual-dialect
+ * `outcome-ledger-sql.ts` (design/158 A12 定型半场), alongside its PG twin so the dialect deltas
+ * (placeholders, JSON encode, the AVG boolean-coercion divergence) read side by side instead of
+ * drifting across two files.
+ *
+ * This file is the historical import path: class name, ctor shape, the shared types and the pure
+ * helpers (`taskSignature` / `deriveOutcome` / `coreOutcomeToLedgerRow`) are unchanged, so
+ * store-backend.ts, the pg twin, and every suite are untouched.
+ */
+export { TiDBOutcomeLedger, taskSignature, deriveOutcome, coreOutcomeToLedgerRow, } from "./outcome-ledger-sql.js";
+//# sourceMappingURL=tidb-outcome-ledger.js.map

package/dist/plugins/tidb-pool.js

@@ -1,4 +1,5 @@
 import mysql from "mysql2/promise";
+import { TIDB_APPROVAL_ASK_STATEMENTS } from "./approval-ask-store-sql.js";
 /**
  * Shared TiDB (MySQL wire-compatible) connection pool for the durable Session center (L1).
  * Owned by `main.ts`; closed on shutdown.
@@ -244,11 +245,28 @@ export const SCHEMA_STATEMENTS = [
      -- D-1 TOCTOU binding guard is UNREACHABLE by the portal without it — it can then only do the unbound legacy
      -- fallback). NULL on PRE-D-1 rows ⇒ that unbound fallback.
      bound_input_hash VARCHAR(190) NULL,
-     -- pending_steer (design/80 D-A, durable steering): the parked steer ({text,trusted} JSON) set by
-     -- setPendingSteer on a STILL-PENDING checkpoint (last-writer-wins, CAS on status='pending'), surfaced via
-     -- get() as state.pendingSteer so core injects it on resume. NULL when no steer is parked.
-     -- Never touches status/resolve (design/80 inv #4).
+     -- pending_steer (design/80 D-A, durable steering):**队列化之前**的单座列,存 {text,trusted}。
+     -- core 5.14.0(#147 BREAKING)之后本服务**只读不写**它:存量行的那一座由 core readPendingSteerQueue
+     -- 折成 member 0,零迁移。NULL = 没有旧座。Never touches status/resolve (design/80 inv #4)。
      pending_steer TEXT         NULL,
+     -- pending_steer_queue:core 5.14.0(#147)的**有界有序队列**(PendingSteerEntry[] 的 JSON)。
+     -- 为什么队列另起一列、而不是把信封写回 pending_steer(codex 复审 2026-08-06 F3,采纳):滚动升级/
+     -- 回滚窗里旧副本仍在跑,它对 pending_steer 是**无条件覆盖**写 —— 队列若躺在同一列,旧副本接的下一条
+     -- steer 会把 5.14 排好的整队悄悄抹掉,正是 #147 要消灭的那种静默丢失换了个位置复发。分列之后:
+     -- 旧副本写它的单座 ⇒ 落 pending_steer,新读侧把它折成 member 0,**两边都活着**;旧副本读不到队列
+     -- 是 core 自己已披露的回滚代价(CHANGELOG:rolling back across the queue event loses steers),
+     -- 那半无法在店面消除,但**写侧互相清零**这半可以,且代价只是一个可空列。
+     -- 容量:core 的 PENDING_STEER_QUEUE_BYTE_BUDGET_BYTES = 48000 字节是对 {pendingSteer,queue} 整信封的
+     -- 硬上界(越界 fail-loud steering.queue_full,绝不驱逐)⇒ 本列恒小于它,MySQL TEXT 的 65535 字节
+     -- 够用,**不升 LONGTEXT**(core 常量注里点名「under a MySQL TEXT column with UTF-8 headroom」)。
+     pending_steer_queue TEXT   NULL,
+     -- pending_steer_rev:pending_steer_queue 列**自己**的乐观锁计数(与 resolve/reopen 的 rev 是两个轴,
+     -- 刻意不复用)。队列化之后 setPendingSteer 从「一条无条件 UPDATE」变成「读-改-写」,中间那道窗必须
+     -- 有 CAS 守着,否则两个并发 steer 各读到同一份队列、后写者把前者的条目整个盖掉。
+     -- 🔴 为什么不拿队列列的旧值当守卫:本表没有显式 COLLATE,库默认多为 *_ci —— 字符串 <=> 在大小写
+     -- 不敏感的排序规则下会把两份只差字母大小写的 JSON 判等,CAS 假命中 = 丢一条指令。整数列没有这个面。
+     -- **绝不**用它做 resolve 的 OCC:bump 它不影响 core 的 rev 语义。
+     pending_steer_rev BIGINT  NOT NULL DEFAULT 0,
      -- risk_descriptor (design/80 riskDescriptor inbox): core's INERT CheckpointGate.riskDescriptor ({severity
      -- 1-5, axes, toolName, redacted summary, touchedPaths}), stamped at put() so listPending can surface it +
      -- triage-sort the supervisor inbox by severity DESC — WITHOUT parsing the checkpoint blob per row.
@@ -602,6 +620,11 @@ export const SCHEMA_STATEMENTS = [
      pool VARCHAR(32) NOT NULL,
      PRIMARY KEY (pool)
    )`,
+    // #151(design/172)流内审批协议持久层的两张表。真源 = approval-ask-store-sql.ts 的
+    // `TIDB_APPROVAL_ASK_STATEMENTS`(那里与 PG twin 并排,方言差异一眼可对);展开进这个数组是为了让它们
+    // 跟着中央 `ensureSchema` 在 **named-lock 的那条 conn** 上建 —— 把 pool 级 ensure 函数塞进执行循环
+    // 会绕开 DDL 串行化。挂进来同时也是「这张表算生产 schema」的声明(基线导出按定义只收录被执行的语句)。
+    ...TIDB_APPROVAL_ASK_STATEMENTS,
 ];
 /** Named MySQL/TiDB advisory lock that serializes the whole `ensureSchema` DDL run (see below). */
 export const ENSURE_SCHEMA_LOCK = "sema_ensure_schema";

package/dist/plugins/tidb-resume-anchor-store.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation moved to the single-file
+ * dual-dialect `resume-anchor-store-sql.ts` (shared with the PG twin via `SqlDriver`). Kept so
+ * consumers importing this path (store-backend.ts, the resume-anchor integration suite) don't move.
+ */
+export { TiDBResumeAnchorStore } from "./resume-anchor-store-sql.js";
+//# sourceMappingURL=tidb-resume-anchor-store.d.ts.map

package/dist/plugins/tidb-resume-anchor-store.js

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation moved to the single-file
+ * dual-dialect `resume-anchor-store-sql.ts` (shared with the PG twin via `SqlDriver`). Kept so
+ * consumers importing this path (store-backend.ts, the resume-anchor integration suite) don't move.
+ */
+export { TiDBResumeAnchorStore } from "./resume-anchor-store-sql.js";
+//# sourceMappingURL=tidb-resume-anchor-store.js.map

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

@@ -0,0 +1,10 @@
+/**
+ * Thin re-export shim (design/158 A12 定型半场 collapse): the real implementation now lives in
+ * `run-store-sql.ts` (single-file dual-dialect — TiDB + PG share one `SqlRunStore` body, dialect deltas
+ * kept EXPLICIT per statement). `TiDBRunStore`'s class name/ctor arity/exported types are unchanged so
+ * every existing consumer (store-backend.ts, src/index.ts, the run/reaper/session/usage suites) needs
+ * ZERO changes. New code should import from `run-store-sql.ts` directly.
+ */
+export { TiDBRunStore } from "./run-store-sql.js";
+export type { RunRecord, SessionSummary, RunEvent } from "./store-contracts.js";
+//# sourceMappingURL=tidb-run-store.d.ts.map

package/dist/plugins/tidb-run-store.js

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 定型半场 collapse): the real implementation now lives in
+ * `run-store-sql.ts` (single-file dual-dialect — TiDB + PG share one `SqlRunStore` body, dialect deltas
+ * kept EXPLICIT per statement). `TiDBRunStore`'s class name/ctor arity/exported types are unchanged so
+ * every existing consumer (store-backend.ts, src/index.ts, the run/reaper/session/usage suites) needs
+ * ZERO changes. New code should import from `run-store-sql.ts` directly.
+ */
+export { TiDBRunStore } from "./run-store-sql.js";
+//# sourceMappingURL=tidb-run-store.js.map

package/dist/plugins/tidb-session-policy-store.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation lives in the single-file
+ * dual-dialect `session-policy-store-sql.ts` (`SqlSessionPolicyStore` + this file's historical
+ * `TiDBSessionPolicyStore` ctor subclass). Kept so every consumer's import path is untouched.
+ */
+export { TiDBSessionPolicyStore } from "./session-policy-store-sql.js";
+//# sourceMappingURL=tidb-session-policy-store.d.ts.map

package/dist/plugins/tidb-session-policy-store.js

@@ -0,0 +1,7 @@
+/**
+ * Thin re-export shim (design/158 A12 收编) — the real implementation lives in the single-file
+ * dual-dialect `session-policy-store-sql.ts` (`SqlSessionPolicyStore` + this file's historical
+ * `TiDBSessionPolicyStore` ctor subclass). Kept so every consumer's import path is untouched.
+ */
+export { TiDBSessionPolicyStore } from "./session-policy-store-sql.js";
+//# sourceMappingURL=tidb-session-policy-store.js.map

package/dist/plugins/tidb-tool-result-store.d.ts

@@ -0,0 +1,8 @@
+/**
+ * MySQL-protocol (TiDB) `ToolResultStore` — the implementation now lives in the single-file dual-dialect
+ * `tool-result-store-sql.ts` (design/158 A12 定型半场). This file is the historical import path: the class
+ * name and ctor shape are re-exported unchanged, so store-backend.ts and every suite are untouched.
+ */
+export { TiDBToolResultStore, SqlToolResultStore } from "./tool-result-store-sql.js";
+export { escapeLike } from "./sql-escape.js";
+//# sourceMappingURL=tidb-tool-result-store.d.ts.map

package/dist/plugins/tidb-tool-result-store.js

@@ -0,0 +1,10 @@
+/**
+ * MySQL-protocol (TiDB) `ToolResultStore` — the implementation now lives in the single-file dual-dialect
+ * `tool-result-store-sql.ts` (design/158 A12 定型半场). This file is the historical import path: the class
+ * name and ctor shape are re-exported unchanged, so store-backend.ts and every suite are untouched.
+ */
+export { TiDBToolResultStore, SqlToolResultStore } from "./tool-result-store-sql.js";
+// Back-compat re-export: escapeLike LIVES in sql-escape.ts (design/158 A3, backend-neutral leaf);
+// import from there in new code.
+export { escapeLike } from "./sql-escape.js";
+//# sourceMappingURL=tidb-tool-result-store.js.map

package/dist/plugins/tidb-workflow-journal-store.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 collapse). The real implementation is the single-file dual-dialect
+ * {@link import("./workflow-journal-store-sql.js").SqlWorkflowJournalStore} — see that file for the durable
+ * {@link WorkflowJournalStore} contract, the schema, and the TiDB/PG dialect-delta ledger. This name (and ctor
+ * arity: `(pool: MySqlPool)`) survives unchanged so every consumer (store-backend.ts, the extreme/integration/
+ * resume-fork-probe suites) is untouched.
+ */
+export { TiDBWorkflowJournalStore } from "./workflow-journal-store-sql.js";
+//# sourceMappingURL=tidb-workflow-journal-store.d.ts.map

package/dist/plugins/tidb-workflow-journal-store.js

@@ -0,0 +1,9 @@
+/**
+ * Thin re-export shim (design/158 A12 collapse). The real implementation is the single-file dual-dialect
+ * {@link import("./workflow-journal-store-sql.js").SqlWorkflowJournalStore} — see that file for the durable
+ * {@link WorkflowJournalStore} contract, the schema, and the TiDB/PG dialect-delta ledger. This name (and ctor
+ * arity: `(pool: MySqlPool)`) survives unchanged so every consumer (store-backend.ts, the extreme/integration/
+ * resume-fork-probe suites) is untouched.
+ */
+export { TiDBWorkflowJournalStore } from "./workflow-journal-store-sql.js";
+//# sourceMappingURL=tidb-workflow-journal-store.js.map

package/dist/plugins/tidb-workflow-run-store.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Thin re-export shim (design/158 A12 扇出): the TiDB `WorkflowRunStore`/`WorkflowCompletionInbox`/
+ * `WorkflowNotifyJournalStore` twins now live collapsed with their PG dialect siblings in the
+ * single-file dual-dialect `workflow-run-store-sql.ts`. Class names, ctor arity, and the exported
+ * `MAX_RUN_BLOB_BYTES` / `slimOversizeRun` / `InboxWarn` surface stay EXACTLY as they were — every
+ * consumer (store-backend.ts, the DB-integration + slim-oversize-run suites) imports from THIS path
+ * unchanged.
+ */
+export { MAX_RUN_BLOB_BYTES, slimOversizeRun, type InboxWarn, TiDBWorkflowRunStore, TiDBWorkflowCompletionInbox, TiDBWorkflowNotifyJournalStore, } from "./workflow-run-store-sql.js";
+//# sourceMappingURL=tidb-workflow-run-store.d.ts.map

package/dist/plugins/tidb-workflow-run-store.js

@@ -0,0 +1,10 @@
+/**
+ * Thin re-export shim (design/158 A12 扇出): the TiDB `WorkflowRunStore`/`WorkflowCompletionInbox`/
+ * `WorkflowNotifyJournalStore` twins now live collapsed with their PG dialect siblings in the
+ * single-file dual-dialect `workflow-run-store-sql.ts`. Class names, ctor arity, and the exported
+ * `MAX_RUN_BLOB_BYTES` / `slimOversizeRun` / `InboxWarn` surface stay EXACTLY as they were — every
+ * consumer (store-backend.ts, the DB-integration + slim-oversize-run suites) imports from THIS path
+ * unchanged.
+ */
+export { MAX_RUN_BLOB_BYTES, slimOversizeRun, TiDBWorkflowRunStore, TiDBWorkflowCompletionInbox, TiDBWorkflowNotifyJournalStore, } from "./workflow-run-store-sql.js";
+//# sourceMappingURL=tidb-workflow-run-store.js.map

package/dist/plugins/workflow-journal-limits.d.ts

@@ -0,0 +1,12 @@
+/**
+ * SVC-2 — the shared size bound for a journaled workflow-agent result, so all THREE backends (tidb/pg SQL
+ * twins here + core's FileWorkflowJournalStore) DEGRADE IDENTICALLY on an oversize TaskResult: skip-journal
+ * (a no-op, never insert/throw) — the agent's ordinal is simply not cached and a resume re-runs that one
+ * agent live. Rationale (TiDB ~6 MiB txn-entry-size-limit vs PG/file no such limit) documented at the source.
+ *
+ * Now a RE-EXPORT of core's copy: the constant + helper moved to core with the FileWorkflowJournalStore
+ * adoption (core 1.223.0 — core inlined them into its store file and exports both).
+ * The SQL twins import from here unchanged; one source of truth for the byte-match contract.
+ */
+export { MAX_JOURNAL_RESULT_BYTES, oversizeJournalResult } from "@sema-agent/core";
+//# sourceMappingURL=workflow-journal-limits.d.ts.map

package/dist/plugins/workflow-journal-limits.js

@@ -0,0 +1,12 @@
+/**
+ * SVC-2 — the shared size bound for a journaled workflow-agent result, so all THREE backends (tidb/pg SQL
+ * twins here + core's FileWorkflowJournalStore) DEGRADE IDENTICALLY on an oversize TaskResult: skip-journal
+ * (a no-op, never insert/throw) — the agent's ordinal is simply not cached and a resume re-runs that one
+ * agent live. Rationale (TiDB ~6 MiB txn-entry-size-limit vs PG/file no such limit) documented at the source.
+ *
+ * Now a RE-EXPORT of core's copy: the constant + helper moved to core with the FileWorkflowJournalStore
+ * adoption (core 1.223.0 — core inlined them into its store file and exports both).
+ * The SQL twins import from here unchanged; one source of truth for the byte-match contract.
+ */
+export { MAX_JOURNAL_RESULT_BYTES, oversizeJournalResult } from "@sema-agent/core";
+//# sourceMappingURL=workflow-journal-limits.js.map