@rei-standard/amsg-server 2.6.0-next.2 → 2.6.0-next.20

package/dist/adapters/neon.d.ts

@@ -0,0 +1,82 @@
+export class NeonAdapter {
+    /** @param {string} connectionString */
+    constructor(connectionString: string);
+    /** @private */
+    private _connectionString;
+    /** @private */
+    private _sql;
+    /** @private */
+    private _getSql;
+    initSchema(): Promise<{
+        columnsCreated: number;
+        indexesCreated: number;
+        indexesFailed: number;
+        columns: {
+            table: string;
+            name: any;
+            type: any;
+            nullable: boolean;
+        }[];
+        indexes: ({
+            name: string;
+            status: string;
+            description: string;
+            critical: boolean;
+            error?: undefined;
+        } | {
+            name: string;
+            status: string;
+            description: string;
+            critical: boolean;
+            error: any;
+        })[];
+    }>;
+    dropSchema(): Promise<void>;
+    createTask(params: any): Promise<Record<string, any>>;
+    getTaskByUuid(uuid: any, userId: any): Promise<Record<string, any>>;
+    getTaskByUuidOnly(uuid: any): Promise<Record<string, any>>;
+    /**
+     * 这条 uuid 现在是什么状态——不限用户，也不限状态（上面那个只看 pending
+     * 行）。`runTask` 用它把「这条已经跑完了」和「压根没这条」分开回报。
+     *
+     * @param {string} uuid
+     * @returns {Promise<{ status: string }|null>}
+     */
+    getTaskStatusByUuidOnly(uuid: string): Promise<{
+        status: string;
+    } | null>;
+    updateTaskById(taskId: any, updates: any): Promise<Record<string, any>>;
+    updateTaskByUuid(uuid: any, userId: any, encryptedPayload: any, extraFields: any): Promise<Record<string, any>>;
+    deleteTaskById(taskId: any): Promise<boolean>;
+    deleteTaskByUuid(uuid: any, userId: any): Promise<boolean>;
+    getPendingTasks(limit?: number): Promise<Record<string, any>[]>;
+    claimTask(taskId: any, expectedNextSendAt: any, leaseUntil: any, serializeGroup?: any): Promise<boolean>;
+    renewTaskLease(taskId: any, leaseUntil: any): Promise<boolean>;
+    listTasks(userId: any, opts?: {}): Promise<{
+        tasks: Record<string, any>[];
+        total: number;
+    }>;
+    cleanupOldTasks(days?: number): Promise<number>;
+    getTaskStatus(uuid: any, userId: any): Promise<any>;
+    getTaskStatusInfo(uuid: any, userId: any): Promise<{
+        status: string;
+        last_error: string | null;
+    }>;
+    getPushSubscription(userId: any): Promise<{
+        subscription: string;
+        updated_at: number;
+    }>;
+    upsertPushSubscription(userId: any, encryptedSubscription: any, updatedAt: any): Promise<boolean>;
+    deletePushSubscription(userId: any): Promise<boolean>;
+    upsertLlmCredentials(userId: any, entries: any): Promise<number>;
+    getLlmCredentials(userId: any, credIds: any): Promise<{
+        cred_id: string;
+        encrypted_value: string;
+        updated_at: string;
+    }[]>;
+    listLlmCredentials(userId: any): Promise<{
+        cred_id: string;
+        updated_at: string;
+    }[]>;
+    deleteLlmCredentials(userId: any, credIds?: any): Promise<number>;
+}

package/dist/adapters/pg-shared.d.ts

@@ -0,0 +1,161 @@
+/**
+ * pg / neon 共用的 Postgres 查询实现。
+ *
+ * 两个适配器只在「怎么把 SQL 发出去」上不同（pg 的连接池 vs neon 的 HTTP
+ * 驱动），SQL 与并发语义必须逐字一致——各自复制一份的话，修一边漏一边就会让
+ * 两种 Postgres 部署的串行化行为静默分歧，而各自的测试还都是绿的。所以这里
+ * 按执行器参数化：适配器只递一个 `query(text, params) → rows`。
+ *
+ * D1（SQLite 方言、单写者、ISO TEXT 时间戳）不走这份实现。
+ *
+ * @typedef {(text: string, params?: any[]) => Promise<any[]>} PgQuery
+ */
+/**
+ * 领取一条到点的任务：在 lease_until 上写下「这条归我管到什么时候」，
+ * 本次投递期间别的 tick 领不走它。
+ *
+ * 租约写在自己的列上，next_send_at 全程不动——那一列是用户设的触发时刻，
+ * 任务列表要读它、循环任务推进下一次也要拿它当基准。
+ *
+ * 两个 tick 抢同一行时只有一个改得动，另一个拿不到 RETURNING 行，据此跳
+ * 过。WHERE 里的两个条件各管一件事：
+ *   - lease_until 为空或已过期：没人正在跑这条。领了任务的 tick 中途没了
+ *     也不会把行焊死，租约到期后自然可以被接手。
+ *   - next_send_at 等于读这行时看到的值：读出来之后用户又改了排期的话，
+ *     这一跳就不该再按旧时刻发。
+ *
+ * 不加一个 'sending' 状态来表达「正在跑」：status 上有 CHECK 约束，加值
+ * 要改表。
+ *
+ * 比 next_send_at 时两边都截到毫秒：列是 timestamptz（微秒精度），驱动读
+ * 出来是 JS Date（毫秒精度），原值送回去可能因为亚毫秒差对不上。
+ *
+ * 带 serializeGroup 时多一道分组门：同一分组里已经有别的行拿着未到期的租
+ * 约，这条就领不走（同一分组同时只跑一条）。判定和写租约在同一条 UPDATE
+ * 里完成——但那只对「抢同一行」成立；READ COMMITTED 下两个并发 tick 各领
+ * 同组的**不同**行时，各自的 NOT EXISTS 子查询都看不到对方尚未提交的租约，
+ * 也没有行锁冲突逼它重查（写偏斜）。所以占位成功后再回头查一次：真撞上了
+ * 就把自己刚写的租约放掉、这一跳不跑——两边都让也没事，行保持 pending，
+ * 下一跳重试。分组门只看租约，不看 `retry_after`：等着重试的任务其实闲着，
+ * 不该把同分组的其他任务一起堵住。
+ *
+ * @param {PgQuery} query
+ * @param {number} taskId
+ * @param {string|Date} expectedNextSendAt - 读这行时拿到的 next_send_at 原值
+ * @param {string|Date} leaseUntil - 租期末尾
+ * @param {string|null} [serializeGroup] - 串行分组标识；空表示不参与分组串行
+ * @returns {Promise<boolean>} true = 领到了；false = 已被别人领走、同分组有
+ *   任务正在跑、排期被改过、或行已不是 pending
+ */
+export function claimTask(query: PgQuery, taskId: number, expectedNextSendAt: string | Date, leaseUntil: string | Date, serializeGroup?: string | null): Promise<boolean>;
+/**
+ * 投递期间的租约续期（run-tick 的心跳用）。只在行仍是 pending 且确实持有
+ * 租约（lease_until 非空）时生效——收尾把租约放掉之后，迟到的心跳不会把
+ * 租约复活。
+ *
+ * @param {PgQuery} query
+ * @param {number} taskId
+ * @param {string|Date} leaseUntil - 新的租期末尾
+ * @returns {Promise<boolean>} true = 续上了
+ */
+export function renewTaskLease(query: PgQuery, taskId: number, leaseUntil: string | Date): Promise<boolean>;
+/**
+ * 状态 + 失败摘要（GET /message 用它把「为什么失败」透给已失败的行）。
+ *
+ * @param {PgQuery} query
+ * @param {string} uuid
+ * @param {string} userId
+ * @returns {Promise<{ status: string, last_error: string|null }|null>}
+ */
+export function getTaskStatusInfo(query: PgQuery, uuid: string, userId: string): Promise<{
+    status: string;
+    last_error: string | null;
+} | null>;
+/**
+ * 这个用户当前登记的推送订阅（密文原样返回，解密在上层）。
+ *
+ * @param {PgQuery} query
+ * @param {string} userId
+ * @returns {Promise<{ subscription: string, updated_at: number }|null>}
+ */
+export function getPushSubscription(query: PgQuery, userId: string): Promise<{
+    subscription: string;
+    updated_at: number;
+} | null>;
+/**
+ * 覆盖写这个用户的订阅。一个用户一行，没有 last-write-wins 之类的比较——
+ * 客户端拿到的新订阅永远比旧的有效，旧的那份只会 410。
+ *
+ * @param {PgQuery} query
+ * @param {string} userId
+ * @param {string} encryptedSubscription
+ * @param {number} updatedAt - epoch 毫秒
+ * @returns {Promise<boolean>}
+ */
+export function upsertPushSubscription(query: PgQuery, userId: string, encryptedSubscription: string, updatedAt: number): Promise<boolean>;
+/**
+ * 删掉这个用户的订阅（设置页「停止接收推送」）。
+ *
+ * @param {PgQuery} query
+ * @param {string} userId
+ * @returns {Promise<boolean>} true = 确实删掉了一行
+ */
+export function deletePushSubscription(query: PgQuery, userId: string): Promise<boolean>;
+/**
+ * 批量 upsert 这个用户的凭据（value 已是密文，加密在上层）。已存在的行覆盖
+ * encrypted_value 并刷 updated_at，created_at 保留首次写入的时刻。
+ *
+ * @param {PgQuery} query
+ * @param {string} userId
+ * @param {Array<{ credId: string, encryptedValue: string }>} entries
+ * @param {string} now - ISO8601 时间戳（与 SQLite 侧同口径的 TEXT）
+ * @returns {Promise<number>} 实际写入/覆盖的行数
+ */
+export function upsertLlmCredentials(query: PgQuery, userId: string, entries: Array<{
+    credId: string;
+    encryptedValue: string;
+}>, now: string): Promise<number>;
+/**
+ * 按 cred_id 批量读这个用户的凭据行（密文原样返回，解密在上层）。
+ *
+ * @param {PgQuery} query
+ * @param {string} userId
+ * @param {string[]} credIds
+ * @returns {Promise<Array<{ cred_id: string, encrypted_value: string, updated_at: string }>>}
+ */
+export function getLlmCredentials(query: PgQuery, userId: string, credIds: string[]): Promise<Array<{
+    cred_id: string;
+    encrypted_value: string;
+    updated_at: string;
+}>>;
+/**
+ * 这个用户名下所有凭据的对账清单（只有 cred_id 和 updated_at）。
+ *
+ * @param {PgQuery} query
+ * @param {string} userId
+ * @returns {Promise<Array<{ cred_id: string, updated_at: string }>>}
+ */
+export function listLlmCredentials(query: PgQuery, userId: string): Promise<Array<{
+    cred_id: string;
+    updated_at: string;
+}>>;
+/**
+ * 删凭据。`credIds` 传数组删指定那几行；传 null 删这个用户的全部。
+ *
+ * @param {PgQuery} query
+ * @param {string} userId
+ * @param {string[]|null} credIds
+ * @returns {Promise<number>} 删掉的行数
+ */
+export function deleteLlmCredentials(query: PgQuery, userId: string, credIds?: string[] | null): Promise<number>;
+/**
+ * pg / neon 共用的 Postgres 查询实现。
+ *
+ * 两个适配器只在「怎么把 SQL 发出去」上不同（pg 的连接池 vs neon 的 HTTP
+ * 驱动），SQL 与并发语义必须逐字一致——各自复制一份的话，修一边漏一边就会让
+ * 两种 Postgres 部署的串行化行为静默分歧，而各自的测试还都是绿的。所以这里
+ * 按执行器参数化：适配器只递一个 `query(text, params) → rows`。
+ *
+ * D1（SQLite 方言、单写者、ISO TEXT 时间戳）不走这份实现。
+ */
+export type PgQuery = (text: string, params?: any[]) => Promise<any[]>;

package/dist/adapters/pg.d.ts

@@ -0,0 +1,84 @@
+export class PgAdapter {
+    /** @param {string} connectionString */
+    constructor(connectionString: string);
+    /** @private */
+    private _connectionString;
+    /** @private */
+    private _pool;
+    /** @private */
+    private _getPool;
+    /** @private */
+    private _query;
+    initSchema(): Promise<{
+        columnsCreated: number;
+        indexesCreated: number;
+        indexesFailed: number;
+        columns: {
+            table: string;
+            name: any;
+            type: any;
+            nullable: boolean;
+        }[];
+        indexes: ({
+            name: string;
+            status: string;
+            description: string;
+            critical: boolean;
+            error?: undefined;
+        } | {
+            name: string;
+            status: string;
+            description: string;
+            critical: boolean;
+            error: any;
+        })[];
+    }>;
+    dropSchema(): Promise<void>;
+    createTask(params: any): Promise<any[]>;
+    getTaskByUuid(uuid: any, userId: any): Promise<any[]>;
+    getTaskByUuidOnly(uuid: any): Promise<any[]>;
+    /**
+     * 这条 uuid 现在是什么状态——不限用户，也不限状态（上面那个只看 pending
+     * 行）。`runTask` 用它把「这条已经跑完了」和「压根没这条」分开回报。
+     *
+     * @param {string} uuid
+     * @returns {Promise<{ status: string }|null>}
+     */
+    getTaskStatusByUuidOnly(uuid: string): Promise<{
+        status: string;
+    } | null>;
+    updateTaskById(taskId: any, updates: any): Promise<any[]>;
+    updateTaskByUuid(uuid: any, userId: any, encryptedPayload: any, extraFields: any): Promise<any[]>;
+    deleteTaskById(taskId: any): Promise<boolean>;
+    deleteTaskByUuid(uuid: any, userId: any): Promise<boolean>;
+    getPendingTasks(limit?: number): Promise<any[][]>;
+    claimTask(taskId: any, expectedNextSendAt: any, leaseUntil: any, serializeGroup?: any): Promise<boolean>;
+    renewTaskLease(taskId: any, leaseUntil: any): Promise<boolean>;
+    listTasks(userId: any, opts?: {}): Promise<{
+        tasks: any[][];
+        total: number;
+    }>;
+    cleanupOldTasks(days?: number): Promise<number>;
+    getTaskStatus(uuid: any, userId: any): Promise<any>;
+    getTaskStatusInfo(uuid: any, userId: any): Promise<{
+        status: string;
+        last_error: string | null;
+    }>;
+    getPushSubscription(userId: any): Promise<{
+        subscription: string;
+        updated_at: number;
+    }>;
+    upsertPushSubscription(userId: any, encryptedSubscription: any, updatedAt: any): Promise<boolean>;
+    deletePushSubscription(userId: any): Promise<boolean>;
+    upsertLlmCredentials(userId: any, entries: any): Promise<number>;
+    getLlmCredentials(userId: any, credIds: any): Promise<{
+        cred_id: string;
+        encrypted_value: string;
+        updated_at: string;
+    }[]>;
+    listLlmCredentials(userId: any): Promise<{
+        cred_id: string;
+        updated_at: string;
+    }[]>;
+    deleteLlmCredentials(userId: any, credIds?: any): Promise<number>;
+}

package/dist/adapters/schema.d.ts

@@ -0,0 +1,41 @@
+/**
+ * Shared SQL schema constants
+ *
+ * 定时触发用的三列各管一件事，别把它们混着读（见 lib/run-tick.js）：
+ *   - `lease_until`：**这条正在跑**。某个 tick 占位时写「归我管到什么时候」，
+ *     投递收尾时放掉。捞取待发任务时跳过租约未到期的行。
+ *   - `retry_after`：**这条没在跑，等着重试**。投递失败的退避时刻，到点之前
+ *     捞不到这行。跟租约分开写，是因为「正在跑」会挡住同分组的其他任务，而
+ *     一条正在等重试的任务其实闲着，不该连累别人。
+ *   - `serialize_group`：这条属于哪个串行分组（`runScheduledTick` 的
+ *     `serializeBy` 算出来的，占位时一起写）。同一分组同时只放行一条。存的是
+ *     派生值而不是宿主给的原始 key —— 原始 key 往往是角色 id 之类的宿主数据，
+ *     任务内容都是密文落库的，这一列不该成为它的明文出口。
+ */
+export const TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS scheduled_messages (\n    id SERIAL PRIMARY KEY,\n    user_id VARCHAR(255) NOT NULL,\n    uuid VARCHAR(36),\n    encrypted_payload TEXT NOT NULL,\n    message_type VARCHAR(50) NOT NULL CHECK (message_type IN ('fixed', 'prompted', 'auto', 'instant')),\n    next_send_at TIMESTAMP WITH TIME ZONE NOT NULL,\n    lease_until TIMESTAMP WITH TIME ZONE,\n    retry_after TIMESTAMP WITH TIME ZONE,\n    serialize_group VARCHAR(64),\n    status VARCHAR(50) NOT NULL DEFAULT 'pending' CHECK (status IN ('pending', 'sent', 'failed')),\n    retry_count INTEGER DEFAULT 0,\n    last_error TEXT,\n    created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),\n    updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()\n  )\n";
+/**
+ * 建表语句用的是 CREATE TABLE IF NOT EXISTS，已经存在的表不会被改动，所以
+ * 后加的列要单独补。initSchema 每次都会跑一遍，Postgres 的 IF NOT EXISTS
+ * 让重复执行也没事。
+ */
+export const MIGRATIONS: {
+    name: string;
+    sql: string;
+    description: string;
+}[];
+export const INDEXES: ({
+    name: string;
+    sql: string;
+    description: string;
+    critical?: undefined;
+} | {
+    name: string;
+    sql: string;
+    description: string;
+    critical: boolean;
+})[];
+export const PUSH_SUBSCRIPTION_TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS push_subscriptions (\n    user_id VARCHAR(255) PRIMARY KEY,\n    subscription TEXT NOT NULL,\n    updated_at BIGINT NOT NULL\n  )\n";
+export const LLM_CREDENTIALS_TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS llm_credentials (\n    user_id VARCHAR(255) NOT NULL,\n    cred_id VARCHAR(128) NOT NULL,\n    encrypted_value TEXT NOT NULL,\n    created_at TEXT NOT NULL,\n    updated_at TEXT NOT NULL,\n    PRIMARY KEY (user_id, cred_id)\n  )\n";
+export const VERIFY_TABLE_SQL: "\n  SELECT table_name\n  FROM information_schema.tables\n  WHERE table_schema = 'public'\n    AND table_name = 'scheduled_messages'\n";
+export const COLUMNS_SQL: "\n  SELECT column_name, data_type, is_nullable\n  FROM information_schema.columns\n  WHERE table_schema = 'public'\n    AND table_name = 'scheduled_messages'\n  ORDER BY ordinal_position\n";
+export const UPDATABLE_COLUMNS: Set<string>;

package/dist/adapters/schema.sqlite.d.ts

@@ -0,0 +1,49 @@
+/**
+ * SQLite (Cloudflare D1) dialect schema for scheduled_messages.
+ *
+ * 定时触发用的 `lease_until` / `retry_after` / `serialize_group` 三列分别是什么
+ * 意思，写在 Postgres 那份 schema 的文件头（adapters/schema.js）。
+ *
+ * Differences from the Postgres schema (adapters/schema.js):
+ *   - id: INTEGER PRIMARY KEY AUTOINCREMENT (vs SERIAL)
+ *   - timestamps stored as TEXT ISO8601 UTC (vs TIMESTAMP WITH TIME ZONE)
+ *   - no NOW()/DEFAULT; the adapter always writes timestamps explicitly
+ *   - retry_count is NOT NULL here (Postgres omits NOT NULL); every write path
+ *     sets it explicitly, so the tighter constraint just documents that intent
+ * Partial indexes and CHECK constraints are native to SQLite, so they carry over.
+ * Index entries mirror the Postgres INDEXES shape ({ name, sql, description,
+ * critical }) so both adapters' initSchema() return the same index metadata.
+ */
+export const SQLITE_TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS scheduled_messages (\n    id INTEGER PRIMARY KEY AUTOINCREMENT,\n    user_id TEXT NOT NULL,\n    uuid TEXT,\n    encrypted_payload TEXT NOT NULL,\n    message_type TEXT NOT NULL CHECK (message_type IN ('fixed', 'prompted', 'auto', 'instant')),\n    next_send_at TEXT NOT NULL,\n    lease_until TEXT,\n    retry_after TEXT,\n    serialize_group TEXT,\n    status TEXT NOT NULL DEFAULT 'pending' CHECK (status IN ('pending', 'sent', 'failed')),\n    retry_count INTEGER NOT NULL DEFAULT 0,\n    last_error TEXT,\n    created_at TEXT NOT NULL,\n    updated_at TEXT NOT NULL\n  )\n";
+/**
+ * 建表语句用的是 CREATE TABLE IF NOT EXISTS，已经存在的表不会被改动，所以
+ * 后加的列要单独补。initSchema 每次都会跑一遍，列已经在了就跳过。
+ */
+export const SQLITE_MIGRATIONS: {
+    name: string;
+    sql: string;
+    description: string;
+}[];
+export const SQLITE_INDEXES: {
+    name: string;
+    sql: string;
+    description: string;
+    critical: boolean;
+}[];
+export const CLIENT_STATE_TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS client_state (\n    user_id TEXT NOT NULL,\n    namespace TEXT NOT NULL,\n    key TEXT NOT NULL,\n    value TEXT NOT NULL,\n    updated_at INTEGER NOT NULL,\n    PRIMARY KEY (user_id, namespace, key)\n  )\n";
+export const PUSH_SUBSCRIPTION_TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS push_subscriptions (\n    user_id TEXT PRIMARY KEY,\n    subscription TEXT NOT NULL,\n    updated_at INTEGER NOT NULL\n  )\n";
+export const LLM_CREDENTIALS_TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS llm_credentials (\n    user_id TEXT NOT NULL,\n    cred_id TEXT NOT NULL,\n    encrypted_value TEXT NOT NULL,\n    created_at TEXT NOT NULL,\n    updated_at TEXT NOT NULL,\n    PRIMARY KEY (user_id, cred_id)\n  )\n";
+export const MESSAGE_OUTBOX_TABLE_SQL: "\n  CREATE TABLE IF NOT EXISTS message_outbox (\n    id INTEGER PRIMARY KEY AUTOINCREMENT,\n    user_id TEXT NOT NULL,\n    message_id TEXT NOT NULL,\n    task_uuid TEXT,\n    session_id TEXT,\n    message_index INTEGER,\n    total_messages INTEGER,\n    payload TEXT NOT NULL,\n    created_at INTEGER NOT NULL,\n    delivered_at INTEGER,\n    acked_at INTEGER,\n    UNIQUE (user_id, message_id)\n  )\n";
+export const MESSAGE_OUTBOX_INDEX_SQL: "\n  CREATE INDEX IF NOT EXISTS idx_outbox_unacked\n    ON message_outbox (user_id, id)\n    WHERE acked_at IS NULL\n";
+/**
+ * 这一版代码跑起来需要的表 / 列 / 索引。
+ *
+ * 索引只列 critical 的那几个（uidx_uuid 之类）：其余索引缺了只是慢，缺了它则
+ * 是正确性问题。
+ *
+ * @type {{ tables: Record<string, string[]>, indexes: string[] }}
+ */
+export const SQLITE_REQUIRED_SCHEMA: {
+    tables: Record<string, string[]>;
+    indexes: string[];
+};

package/dist/chunk-5FXVSC5O.mjs

@@ -0,0 +1,144 @@
+// src/server/adapters/schema.js
+var TABLE_SQL = `
+  CREATE TABLE IF NOT EXISTS scheduled_messages (
+    id SERIAL PRIMARY KEY,
+    user_id VARCHAR(255) NOT NULL,
+    uuid VARCHAR(36),
+    encrypted_payload TEXT NOT NULL,
+    message_type VARCHAR(50) NOT NULL CHECK (message_type IN ('fixed', 'prompted', 'auto', 'instant')),
+    next_send_at TIMESTAMP WITH TIME ZONE NOT NULL,
+    lease_until TIMESTAMP WITH TIME ZONE,
+    retry_after TIMESTAMP WITH TIME ZONE,
+    serialize_group VARCHAR(64),
+    status VARCHAR(50) NOT NULL DEFAULT 'pending' CHECK (status IN ('pending', 'sent', 'failed')),
+    retry_count INTEGER DEFAULT 0,
+    last_error TEXT,
+    created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),
+    updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
+  )
+`;
+var MIGRATIONS = [
+  {
+    name: "add_lease_until",
+    sql: "ALTER TABLE scheduled_messages ADD COLUMN IF NOT EXISTS lease_until TIMESTAMP WITH TIME ZONE",
+    description: "Task claim lease (2.6.0)"
+  },
+  {
+    name: "add_retry_after",
+    sql: "ALTER TABLE scheduled_messages ADD COLUMN IF NOT EXISTS retry_after TIMESTAMP WITH TIME ZONE",
+    description: "Retry backoff, held apart from the claim lease (2.6.0)"
+  },
+  {
+    name: "add_serialize_group",
+    sql: "ALTER TABLE scheduled_messages ADD COLUMN IF NOT EXISTS serialize_group VARCHAR(64)",
+    description: "Serialization group for runScheduledTick serializeBy (2.6.0)"
+  },
+  {
+    name: "add_last_error",
+    // 上一次投递失败的脱敏摘要（JSON：{ at, occurrence, reason }）。payload 里
+    // 的 lastError 是密文里的完整记录，这一列是它的明文出口——payload 本身
+    // 解密失败时也写得进去，GET /message 对已失败的行也读得出来。
+    sql: "ALTER TABLE scheduled_messages ADD COLUMN IF NOT EXISTS last_error TEXT",
+    description: "Sanitized last delivery-failure summary (2.6.0)"
+  }
+];
+var INDEXES = [
+  {
+    name: "idx_pending_tasks_optimized",
+    sql: `CREATE INDEX IF NOT EXISTS idx_pending_tasks_optimized
+          ON scheduled_messages (status, next_send_at, id, retry_count)
+          WHERE status = 'pending'`,
+    description: "Main query index (Cron Job finds pending tasks)"
+  },
+  {
+    name: "idx_cleanup_completed",
+    sql: `CREATE INDEX IF NOT EXISTS idx_cleanup_completed
+          ON scheduled_messages (status, updated_at)
+          WHERE status IN ('sent', 'failed')`,
+    description: "Cleanup query index"
+  },
+  {
+    name: "idx_failed_retry",
+    sql: `CREATE INDEX IF NOT EXISTS idx_failed_retry
+          ON scheduled_messages (status, retry_count, next_send_at)
+          WHERE status = 'failed' AND retry_count < 3`,
+    description: "Failed retry index"
+  },
+  {
+    name: "idx_user_id",
+    sql: `CREATE INDEX IF NOT EXISTS idx_user_id
+          ON scheduled_messages (user_id)`,
+    description: "User task query index"
+  },
+  {
+    name: "uidx_uuid",
+    sql: `CREATE UNIQUE INDEX IF NOT EXISTS uidx_uuid
+          ON scheduled_messages (uuid)
+          WHERE uuid IS NOT NULL`,
+    description: "UUID uniqueness guard",
+    critical: true
+  },
+  {
+    name: "idx_serialize_group_lease",
+    sql: `CREATE INDEX IF NOT EXISTS idx_serialize_group_lease
+          ON scheduled_messages (serialize_group, lease_until)
+          WHERE serialize_group IS NOT NULL AND status = 'pending'`,
+    description: "Serialization group busy-check index (claimTask)"
+  }
+];
+var PUSH_SUBSCRIPTION_TABLE_SQL = `
+  CREATE TABLE IF NOT EXISTS push_subscriptions (
+    user_id VARCHAR(255) PRIMARY KEY,
+    subscription TEXT NOT NULL,
+    updated_at BIGINT NOT NULL
+  )
+`;
+var LLM_CREDENTIALS_TABLE_SQL = `
+  CREATE TABLE IF NOT EXISTS llm_credentials (
+    user_id VARCHAR(255) NOT NULL,
+    cred_id VARCHAR(128) NOT NULL,
+    encrypted_value TEXT NOT NULL,
+    created_at TEXT NOT NULL,
+    updated_at TEXT NOT NULL,
+    PRIMARY KEY (user_id, cred_id)
+  )
+`;
+var VERIFY_TABLE_SQL = `
+  SELECT table_name
+  FROM information_schema.tables
+  WHERE table_schema = 'public'
+    AND table_name = 'scheduled_messages'
+`;
+var COLUMNS_SQL = `
+  SELECT column_name, data_type, is_nullable
+  FROM information_schema.columns
+  WHERE table_schema = 'public'
+    AND table_name = 'scheduled_messages'
+  ORDER BY ordinal_position
+`;
+var UPDATABLE_COLUMNS = /* @__PURE__ */ new Set([
+  "user_id",
+  "uuid",
+  "encrypted_payload",
+  "message_type",
+  "next_send_at",
+  "lease_until",
+  "retry_after",
+  "serialize_group",
+  "status",
+  "retry_count",
+  "last_error",
+  "created_at",
+  "updated_at"
+]);
+
+export {
+  TABLE_SQL,
+  MIGRATIONS,
+  INDEXES,
+  PUSH_SUBSCRIPTION_TABLE_SQL,
+  LLM_CREDENTIALS_TABLE_SQL,
+  VERIFY_TABLE_SQL,
+  COLUMNS_SQL,
+  UPDATABLE_COLUMNS
+};