refactor: consolidate drizzle config files (#202)

This PR consolidates the duplicated PostgreSQL drizzle config files.

**Changes:**
- Renamed `drizzle.config.ts` → `drizzle.config.sqlite.ts` for clarity
- Removed duplicate `drizzle.config.pg.ts` (kept
`drizzle.config.postgres.ts` as the canonical PostgreSQL config)
- Updated test/setup.ts and CONTRIBUTING.md with new references

Fixes #201

Generated with [Claude Code](https://claude.ai/code)

---------

Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>

Author: mcowger

.github/workflows/generate-migrations.yml

@@ -42,7 +42,7 @@ jobs:
 
       - name: Generate PostgreSQL migrations
         working-directory: packages/backend
-        run: bunx drizzle-kit generate --config drizzle.config.pg.ts
+        run: bunx drizzle-kit generate --config drizzle.config.postgres.ts
 
       - name: Check for new migrations
         id: check

.github/workflows/release.yml

@@ -50,7 +50,7 @@ jobs:
           # the last migration was committed — the release must wait for the
           # generate-migrations workflow to catch up.
           bunx drizzle-kit generate 2>&1 | tee /tmp/sqlite-migrate.log
-          bunx drizzle-kit generate --config drizzle.config.pg.ts 2>&1 | tee /tmp/pg-migrate.log
+          bunx drizzle-kit generate --config drizzle.config.postgres.ts 2>&1 | tee /tmp/pg-migrate.log
 
           if git diff --quiet && [ -z "$(git ls-files --others --exclude-standard drizzle/migrations drizzle/migrations_pg)" ]; then
             echo "✅ No pending migrations — all schema changes have corresponding migration files."

CONTRIBUTING.md

@@ -40,6 +40,15 @@ git reset HEAD -- packages/backend/drizzle/migrations/ packages/backend/drizzle/
 
 Then commit again with only your schema `.ts` files.
 
+## Drizzle Config Files
+
+The project uses separate Drizzle ORM config files for each database dialect:
+
+- `drizzle.config.sqlite.ts` -- SQLite configuration
+- `drizzle.config.postgres.ts` -- PostgreSQL configuration
+
+When running Drizzle Kit commands, specify the appropriate config file with `--config`.
+
 ## Code Style
 
 All code must be formatted with Biome before committing:

packages/backend/drizzle.config.pg.ts

@@ -4,9 +4,11 @@ export default defineConfig({
   schema: './drizzle/schema/postgres',
   out: './drizzle/migrations_pg',
   dialect: 'postgresql',
-  dbCredentials: {
-    url: process.env.DATABASE_URL || 'postgres://postgres:postgres@localhost:5432/plexus',
-  },
+  // dbCredentials not needed for migration generation;
+  // uncomment if using drizzle-kit push/migrate against a live database.
+  // dbCredentials: {
+  //   url: process.env.DATABASE_URL || 'postgres://postgres:postgres@localhost:5432/plexus',
+  // },
   verbose: true,
   strict: true,
   migrations: {

packages/backend/drizzle.config.postgres.ts

@@ -111,11 +111,11 @@ setConfigForTesting(validateConfig(testConfig));
 // in the schema but not yet present in any tracked migration file.
 import { execSync } from 'node:child_process';
 try {
-  execSync('bunx drizzle-kit generate --config=drizzle.config.ts', {
+  execSync('bunx drizzle-kit generate --config=drizzle.config.sqlite.ts', {
     cwd: path.resolve(import.meta.dir, '..'),
     stdio: 'pipe',
   });
-  execSync('bunx drizzle-kit generate --config=drizzle.config.pg.ts', {
+  execSync('bunx drizzle-kit generate --config=drizzle.config.postgres.ts', {
     cwd: path.resolve(import.meta.dir, '..'),
     stdio: 'pipe',
   });