@sema-agent/server 4.3.0 → 5.0.0

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

@@ -1,116 +0,0 @@
-/**
- * Durable approval store for the human-in-the-loop write gate (F4) — SINGLE-FILE DUAL-DIALECT
- * (design/158 A12 定型半场). ONE implementation, TWO dialects; the historical `TiDBApprovalStore` /
- * `PgApprovalStore` class names survive as thin ctor subclasses so every consumer (store-backend.ts,
- * src/index.ts, the approval/audit/security-coverage suites) is untouched.
- *
- * When a gated tool call is about to run, a `pending` row is recorded here; the instance running the
- * task polls it for a decision. Because the row is durable and shared, an operator's approve/deny can
- * land on ANY instance — critical under async runs + a load balancer, where the deciding request and
- * the waiting run are usually on different instances.
- *
- * Unlike the run/checkpoint PG store (whose schema is owned centrally by pg-pool.ts), this file also
- * exports a self-contained PG schema (`PG_APPROVAL_SCHEMA` + `ensureSchema`) — the `approval` table is
- * DISJOINT from the other PG stores' tables, so a CREATE IF NOT EXISTS here shadows nothing. Central
- * aggregation into pg-pool.ts composes it alongside the others. Kept in lock-step with the TiDB store
- * by the shared real-DB integration suite (test/pg-approval-store-integration.test.ts).
- *
- * ── Dialect deltas, kept EXPLICIT ────────────────────────────────────────────────────────────────────
- *   - `?` placeholders vs `$n`
- *   - null-safe scope compare: `<=>` vs `IS NOT DISTINCT FROM` (a NULL scope row — legacy/untenanted
- *     run — is matched by a NULL scope arg; one tenant's scope NEVER matches another's — the
- *     single-DB fleet read guard, defense-in-depth)
- *   - JSON binding: TiDB `JSON.stringify` verbatim vs PG `pgProtocolJsonStringify` (codex R4-H2: the
- *     persisted approval `args` is the operator's REVIEW surface and must agree byte-for-byte with the
- *     policy-executed args — a lossy/rewriting envelope would let an operator approve one payload while
- *     a different one runs)
- *   - affectedRows vs rowCount (via SqlDriver)
- *   - schema ownership: TiDB DDL lives in tidb-pool.ts SCHEMA_STATEMENTS; PG DDL is this file's own
- *     self-contained `PG_APPROVAL_SCHEMA` (see the PG twin's original header — unlike the other PG
- *     stores, `approval` is NOT centrally owned by pg-pool.ts's DDL array, only aggregated into its
- *     `ensureSchema` composition).
- *   - `getStatus` result shape: `RowDataPacket[]` (mysql2 typed query) vs a plain-record `pg` query —
- *     normalized to `SqlRow` by the shared driver, so both arms read the same field names.
- */
-import type { Pool as MySqlPool } from "mysql2/promise";
-import type { Pool as PgPool, PoolClient } from "pg";
-import { type SqlDriver } from "./sql-driver.js";
-export type ApprovalStatus = "pending" | "approved" | "denied" | "expired";
-export interface ApprovalRow {
-    id: string;
-    taskId: string | null;
-    sessionId: string | null;
-    owner: string | null;
-    /** Single-DB fleet scope guard (defense-in-depth): the run's tenant identity, owner-sourced. Reads filter on it. */
-    scope: string | null;
-    toolName: string;
-    args: unknown;
-    status: ApprovalStatus;
-    reason: string | null;
-    decidedBy: string | null;
-    createdAt: string;
-    decidedAt: string | null;
-}
-/** PG translation of the `approval` DDL in tidb-pool.ts SCHEMA_STATEMENTS (JSON→JSONB, DATETIME(3)→TIMESTAMPTZ(3),
- *  inline KEY→separate CREATE INDEX).
- *
- *  SCHEMA POLICY: see the header of pg-pool.ts — the code is the single source of truth, schema changes are
- *  drop-and-recreate, and NO new `ALTER TABLE` seams are added here; fold into the CREATE instead. */
-export declare const PG_APPROVAL_SCHEMA: string[];
-/** Idempotent self-contained schema apply (for the integration test; central aggregation is done separately). */
-export declare function ensureSchema(pool: PgPool | PoolClient): Promise<void>;
-/** Dual-dialect durable approval store. See the file header for the dialect-delta ledger. */
-export declare class SqlApprovalStore {
-    protected readonly db: SqlDriver;
-    constructor(db: SqlDriver);
-    /** Pick the dialect's SQL text. Both statements stay written out at the call site ON PURPOSE. */
-    private q;
-    /** JSON column binding: TiDB stores the string verbatim; PG goes through the LOSSLESS protocol envelope
-     *  (codex R4-H2 — the approval `args` is the operator's review surface and must agree with the
-     *  policy-executed args at the NUL position). */
-    private json;
-    createPending(id: string, scope: string | null, ctx: {
-        taskId?: string | null;
-        sessionId?: string | null;
-        owner?: string | null;
-        toolName: string;
-        args: unknown;
-    }): Promise<void>;
-    getStatus(id: string, scope: string | null): Promise<{
-        status: ApprovalStatus;
-        reason: string | null;
-        decidedBy: string | null;
-    } | undefined>;
-    /** Apply a terminal decision, but only to a still-pending row (CAS). Returns whether it applied. The scope
-     *  guard (null-safe) is carried on the operator path too for consistency with the read paths. */
-    decide(id: string, scope: string | null, decision: "approved" | "denied" | "expired", reason: string | null, decidedBy: string | null): Promise<boolean>;
-    /** Pending approvals (operator queue), scoped to one tenant (single-DB fleet read guard, null-safe), optionally
-     *  further filtered to one owner. */
-    listPending(scope: string | null, owner?: string): Promise<ApprovalRow[]>;
-    get(id: string, scope: string | null): Promise<ApprovalRow | undefined>;
-    /** Operator-only CROSS-tenant by-id read (no scope filter). The F4 operator queue serves/decides across
-     *  tenants by design; the HTTP layer gates this to an operator and then re-binds decide() to the row's OWN
-     *  scope. Tenants NEVER reach this — they use the scope-bound {@link get}. */
-    getById(id: string): Promise<ApprovalRow | undefined>;
-    /** Operator-only CROSS-tenant pending list (no scope filter) — the unfiltered operator queue across all
-     *  tenants. Tenants use the scope-bound {@link listPending}; this is HTTP-gated to an operator.
-     *  🔴 identical SQL text on both dialects (no placeholders, nothing dialect-specific) — kept as ONE literal
-     *  rather than a `q()` pair so a reader isn't misled into looking for a divergence that isn't there. */
-    listPendingAll(): Promise<ApprovalRow[]>;
-    /** Expire pending approvals older than `olderThanMs` (a never-answered operator request). Deliberately GLOBAL
-     *  (NOT scope-filtered): staleness expiry is fleet-level maintenance that protects the worker regardless of
-     *  tenant — a stale row in any scope must be reaped. Scope isolation applies to the per-tenant READ paths, not
-     *  to this maintenance sweep. */
-    expireStale(olderThanMs: number): Promise<number>;
-}
-/** approval row → {@link ApprovalRow} — shared by BOTH dialects. design/158 S8 归位 / A12 收编. */
-export declare function mapRow(r: Record<string, unknown>): ApprovalRow;
-/** MySQL-protocol (TiDB) binding — historical class name + ctor shape preserved. */
-export declare class TiDBApprovalStore extends SqlApprovalStore {
-    constructor(pool: MySqlPool);
-}
-/** PostgreSQL binding — historical class name + ctor shape preserved. */
-export declare class PgApprovalStore extends SqlApprovalStore {
-    constructor(pool: PgPool);
-}
-//# sourceMappingURL=approval-store-sql.d.ts.map

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

@@ -1,150 +0,0 @@
-import { parseJsonStrict as parseJson, toIsoOrNull as iso } from "./sql-row-helpers.js";
-import { mysqlDriver, pgDriver, dialectProtocolJsonEncoder } from "./sql-driver.js";
-/** PG translation of the `approval` DDL in tidb-pool.ts SCHEMA_STATEMENTS (JSON→JSONB, DATETIME(3)→TIMESTAMPTZ(3),
- *  inline KEY→separate CREATE INDEX).
- *
- *  SCHEMA POLICY: see the header of pg-pool.ts — the code is the single source of truth, schema changes are
- *  drop-and-recreate, and NO new `ALTER TABLE` seams are added here; fold into the CREATE instead. */
-export const PG_APPROVAL_SCHEMA = [
-    `CREATE TABLE IF NOT EXISTS approval (
-     id          VARCHAR(64)  NOT NULL,
-     task_id     VARCHAR(64),
-     session_id  VARCHAR(64),
-     owner       VARCHAR(190),
-     -- Single-DB fleet scope guard (tenant isolation). NULLABLE on purpose: a NULL-scope row is an untenanted
-     -- run, and every read/decide path matches it with \`scope IS NOT DISTINCT FROM $n\` (the PG twin of TiDB
-     -- \`<=>\`) so NULL matches only NULL and one tenant's scope NEVER matches another's.
-     scope       VARCHAR(190),
-     tool_name   VARCHAR(190) NOT NULL,
-     args        JSONB,
-     status      VARCHAR(16)  NOT NULL,
-     reason      TEXT,
-     decided_by  VARCHAR(190),
-     created_at  TIMESTAMPTZ(3) NOT NULL,
-     decided_at  TIMESTAMPTZ(3),
-     PRIMARY KEY (id)
-   )`,
-    `CREATE INDEX IF NOT EXISTS idx_approval_owner_status ON approval (owner, status)`,
-    `CREATE INDEX IF NOT EXISTS idx_approval_status ON approval (status)`,
-    `CREATE INDEX IF NOT EXISTS idx_approval_scope_status ON approval (scope, status)`,
-];
-/** Idempotent self-contained schema apply (for the integration test; central aggregation is done separately). */
-export async function ensureSchema(pool) {
-    for (const stmt of PG_APPROVAL_SCHEMA)
-        await pool.query(stmt);
-}
-/** Dual-dialect durable approval store. See the file header for the dialect-delta ledger. */
-export class SqlApprovalStore {
-    db;
-    constructor(db) {
-        this.db = db;
-    }
-    /** Pick the dialect's SQL text. Both statements stay written out at the call site ON PURPOSE. */
-    q(tidb, pg) {
-        return this.db.dialect === "tidb" ? tidb : pg;
-    }
-    /** JSON column binding: TiDB stores the string verbatim; PG goes through the LOSSLESS protocol envelope
-     *  (codex R4-H2 — the approval `args` is the operator's review surface and must agree with the
-     *  policy-executed args at the NUL position). */
-    json(value, label) {
-        return dialectProtocolJsonEncoder(this.db.dialect)(value, label);
-    }
-    async createPending(id, scope, ctx) {
-        await this.db.query(this.q("INSERT INTO approval (id, task_id, session_id, owner, scope, tool_name, args, status, created_at) " +
-            "VALUES (?,?,?,?,?,?,?,'pending',?)", "INSERT INTO approval (id, task_id, session_id, owner, scope, tool_name, args, status, created_at) " +
-            "VALUES ($1,$2,$3,$4,$5,$6,$7::jsonb,'pending',$8)"), [
-            id,
-            ctx.taskId ?? null,
-            ctx.sessionId ?? null,
-            ctx.owner ?? null,
-            scope,
-            ctx.toolName,
-            ctx.args == null ? null : this.json(ctx.args, "approval args"),
-            new Date(),
-        ]);
-    }
-    async getStatus(id, scope) {
-        // null-safe scope match (`<=>` / `IS NOT DISTINCT FROM`): a NULL scope row (legacy / untenanted run) is
-        // matched by a NULL scope arg, and a tenant's scope NEVER matches another tenant's — the single-DB fleet
-        // read guard (defense-in-depth).
-        const { rows } = await this.db.query(this.q("SELECT status, reason, decided_by FROM approval WHERE id = ? AND scope <=> ?", "SELECT status, reason, decided_by FROM approval WHERE id = $1 AND scope IS NOT DISTINCT FROM $2"), [id, scope]);
-        const r = rows[0];
-        if (!r)
-            return undefined;
-        return { status: r.status, reason: r.reason ?? null, decidedBy: r.decided_by ?? null };
-    }
-    /** Apply a terminal decision, but only to a still-pending row (CAS). Returns whether it applied. The scope
-     *  guard (null-safe) is carried on the operator path too for consistency with the read paths. */
-    async decide(id, scope, decision, reason, decidedBy) {
-        const res = await this.db.query(this.q("UPDATE approval SET status = ?, reason = ?, decided_by = ?, decided_at = ? WHERE id = ? AND scope <=> ? AND status = 'pending'", "UPDATE approval SET status = $1, reason = $2, decided_by = $3, decided_at = $4 WHERE id = $5 AND scope IS NOT DISTINCT FROM $6 AND status = 'pending'"), [decision, reason, decidedBy, new Date(), id, scope]);
-        return res.affected === 1;
-    }
-    /** Pending approvals (operator queue), scoped to one tenant (single-DB fleet read guard, null-safe), optionally
-     *  further filtered to one owner. */
-    async listPending(scope, owner) {
-        const { rows } = owner
-            ? await this.db.query(this.q("SELECT * FROM approval WHERE status = 'pending' AND scope <=> ? AND owner = ? ORDER BY created_at ASC", "SELECT * FROM approval WHERE status = 'pending' AND scope IS NOT DISTINCT FROM $1 AND owner = $2 ORDER BY created_at ASC"), [scope, owner])
-            : await this.db.query(this.q("SELECT * FROM approval WHERE status = 'pending' AND scope <=> ? ORDER BY created_at ASC", "SELECT * FROM approval WHERE status = 'pending' AND scope IS NOT DISTINCT FROM $1 ORDER BY created_at ASC"), [scope]);
-        return rows.map(mapRow);
-    }
-    async get(id, scope) {
-        const { rows } = await this.db.query(this.q("SELECT * FROM approval WHERE id = ? AND scope <=> ?", "SELECT * FROM approval WHERE id = $1 AND scope IS NOT DISTINCT FROM $2"), [id, scope]);
-        return rows[0] ? mapRow(rows[0]) : undefined;
-    }
-    /** Operator-only CROSS-tenant by-id read (no scope filter). The F4 operator queue serves/decides across
-     *  tenants by design; the HTTP layer gates this to an operator and then re-binds decide() to the row's OWN
-     *  scope. Tenants NEVER reach this — they use the scope-bound {@link get}. */
-    async getById(id) {
-        const { rows } = await this.db.query(this.q("SELECT * FROM approval WHERE id = ?", "SELECT * FROM approval WHERE id = $1"), [id]);
-        return rows[0] ? mapRow(rows[0]) : undefined;
-    }
-    /** Operator-only CROSS-tenant pending list (no scope filter) — the unfiltered operator queue across all
-     *  tenants. Tenants use the scope-bound {@link listPending}; this is HTTP-gated to an operator.
-     *  🔴 identical SQL text on both dialects (no placeholders, nothing dialect-specific) — kept as ONE literal
-     *  rather than a `q()` pair so a reader isn't misled into looking for a divergence that isn't there. */
-    async listPendingAll() {
-        const { rows } = await this.db.query("SELECT * FROM approval WHERE status = 'pending' ORDER BY created_at ASC");
-        return rows.map(mapRow);
-    }
-    /** Expire pending approvals older than `olderThanMs` (a never-answered operator request). Deliberately GLOBAL
-     *  (NOT scope-filtered): staleness expiry is fleet-level maintenance that protects the worker regardless of
-     *  tenant — a stale row in any scope must be reaped. Scope isolation applies to the per-tenant READ paths, not
-     *  to this maintenance sweep. */
-    async expireStale(olderThanMs) {
-        const cutoff = new Date(Date.now() - olderThanMs);
-        const res = await this.db.query(this.q("UPDATE approval SET status = 'expired', reason = 'timed out before decision', decided_at = ? " +
-            "WHERE status = 'pending' AND created_at < ?", "UPDATE approval SET status = 'expired', reason = 'timed out before decision', decided_at = $1 " +
-            "WHERE status = 'pending' AND created_at < $2"), [new Date(), cutoff]);
-        return res.affected;
-    }
-}
-/** approval row → {@link ApprovalRow} — shared by BOTH dialects. design/158 S8 归位 / A12 收编. */
-export function mapRow(r) {
-    return {
-        id: String(r.id),
-        taskId: r.task_id ?? null,
-        sessionId: r.session_id ?? null,
-        owner: r.owner ?? null,
-        scope: r.scope ?? null,
-        toolName: String(r.tool_name),
-        args: parseJson(r.args),
-        status: r.status,
-        reason: r.reason ?? null,
-        decidedBy: r.decided_by ?? null,
-        createdAt: iso(r.created_at),
-        decidedAt: iso(r.decided_at),
-    };
-}
-/** MySQL-protocol (TiDB) binding — historical class name + ctor shape preserved. */
-export class TiDBApprovalStore extends SqlApprovalStore {
-    constructor(pool) {
-        super(mysqlDriver(pool));
-    }
-}
-/** PostgreSQL binding — historical class name + ctor shape preserved. */
-export class PgApprovalStore extends SqlApprovalStore {
-    constructor(pool) {
-        super(pgDriver(pool));
-    }
-}
-//# sourceMappingURL=approval-store-sql.js.map

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

@@ -1,12 +0,0 @@
-/**
- * SVC-2 — FILE-backed durable WorkflowJournalStore for the LOCAL (TOC) backend.
- *
- * Now a RE-EXPORT of core's copy (the write-here-then-core-adopts 剧本): the implementation was written here for server
- * 1.89.0, then adopted verbatim by core (`@sema-agent/core` 1.223.0, file
- * `src/stores/file/workflow-journal-store.ts` — crash-safe per-run JSONL, scope-guarded [CORE-9],
- * idempotent-per-ordinal, oversize skip-journal, traversal-runId load degrade, 0o600/0o700). One source of
- * truth in core; the SQL twins (tidb/pg) stay service-side (dialect = deployment glue). The service test
- * suite (test/file-workflow-journal-store.test.ts) keeps pinning the contract through this re-export.
- */
-export { FileWorkflowJournalStore } from "@sema-agent/core";
-//# sourceMappingURL=file-workflow-journal-store.d.ts.map

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

@@ -1,12 +0,0 @@
-/**
- * SVC-2 — FILE-backed durable WorkflowJournalStore for the LOCAL (TOC) backend.
- *
- * Now a RE-EXPORT of core's copy (the write-here-then-core-adopts 剧本): the implementation was written here for server
- * 1.89.0, then adopted verbatim by core (`@sema-agent/core` 1.223.0, file
- * `src/stores/file/workflow-journal-store.ts` — crash-safe per-run JSONL, scope-guarded [CORE-9],
- * idempotent-per-ordinal, oversize skip-journal, traversal-runId load degrade, 0o600/0o700). One source of
- * truth in core; the SQL twins (tidb/pg) stay service-side (dialect = deployment glue). The service test
- * suite (test/file-workflow-journal-store.test.ts) keeps pinning the contract through this re-export.
- */
-export { FileWorkflowJournalStore } from "@sema-agent/core";
-//# sourceMappingURL=file-workflow-journal-store.js.map

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

@@ -1,9 +0,0 @@
-/**
- * Thin re-export shim (design/158 A12 收编 — see src/plugins/approval-store-sql.ts for the
- * implementation, now SINGLE-FILE DUAL-DIALECT alongside the TiDB twin). Class name, ctor arity,
- * and every exported type/const/helper stay EXACTLY as they were so no consumer (pg-pool.ts's
- * central schema composition, store-backend.ts, test/pg-approval-store-integration.test.ts) has
- * to move.
- */
-export { PgApprovalStore, PG_APPROVAL_SCHEMA, ensureSchema, type ApprovalRow, type ApprovalStatus, } from "./approval-store-sql.js";
-//# sourceMappingURL=pg-approval-store.d.ts.map

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

@@ -1,9 +0,0 @@
-/**
- * Thin re-export shim (design/158 A12 收编 — see src/plugins/approval-store-sql.ts for the
- * implementation, now SINGLE-FILE DUAL-DIALECT alongside the TiDB twin). Class name, ctor arity,
- * and every exported type/const/helper stay EXACTLY as they were so no consumer (pg-pool.ts's
- * central schema composition, store-backend.ts, test/pg-approval-store-integration.test.ts) has
- * to move.
- */
-export { PgApprovalStore, PG_APPROVAL_SCHEMA, ensureSchema, } from "./approval-store-sql.js";
-//# sourceMappingURL=pg-approval-store.js.map

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

@@ -1,8 +0,0 @@
-/**
- * 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 "./pg-breaker-state.js"` import (incl. pg-pool.ts's central ensureSchema
- * composition and the real dual-DB integration suite) keeps working unchanged.
- */
-export { PgBreakerState, PG_BREAKER_STATE_SCHEMA, ensureSchema } from "./breaker-state-sql.js";
-//# sourceMappingURL=pg-breaker-state.d.ts.map

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

@@ -1,8 +0,0 @@
-/**
- * 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 "./pg-breaker-state.js"` import (incl. pg-pool.ts's central ensureSchema
- * composition and the real dual-DB integration suite) keeps working unchanged.
- */
-export { PgBreakerState, PG_BREAKER_STATE_SCHEMA, ensureSchema } from "./breaker-state-sql.js";
-//# sourceMappingURL=pg-breaker-state.js.map

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

@@ -1,10 +0,0 @@
-/**
- * PostgreSQL `CheckpointStore` — the implementation now lives in the single-file dual-dialect
- * `checkpoint-store-sql.ts` (design/158 A12 定型半场), alongside its TiDB twin so the dialect deltas
- * (placeholders, ON CONFLICT, `IS NOT DISTINCT FROM` + its placeholder-arity consequence, the lossless
- * JSON envelope) read side by side instead of drifting across two files.
- *
- * This file is the historical import path: class name and ctor shape unchanged.
- */
-export { PgCheckpointStore } from "./checkpoint-store-sql.js";
-//# sourceMappingURL=pg-checkpoint-store.d.ts.map

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

@@ -1,10 +0,0 @@
-/**
- * PostgreSQL `CheckpointStore` — the implementation now lives in the single-file dual-dialect
- * `checkpoint-store-sql.ts` (design/158 A12 定型半场), alongside its TiDB twin so the dialect deltas
- * (placeholders, ON CONFLICT, `IS NOT DISTINCT FROM` + its placeholder-arity consequence, the lossless
- * JSON envelope) read side by side instead of drifting across two files.
- *
- * This file is the historical import path: class name and ctor shape unchanged.
- */
-export { PgCheckpointStore } from "./checkpoint-store-sql.js";
-//# sourceMappingURL=pg-checkpoint-store.js.map

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

@@ -1,8 +0,0 @@
-/**
- * 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 { PgFileSnapshotStore } from "./file-snapshot-store-sql.js";
-//# sourceMappingURL=pg-file-snapshot-store.d.ts.map

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

@@ -1,8 +0,0 @@
-/**
- * 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 { PgFileSnapshotStore } from "./file-snapshot-store-sql.js";
-//# sourceMappingURL=pg-file-snapshot-store.js.map

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

@@ -1,12 +0,0 @@
-/**
- * PostgreSQL BAKE store — the implementation now lives in the single-file dual-dialect
- * `image-bake-store-sql.ts` (design/158 A12 定型半场), alongside its TiDB twin so the dialect deltas
- * (placeholders, ON CONFLICT, jsonb casts, the admission-statement divergence, the PG-only
- * protocol-byte defenses) read side by side instead of drifting across two files.
- *
- * This file is the historical import path: class name, ctor shape, `PG_IMAGE_BAKE_SCHEMA` and
- * `ensureSchema` are unchanged, so pg-pool.ts / store-backend.ts / the integration suite are untouched.
- */
-export { PgImageBake, PG_IMAGE_BAKE_SCHEMA, ensurePgImageBakeSchema as ensureSchema } from "./image-bake-store-sql.js";
-export type { BakeStatus, BakeState, BakeErrorCode, BakeRecord, BakeEvent, CreateBakeInput, BakeTerminal, } from "./store-contracts.js";
-//# sourceMappingURL=pg-image-bake.d.ts.map

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

@@ -1,11 +0,0 @@
-/**
- * PostgreSQL BAKE store — the implementation now lives in the single-file dual-dialect
- * `image-bake-store-sql.ts` (design/158 A12 定型半场), alongside its TiDB twin so the dialect deltas
- * (placeholders, ON CONFLICT, jsonb casts, the admission-statement divergence, the PG-only
- * protocol-byte defenses) read side by side instead of drifting across two files.
- *
- * This file is the historical import path: class name, ctor shape, `PG_IMAGE_BAKE_SCHEMA` and
- * `ensureSchema` are unchanged, so pg-pool.ts / store-backend.ts / the integration suite are untouched.
- */
-export { PgImageBake, PG_IMAGE_BAKE_SCHEMA, ensurePgImageBakeSchema as ensureSchema } from "./image-bake-store-sql.js";
-//# sourceMappingURL=pg-image-bake.js.map

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

@@ -1,12 +0,0 @@
-/**
- * PostgreSQL-backed sandbox-image-pool INDEX store — the PG twin of {@link TiDBImageIndex}
- * (src/plugins/tidb-image-index.ts).
- *
- * Thin re-export shim (design/158 A12 定型半场): the real implementation is the single-file dual-dialect
- * `image-index-sql.ts` (`SqlImageIndex` + this file's `PgImageIndex` ctor subclass). Class name, ctor
- * arity, and the exported type/schema surface are UNCHANGED — every consumer (store-backend.ts, pg-pool.ts,
- * the real-DB integration suite) imports from here exactly as before.
- */
-export { PgImageIndex, PG_IMAGE_INDEX_SCHEMA, ensureSchema } from "./image-index-sql.js";
-export type { ImageNestedBuildMode, ImageCapabilities, ImagePodContract, ImageStatus, ImageVisibility, ImageIndexEntry, ImageIndexUpsert, ImageViewer, ImageListFilter, } from "./store-contracts.js";
-//# sourceMappingURL=pg-image-index.d.ts.map

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

@@ -1,11 +0,0 @@
-/**
- * PostgreSQL-backed sandbox-image-pool INDEX store — the PG twin of {@link TiDBImageIndex}
- * (src/plugins/tidb-image-index.ts).
- *
- * Thin re-export shim (design/158 A12 定型半场): the real implementation is the single-file dual-dialect
- * `image-index-sql.ts` (`SqlImageIndex` + this file's `PgImageIndex` ctor subclass). Class name, ctor
- * arity, and the exported type/schema surface are UNCHANGED — every consumer (store-backend.ts, pg-pool.ts,
- * the real-DB integration suite) imports from here exactly as before.
- */
-export { PgImageIndex, PG_IMAGE_INDEX_SCHEMA, ensureSchema } from "./image-index-sql.js";
-//# sourceMappingURL=pg-image-index.js.map

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

@@ -1,12 +0,0 @@
-/**
- * PostgreSQL outcome ledger — the implementation now lives in the single-file dual-dialect
- * `outcome-ledger-sql.ts` (design/158 A12 定型半场), alongside its TiDB 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, `PG_OUTCOME_LEDGER_SCHEMA` and `ensureSchema`
- * are unchanged, so pg-pool.ts / store-backend.ts / the integration suite are untouched.
- */
-export { PgOutcomeLedger, PG_OUTCOME_LEDGER_SCHEMA, ensurePgOutcomeLedgerSchema as ensureSchema, } from "./outcome-ledger-sql.js";
-export type { TaskOutcome, RunStatus } from "./outcome-ledger-sql.js";
-//# sourceMappingURL=pg-outcome-ledger.d.ts.map

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

@@ -1,11 +0,0 @@
-/**
- * PostgreSQL outcome ledger — the implementation now lives in the single-file dual-dialect
- * `outcome-ledger-sql.ts` (design/158 A12 定型半场), alongside its TiDB 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, `PG_OUTCOME_LEDGER_SCHEMA` and `ensureSchema`
- * are unchanged, so pg-pool.ts / store-backend.ts / the integration suite are untouched.
- */
-export { PgOutcomeLedger, PG_OUTCOME_LEDGER_SCHEMA, ensurePgOutcomeLedgerSchema as ensureSchema, } from "./outcome-ledger-sql.js";
-//# sourceMappingURL=pg-outcome-ledger.js.map

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

@@ -1,7 +0,0 @@
-/**
- * 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

@@ -1,7 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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

@@ -1,7 +0,0 @@
-/**
- * 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

@@ -1,7 +0,0 @@
-/**
- * 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

@@ -1,12 +0,0 @@
-/**
- * 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

@@ -1,12 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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

@@ -1,9 +0,0 @@
-/**
- * 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/tidb-approval-store.d.ts

@@ -1,8 +0,0 @@
-/**
- * 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