@rei-standard/amsg-server 2.6.0-next.33 → 2.6.0-next.35

package/README.md

@@ -1014,3 +1014,18 @@ async function executeToolCalls(calls, ctx) {
 取消收尾使用 `onFireSettled({ status: 'cancelled', willRetry: false, error, ... })`，不是生成失败。应用应在这里释放资源、结算已发生的用量，避免发出失败提示或把未送达内容记为已回复。取消时已经开始写入的 outbox 批次会在写完后检查信号并撤掉未投递部分；已经发到客户端的消息仍由客户端处理。应用需要记录停止的任务身份，拦住迟到推送、补收以及尚未显示的本地内容。已完成的外部副作用无法撤销；不支持 AbortSignal 的工具也需要自己在执行步骤之间检查取消。
 
 执行阶段的 `ctx.writeState`、`scheduleTask`、`cancelTask`、`renewTask` 和 `emitResult` 会拒绝取消后新发起的操作。`onFireSettled` 的 `info.writeState` 特意仍可用，供宿主释放锁、保存账单等收尾；它不能用于继续生成阶段的业务动作。已经开始的数据库写入不支持回滚，宿主仍需处理并发状态版本。
+
+### Cloud data inventory and cleanup (D1)
+
+Single-user D1 deployments expose `cloud-data-management` in `/capabilities`.
+The management API lists actual cloud resources, including acknowledged outbox
+rows, orphan state chunks and resources missing a local character. Cleanup uses
+server previews, persistent operations and cron continuation. Owner retirement
+fences future writes and in-flight task outputs; restoration is explicit and
+returns the generation required on subsequent writes.
+
+See the repository [cloud data management contract](../../../docs/cloud-data-management.md)
+for routes, encrypted metadata, host `cloudData.resolveOwner` configuration,
+retention, and upgrade requirements. Other adapters do not advertise this
+capability. Use the matching client SDK management methods rather than composing
+bulk deletes from the browser's local resource list.

package/dist/adapters/d1.d.ts

@@ -49,6 +49,104 @@ export class D1Adapter {
      * @returns {Promise<number>} 各批影响行数之和
      */
     private _runInClauseWrite;
+    /** A complete management implementation needs real transactional batches. */
+    get cloudDataManagement(): boolean;
+    _cloudGuardPredicate(userId: any, guard: any): {
+        sql: string;
+        args: any[];
+    };
+    _cloudBatch(statements: any, userId: any, guards?: any[], metadata?: Map<any, any>): Promise<any[]>;
+    getCloudResourceMetadata(userId: any, resourceKey: any): Promise<any>;
+    listCloudResourceRows(userId: any): Promise<{
+        gaps: any[];
+    }>;
+    _cloudRecord(row: any): Promise<{
+        id: any;
+        userId: any;
+        kind: any;
+        data: any;
+        updatedAt: any;
+    }>;
+    putCloudDataRecord(userId: any, kind: any, id: any, data: any, { idempotencyKey, createOnly, leaseToken, work }?: {
+        idempotencyKey?: any;
+        createOnly?: boolean;
+    }): Promise<{
+        id: any;
+        userId: any;
+        kind: any;
+        data: any;
+        updatedAt: any;
+    }>;
+    getCloudDataRecord(userId: any, kind: any, id: any): Promise<{
+        id: any;
+        userId: any;
+        kind: any;
+        data: any;
+        updatedAt: any;
+    }>;
+    getCloudDataRecordByIdempotency(userId: any, kind: any, idempotencyKey: any): Promise<{
+        id: any;
+        userId: any;
+        kind: any;
+        data: any;
+        updatedAt: any;
+    }>;
+    _cloudRecordForList(row: any): Promise<{
+        id: any;
+        userId: any;
+        kind: any;
+        data: any;
+        updatedAt: any;
+    }>;
+    listCloudDataRecords(userId: any, kind: any): Promise<any[]>;
+    listCloudDataRecordsAcrossUsers(kind: any): Promise<any[]>;
+    claimCloudDataRecord(userId: any, kind: any, id: any, leaseMs: any, leaseToken?: any): Promise<boolean>;
+    releaseCloudDataRecord(userId: any, kind: any, id: any, leaseToken: any): Promise<void>;
+    renewCloudDataRecordLease(userId: any, kind: any, id: any, leaseMs: any, leaseToken: any): Promise<boolean>;
+    deleteCloudDataRecord(userId: any, kind: any, id: any): Promise<boolean>;
+    cleanupCloudDataRecords(kind: any, beforeMs: any): Promise<any>;
+    listDueCloudDataOperations(now?: number, limit?: number): Promise<any[]>;
+    cleanupExpiredCloudDataRecords(now?: number, limit?: number): Promise<any>;
+    getCloudMaintenanceBatch(name: any, table: any, limit?: number): Promise<{
+        rows: any[];
+        completed: boolean;
+        upperBound?: undefined;
+        cursor?: undefined;
+    } | {
+        rows: any;
+        upperBound: any;
+        cursor: any;
+        completed: boolean;
+    }>;
+    finishCloudMaintenanceBatch(name: any, cursor: any, completed: any): Promise<void>;
+    indexCloudDataRecordWork(userId: any, kind: any, id: any, work: any, expectedWriteToken?: any): Promise<void>;
+    readCloudMaintenanceRecord(row: any): Promise<{
+        id: any;
+        userId: any;
+        kind: any;
+        data: any;
+        updatedAt: any;
+    }>;
+    repairCloudResourceMetadata(limit?: number): Promise<void>;
+    /** One explicit repair, or a bounded upgrade batch; never called as a recurring sweep. */
+    cleanupCloudResourceMetadata(userId?: any, range?: any): Promise<any>;
+    listCloudOwners(userId: any): Promise<any>;
+    getCloudOwner(userId: any, owner: any): Promise<{
+        active: boolean;
+        generation: any;
+        updatedAt: any;
+    }>;
+    setCloudOwnerActive(userId: any, owner: any, active: any, expectedGeneration: any): Promise<{
+        active: boolean;
+        generation: any;
+        updatedAt: any;
+    }>;
+    isCloudOwnerGuardValid(userId: any, guard: any): Promise<boolean>;
+    /** Delete only the exact physical snapshot; no untrusted SQL identifiers. */
+    deleteCloudResourceRows(userId: any, locators: any, { operationId, leaseToken }?: {}): Promise<{
+        deleted: number;
+        changed: number;
+    }>;
     initSchema(): Promise<{
         columnsCreated: number;
         indexesCreated: number;
@@ -76,14 +174,15 @@ export class D1Adapter {
      * 构变了而老部署没跑过 initSchema 时，cron 会每分钟静默挂在缺的那一列上，
      * 界面上一切正常——这个方法就是让宿主查得出来。
      *
-     * @returns {Promise<{ tables: Record<string, string[]>, indexes: string[] }>}
+     * @returns {Promise<{ tables: Record<string, string[]>, indexes: string[], triggers: string[] }>}
      */
     describeSchema(): Promise<{
         tables: Record<string, string[]>;
         indexes: string[];
+        triggers: string[];
     }>;
     dropSchema(): Promise<void>;
-    createTask(params: any): Promise<any>;
+    createTask(params: any, cloudGuard?: any): Promise<any>;
     /**
      * 建新任务的同时取消旧的那条（`POST /schedule-message` 的 supersedesUuid）。
      *
@@ -96,7 +195,7 @@ export class D1Adapter {
      * @returns {Promise<Object>} createTask 的返回行 + `superseded`（旧行是否
      *   真的被删掉；false = 旧行本就不存在）
      */
-    createTaskSuperseding(params: import("./interface.js").InsertTaskParams, supersedesUuid: string): Promise<any>;
+    createTaskSuperseding(params: import("./interface.js").InsertTaskParams, supersedesUuid: string, cloudGuard?: any): Promise<any>;
     getTaskByUuid(uuid: any, userId: any): Promise<any>;
     getTaskByUuidOnly(uuid: any): Promise<any>;
     /**
@@ -109,7 +208,7 @@ export class D1Adapter {
     getTaskStatusByUuidOnly(uuid: string): Promise<{
         status: string;
     } | null>;
-    updateTaskById(taskId: any, updates: any): Promise<any>;
+    updateTaskById(taskId: any, updates: any, cloudGuard?: any): Promise<any>;
     /**
      * 按 uuid 改一条 pending 任务（PUT /update-message、fire hook 的 renewTask）。
      *
@@ -119,7 +218,7 @@ export class D1Adapter {
      * ——用户以为改期生效了，实际什么都没留下。正文这类字段不受这道门约束：它们
      * 只影响以后的触发，收尾那边本来就不会覆盖（见 run-tick 的收尾守卫）。
      */
-    updateTaskByUuid(uuid: any, userId: any, encryptedPayload: any, extraFields: any): Promise<{
+    updateTaskByUuid(uuid: any, userId: any, encryptedPayload: any, extraFields: any, cloudGuard?: any): Promise<{
         uuid: any;
         updated_at: string;
     }>;
@@ -160,7 +259,7 @@ export class D1Adapter {
      * @returns {Promise<boolean>} true = 领到了；false = 别人正拿着租约、同分组
      *   有任务正在跑、排期被改过、或行已不是 pending
      */
-    claimTask(taskId: number, expectedNextSendAt: string, leaseUntil: string | Date, serializeGroup?: string | null): Promise<boolean>;
+    claimTask(taskId: number, expectedNextSendAt: string, leaseUntil: string | Date, serializeGroup?: string | null, cloudGuard?: any): Promise<boolean>;
     /**
      * 投递期间的租约续期（run-tick 的心跳用）。只在行仍是 pending 且确实持有
      * 租约（lease_until 非空）时生效——收尾把租约放掉之后，迟到的心跳不会把
@@ -170,7 +269,7 @@ export class D1Adapter {
      * @param {string|Date} leaseUntil - 新的租期末尾
      * @returns {Promise<boolean>} true = 续上了
      */
-    renewTaskLease(taskId: number, leaseUntil: string | Date): Promise<boolean>;
+    renewTaskLease(taskId: number, leaseUntil: string | Date, cloudGuard?: any): Promise<boolean>;
     listTasks(userId: any, opts?: {}): Promise<{
         tasks: any;
         total: number;
@@ -241,7 +340,7 @@ export class D1Adapter {
         key?: string;
         keyPrefix?: string;
         updatedAt: number;
-    }>, now?: number): Promise<{
+    }>, now?: number, cloudGuard?: any): Promise<{
         upserted: number;
         skipped: number;
         outcomes: boolean[];
@@ -377,7 +476,7 @@ export class D1Adapter {
     upsertLlmCredentials(userId: string, entries: Array<{
         credId: string;
         encryptedValue: string;
-    }>): Promise<number>;
+    }>, cloudGuard?: any): Promise<number>;
     /**
      * 按 cred_id 批量读这个用户的凭据行（`encrypted_value` 是密文，解密在上
      * 层）。排程时的存在性检查和 fire 时的解析共用这一个口。
@@ -456,7 +555,7 @@ export class D1Adapter {
         total_messages?: number | null;
         payload: string;
         created_at: number;
-    }>): Promise<number>;
+    }>, cloudGuard?: any): Promise<number>;
     /**
      * 把这一批标记为「Web Push 已发出」。发送失败的段不标——delivered_at 为
      * null 的行正是客户端最需要拉的那部分。

package/dist/adapters/interface.d.ts

@@ -49,6 +49,7 @@ export type DbAdapter = {
     describeSchema?: () => Promise<{
         tables: Record<string, string[]>;
         indexes: string[];
+        triggers?: string[];
     }>;
     /**
      *   Drop the scheduled_messages table (CASCADE).

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

@@ -53,15 +53,28 @@ export const SQLITE_ALL_INDEXES: {
     description: string;
     critical: boolean;
 }[];
+export const CLOUD_DATA_TABLES_SQL: string[];
+export const CLOUD_DATA_WORK_TABLES_SQL: string[];
+export const CLOUD_DATA_WORK_INDEXES: {
+    name: string;
+    sql: string;
+    description: string;
+    critical: boolean;
+}[];
+export const CLOUD_DATA_DELETE_TRIGGERS: {
+    name: string;
+    sql: string;
+}[];
 /**
  * 这一版代码跑起来需要的表 / 列 / 索引。
  *
  * 索引只列 critical 的那几个（uidx_uuid 之类）：其余索引缺了只是慢，缺了它则
  * 是正确性问题。
  *
- * @type {{ tables: Record<string, string[]>, indexes: string[] }}
+ * @type {{ tables: Record<string, string[]>, indexes: string[], triggers: string[] }}
  */
 export const SQLITE_REQUIRED_SCHEMA: {
     tables: Record<string, string[]>;
     indexes: string[];
+    triggers: string[];
 };