Fix 001_init.js to follow proper migration pattern

- Changed from standalone script to proper migration with exports.up/down
- Removed process.exit() calls that were terminating the migration runner
- Removed immediate execution of runMigrations()
- Now properly exports migration functions like other migrations

This was the root cause - 001_init.js was executing immediately when
required and calling process.exit(), preventing it from being run as
a migration and causing 029 to run first on an empty database.

backend/migrations/run-migrations-safe.js

@@ -141,6 +141,7 @@ async function runMigrations() {
           const numB = parseInt(baseB.split('_')[0]);
           return numA - numB;
         });
+      console.log('Migration files in order:', migrationFiles.map(f => path.basename(f)));
     } else {
       // For existing deployments, run all migrations (legacy + core)
       console.log('Existing deployment detected - checking all migrations');