@sema-agent/server 7.4.0 → 7.5.0

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

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

@@ -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, } from "./approval-store-sql.js";
-//# sourceMappingURL=tidb-approval-store.js.map

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

@@ -1,7 +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 "./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

@@ -1,7 +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 "./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

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

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

@@ -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 { TiDBFileSnapshotStore } from "./file-snapshot-store-sql.js";
-//# sourceMappingURL=tidb-file-snapshot-store.d.ts.map

package/dist/plugins/tidb-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 { TiDBFileSnapshotStore } from "./file-snapshot-store-sql.js";
-//# sourceMappingURL=tidb-file-snapshot-store.js.map

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

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

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

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

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

package/dist/sema-registry.d.ts

@@ -1,41 +0,0 @@
-/**
- * Sema-registry adapter — pull the effective config from sema-registry and apply it OVER the
- * env-derived defaults (env = fallback, center = override). Follows the "universal internal
- * schema → translate at the boundary" pattern, with our security boundary kept:
- *
- *   - the CENTER owns the LOGICAL config: the model roster (names/capabilities/tier), the role map,
- *     and team templates;
- *   - the SERVICE env still owns the SECRETS: API keys stay in env (the center never stores a secret);
- *     keys are per-model via `apiKeyEnv` → `config.modelApiKeyEnv` → the spec's `getApiKeyAndHeaders`
- *     (core 1.45), so each model/cascade-rung authenticates with its own upstream key.
- *
- * Per-model `baseUrl` IS transported (a catalog model may live on a different gateway;
- * core brain honors model.baseUrl, absent = "" = boot-env endpoint).
- *
- * Hot-reload status (复审 2026-07-29 P1-11 — 亲读判定,取代此处旧的 "models/roles are restart-to-apply"
- * TODO, which went stale when `mutateInPlace` landed):
- *   - models/roles/roster/teams/projects/autonomy — **HOT**. `applyEffective` mutates `config.models`/
- *     `config.roles` IN PLACE, and core's Runner reads `this.deps.models/roles` per task off that very
- *     reference. Both brains re-resolve `model.baseUrl || config.baseUrl` inside `buildRequest()` on every
- *     call (core 2.1.0 `brain/openai.js` + `brain/anthropic.js`), so a moved gateway takes effect on the
- *     next task with no restart.
- *   - the same plane under a **tier-frozen** Runner — deferred, not hot: core expands a PRIVATE catalog copy
- *     at construction, so `main` defers the whole plane and the `models-tiers` restart slice signals.
- *   - **`degrade-route`** — the one genuinely boot-frozen catalog consumer left: reactive degrade
- *     (`MODEL_DEGRADE_REACTIVE`) bakes the target Model + its gateway + its key into the brain composition
- *     at boot. It cannot be hot-applied without rebuilding the brain, so it is registered on the existing
- *     restartRequired /health contract instead (see `restart-signal.ts`). Fail-loud beats serving a stale
- *     gateway silently on the rate-limit path.
- *   - skills/mcp/scenarios/runtime-gates — restart-to-apply by construction (baked into the boot wiring).
- *
- * (design/158 A13, internal-lossless) This module is now a FACADE: the implementation lives in
- * `src/config-center/` split by responsibility group (HTTP client / EffectiveConfig application /
- * restart-signal detection / skills+MCP consumption). Every symbol below is re-exported UNCHANGED —
- * existing `from "./sema-registry.js"` / `from "../sema-registry.js"` imports need zero changes.
- */
-export { fetchEffective, fetchPrincipalCaps, ConfigCenterHttpError, fetchSkillContent, fetchPromptArtifact, fetchPromptBlob, } from "./config-center/http-client.js";
-export { mutateInPlace, applyEffective, applyRuntimeGates, applyRuntimeHot, resolveDefaultModelName, logEffectiveDiff, runtimeHasActiveGate, } from "./config-center/apply-effective.js";
-export { restartReasons, planeHasActiveTiers, modelPlaneChanged, type RestartSlice, type RestartSliceCtx, type RestartSignal, } from "./config-center/restart-signal.js";
-export { applyCenterSkills, resolveMcpServers, mcpForScenario } from "./config-center/skills-mcp.js";
-export type { CenterSkillManifest, CenterMcpServer, EffectiveConfig, ExecutionRuling, SessionMirrorRuling, } from "./config-center/types.js";
-//# sourceMappingURL=sema-registry.d.ts.map

package/dist/sema-registry.js

@@ -1,40 +0,0 @@
-/**
- * Sema-registry adapter — pull the effective config from sema-registry and apply it OVER the
- * env-derived defaults (env = fallback, center = override). Follows the "universal internal
- * schema → translate at the boundary" pattern, with our security boundary kept:
- *
- *   - the CENTER owns the LOGICAL config: the model roster (names/capabilities/tier), the role map,
- *     and team templates;
- *   - the SERVICE env still owns the SECRETS: API keys stay in env (the center never stores a secret);
- *     keys are per-model via `apiKeyEnv` → `config.modelApiKeyEnv` → the spec's `getApiKeyAndHeaders`
- *     (core 1.45), so each model/cascade-rung authenticates with its own upstream key.
- *
- * Per-model `baseUrl` IS transported (a catalog model may live on a different gateway;
- * core brain honors model.baseUrl, absent = "" = boot-env endpoint).
- *
- * Hot-reload status (复审 2026-07-29 P1-11 — 亲读判定,取代此处旧的 "models/roles are restart-to-apply"
- * TODO, which went stale when `mutateInPlace` landed):
- *   - models/roles/roster/teams/projects/autonomy — **HOT**. `applyEffective` mutates `config.models`/
- *     `config.roles` IN PLACE, and core's Runner reads `this.deps.models/roles` per task off that very
- *     reference. Both brains re-resolve `model.baseUrl || config.baseUrl` inside `buildRequest()` on every
- *     call (core 2.1.0 `brain/openai.js` + `brain/anthropic.js`), so a moved gateway takes effect on the
- *     next task with no restart.
- *   - the same plane under a **tier-frozen** Runner — deferred, not hot: core expands a PRIVATE catalog copy
- *     at construction, so `main` defers the whole plane and the `models-tiers` restart slice signals.
- *   - **`degrade-route`** — the one genuinely boot-frozen catalog consumer left: reactive degrade
- *     (`MODEL_DEGRADE_REACTIVE`) bakes the target Model + its gateway + its key into the brain composition
- *     at boot. It cannot be hot-applied without rebuilding the brain, so it is registered on the existing
- *     restartRequired /health contract instead (see `restart-signal.ts`). Fail-loud beats serving a stale
- *     gateway silently on the rate-limit path.
- *   - skills/mcp/scenarios/runtime-gates — restart-to-apply by construction (baked into the boot wiring).
- *
- * (design/158 A13, internal-lossless) This module is now a FACADE: the implementation lives in
- * `src/config-center/` split by responsibility group (HTTP client / EffectiveConfig application /
- * restart-signal detection / skills+MCP consumption). Every symbol below is re-exported UNCHANGED —
- * existing `from "./sema-registry.js"` / `from "../sema-registry.js"` imports need zero changes.
- */
-export { fetchEffective, fetchPrincipalCaps, ConfigCenterHttpError, fetchSkillContent, fetchPromptArtifact, fetchPromptBlob, } from "./config-center/http-client.js";
-export { mutateInPlace, applyEffective, applyRuntimeGates, applyRuntimeHot, resolveDefaultModelName, logEffectiveDiff, runtimeHasActiveGate, } from "./config-center/apply-effective.js";
-export { restartReasons, planeHasActiveTiers, modelPlaneChanged, } from "./config-center/restart-signal.js";
-export { applyCenterSkills, resolveMcpServers, mcpForScenario } from "./config-center/skills-mcp.js";
-//# sourceMappingURL=sema-registry.js.map