@celilo/cli 0.21.0 → 0.23.0

package/src/test-utils/setup-test-db.ts

@@ -1,30 +1,20 @@
 import { existsSync } from 'node:fs';
 import { unlink } from 'node:fs/promises';
-import { join } from 'node:path';
 import { migrate } from 'drizzle-orm/bun-sqlite/migrator';
-import { type DbClient, createDbClient } from '../db/client';
+import { type DbClient, createDbClient, findMigrationsFolder } from '../db/client';
 
-/**
- * Find migrations folder relative to current working directory
- */
-function findMigrationsFolder(): string {
-  // Try common locations
-  const candidates = [
-    './drizzle', // Running from backend directory
-    './backend/drizzle', // Running from celilo directory
-    join(process.cwd(), 'drizzle'), // Absolute from backend
-    join(process.cwd(), 'backend', 'drizzle'), // Absolute from celilo
-  ];
-
-  for (const candidate of candidates) {
-    const metaPath = join(candidate, 'meta', '_journal.json');
-    if (existsSync(metaPath)) {
-      return candidate;
-    }
-  }
-
-  throw new Error(`Could not find drizzle migrations folder. Tried: ${candidates.join(', ')}`);
-}
+// `findMigrationsFolder` is imported from db/client rather than redefined here.
+// This file used to carry its own copy, and the copy had drifted: it listed
+// only CWD-RELATIVE candidates (`./drizzle`, `process.cwd()/drizzle`, …) and was
+// missing the `join(currentDir, '../../drizzle')` fallback that resolves
+// relative to the source file.
+//
+// The effect was invisible from `apps/celilo` and total from the repo root —
+// which is where CLAUDE.md says to run the gate. Every suite using
+// setupTestDatabase threw here, left `db` unassigned, and then failed again in
+// its own afterEach on `db.$client`, so one missing path candidate presented as
+// hundreds of unrelated-looking assertion failures (celilo: 668 across the
+// repo, 341 in apps/celilo/src alone).
 
 /**
  * Setup test database with real migrations