Wait for all app workloads before marking deployments running.

Deployment success now reflects readiness across the application, database, and enabled add-on workloads so scheduling or resource failures do not appear as a running app.

Co-authored-by: Cursor <cursoragent@cursor.com>

backend/src/deployments/deployments.service.ts

@@ -92,7 +92,17 @@ export class DeploymentsService {
         }
       }
 
-      // Step 4: Mark success
+      // Step 4: wait for every workload owned by this app before marking it running.
+      // Helm/API apply success only means resources were accepted; quota or scheduling
+      // pressure can still leave DB/addon/app pods Pending.
+      this.buildService.setProgress(deploymentId, {
+        phase: 'deploying',
+        percent: 96,
+        message: 'Waiting for all application pods to become ready...',
+      });
+      await this.kubernetesService.waitForApplicationReady(app);
+
+      // Step 5: Mark success
       this.buildService.setProgress(deploymentId, {
         phase: 'done',
         percent: 100,