@sema-agent/server 4.2.0 → 5.0.0

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

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

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

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

@@ -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 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

@@ -1,10 +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). `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

@@ -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). `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

@@ -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
- * `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

@@ -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
- * `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

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

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

@@ -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: 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

@@ -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: 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

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

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

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

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