feat(db): Add query logging to migration script

[marcodejongh]

Summary

Add verbose logging to the migration script for better visibility in CI builds.

Changes

• Log timestamp + first 200 chars of each SQL query as it executes
• Show total migrations in journal before running

Example Output

🔄 Running migrations on: ep-dry-night-a67fnzaz-pooler.us-west-2.aws.neon.tech
📋 Found 27 migrations in journal
[17:05:23] INSERT INTO board_climbs (board_type, uuid, layout_id, ...) SELECT 'kilter', uuid, layout_id...
[17:07:45] DELETE FROM board_beta_links WHERE climb_uuid NOT IN (SELECT uuid FROM board_climbs)...
[17:08:12] ALTER TABLE "board_beta_links" ADD CONSTRAINT "board_beta_links_climb_fk"...
✅ Migrations completed successfully

Why

Long-running migrations (like the unified tables migration) give no feedback in CI. This makes it hard to know if a migration is stuck or just slow.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
boardsesh	Building		Jan 4, 2026 6:40am

[claude]

Claude Review

✅ Ready to merge - Minor issues noted below, but nothing blocking.

Issues

1. Missing error handling for journal file (packages/db/scripts/migrate.ts:84): fs.readFileSync will throw if the journal file doesn't exist or is malformed JSON. Consider wrapping in try-catch or checking file existence first to provide a clearer error message.

2. Logs total migrations, not pending (packages/db/scripts/migrate.ts:85): The log says "Found X migrations in journal" but this shows total migrations, not pending ones. The wording could be misleading - consider clarifying this is the total count or actually computing pending migrations by checking the drizzle_migrations table.