Clean error alerts and harden startup migration

JobTrackerApi/Program.cs

@@ -60,11 +60,17 @@ builder.Services.AddDbContext<JobTrackerContext>((sp, options) =>
         // Avoid ServerVersion.AutoDetect here because it forces an immediate DB connection
         // during service registration, which can crash the API if MariaDB is temporarily
         // unavailable or on a different network during deploy startup.
-        options.UseMySql(cs, new MariaDbServerVersion(new Version(11, 0, 0)));
+        options.UseMySql(cs, new MariaDbServerVersion(new Version(11, 0, 0)), mysql =>
+        {
+            mysql.MigrationsAssembly("JobTrackerApi");
+        });
     }
     else
     {
-        options.UseSqlite(cs);
+        options.UseSqlite(cs, sqlite =>
+        {
+            sqlite.MigrationsAssembly("JobTrackerApi");
+        });
     }
 
     // We create Identity tables on startup in environments where `dotnet ef` isn't available.

JobTrackerApi/Services/StartupInitializationExtensions.cs

@@ -870,7 +870,17 @@ public static class StartupInitializationExtensions
                 }
             }
 
-            db.Database.Migrate();
+            try
+            {
+                using var migrationScope = app.Services.CreateScope();
+                var migrationDb = migrationScope.ServiceProvider.GetRequiredService<JobTrackerContext>();
+                migrationDb.Database.Migrate();
+            }
+            catch (Exception ex)
+            {
+                app.Logger.LogError(ex, "Database migration failed during startup initialization.");
+                throw;
+            }
 
             // Optional: seed an initial admin user for local username/password login.
             // Set Auth:AdminEmail and Auth:AdminPassword to enable.