cursedbelt-server 4.40.0 → 4.40.2

package/dist/server/d1/pullD1.js

@@ -287,6 +287,15 @@ export async function pullD1ToSqlite(options) {
         // `exec`, not `run`: each is many statements and `run` would execute only the first,
         // leaving a file with a schema and no rows that looks perfectly valid.
         db.exec(options.schemaSql);
+        // 🔴 The schema's TRIGGERS come off for the load and go back on after it. A trigger fires on
+        // every restored row as if it were a new write: measured 2026-09-29, collections' api-cache
+        // stamp triggers (AFTER INSERT ON items → a `meta` row) wrote `meta` during the `items` load,
+        // and `meta`'s own rows then refused with `UNIQUE constraint failed: meta.key` — every
+        // nightly backup of an app with such a trigger would have failed. D1's rows are already the
+        // triggers' results; the snapshot needs the triggers only for what happens AFTER it.
+        const triggers = db.query("SELECT name, sql FROM sqlite_master WHERE type = 'trigger' AND sql IS NOT NULL").all();
+        for (const t of triggers)
+            db.exec(`DROP TRIGGER ${sqlIdent(t.name)}`);
         // 🔴 A table D1 holds that the schema does not declare is created from D1's OWN DDL, never
         // dropped: measured on music's first post-cutover pull (2026-09-23), `art_lookups` — a
         // cache its art job creates where it first needs it — made the whole pull refuse with
@@ -301,6 +310,8 @@ export async function pullD1ToSqlite(options) {
         for (const { text } of dumps)
             if (text)
                 db.exec(text);
+        for (const t of triggers)
+            db.exec(t.sql);
         if (options.afterLoadSql)
             db.exec(options.afterLoadSql);
         // 🔴 Every table holds as many rows as were read from D1, or this is not a backup: the check

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "cursedbelt-server",
-	"version": "4.40.0",
+	"version": "4.40.2",
 	"license": "ISC",
 	"type": "module",
 	"description": "The app-facing Bun/Hono server tier of the cursedbelt split — storage, sharing, activity, guard, sync. React-free; cursedbelt-core below it.",
@@ -352,7 +352,7 @@
 	"dependencies": {
 		"argon2id": "1.0.1",
 		"cursedbelt-core": "^2.1.1",
-		"cursedops": ">=0.8.1 <0.11.0",
+		"cursedops": ">=0.8.1 <0.12.0",
 		"cwip": "^4.6.0",
 		"jose": "^6.2.3"
 	},

package/src/server/d1/pullD1.spec.ts

@@ -290,6 +290,29 @@ describe('pulling D1 down — paged SELECTs, table by table, never an export', (
 		expect(row?.art_key).toBe('art/1');
 	});
 
+	test('🔴 a schema TRIGGER does not fire on the restored rows, and is in the snapshot after (collections, 2026-09-29)', async () => {
+		const dir = scratch();
+		const schema = `${SCHEMA}
+CREATE TRIGGER items_stamp AFTER INSERT ON items BEGIN
+  INSERT INTO meta (key, value) VALUES ('v', 1) ON CONFLICT(key) DO UPDATE SET value = value + 1;
+END;`;
+		const source = new Database(':memory:');
+		source.exec(schema);
+		source.exec("INSERT INTO items VALUES ('a', 'x'); INSERT INTO items VALUES ('b', 'y');");
+		await pullD1ToSqlite({
+			destination: join(dir, 'pulled.sqlite'),
+			database: 'collections',
+			schemaSql: schema,
+			requiredTable: 'items',
+			afterLoadSql: REBUILD,
+			wrangler: d1(source).run,
+		});
+		const db = opened(dir);
+		expect(Number((db.query("SELECT value FROM meta WHERE key = 'v'").get() as { value: unknown }).value)).toBe(2);
+		expect(db.query("SELECT name FROM sqlite_master WHERE type = 'trigger'").all()).toEqual([{ name: 'items_stamp' }]);
+		db.close();
+	});
+
 	test('🔴 a database without the required table is refused as the wrong one', async () => {
 		const dir = scratch();
 		await expect(

package/src/server/d1/pullD1.ts

@@ -346,6 +346,17 @@ export async function pullD1ToSqlite(options: PullD1Options): Promise<void> {
 		// `exec`, not `run`: each is many statements and `run` would execute only the first,
 		// leaving a file with a schema and no rows that looks perfectly valid.
 		db.exec(options.schemaSql);
+		// 🔴 The schema's TRIGGERS come off for the load and go back on after it. A trigger fires on
+		// every restored row as if it were a new write: measured 2026-09-29, collections' api-cache
+		// stamp triggers (AFTER INSERT ON items → a `meta` row) wrote `meta` during the `items` load,
+		// and `meta`'s own rows then refused with `UNIQUE constraint failed: meta.key` — every
+		// nightly backup of an app with such a trigger would have failed. D1's rows are already the
+		// triggers' results; the snapshot needs the triggers only for what happens AFTER it.
+		const triggers = db.query("SELECT name, sql FROM sqlite_master WHERE type = 'trigger' AND sql IS NOT NULL").all() as {
+			name: string;
+			sql: string;
+		}[];
+		for (const t of triggers) db.exec(`DROP TRIGGER ${sqlIdent(t.name)}`);
 		// 🔴 A table D1 holds that the schema does not declare is created from D1's OWN DDL, never
 		// dropped: measured on music's first post-cutover pull (2026-09-23), `art_lookups` — a
 		// cache its art job creates where it first needs it — made the whole pull refuse with
@@ -359,6 +370,7 @@ export async function pullD1ToSqlite(options: PullD1Options): Promise<void> {
 		}
 		// One table at a time, so a fault is located rather than smeared over the whole load.
 		for (const { text } of dumps) if (text) db.exec(text);
+		for (const t of triggers) db.exec(t.sql);
 		if (options.afterLoadSql) db.exec(options.afterLoadSql);
 		// 🔴 Every table holds as many rows as were read from D1, or this is not a backup: the check
 		// that makes a silently truncated load (task 2128's NUL padding, or whatever does it next)