Fix wait command to always check replica count

Previously, the wait command would trust UpdateStatus.State when present
without verifying that all replicas were actually running. This could
cause the command to exit successfully even when some tasks were still
starting or had failed.

Now we always check that running tasks match total tasks before
considering a service as done, matching the behavior of docker-stack-wait.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: firecow

src/commands/wait-cmd.ts

@@ -44,14 +44,14 @@ export async function handler (args: ArgumentsCamelCase) {
         tasks = await dockerode.listTasks({filters: {"label": [`com.docker.stack.namespace=${appName}`], "desired-state": ["running"]}}) as Task[];
 
         for (const s of services) {
-            if (s.UpdateStatus?.State) {
+            const runningTasks = tasks.filter((t) => t.Status.State === "running" && t.ServiceID === s.ID);
+            const totalTasks = tasks.filter((t) => t.ServiceID === s.ID);
+
+            // Always check replica count first
+            if (totalTasks.length > runningTasks.length) {
+                serviceStateMap.set(s.ID, "replicating");
+            } else if (s.UpdateStatus?.State && !["completed", "rollback_completed"].includes(s.UpdateStatus.State)) {
                 serviceStateMap.set(s.ID, s.UpdateStatus.State);
-            } else {
-                const runningTasks = tasks.filter((t) => t.Status.State === "running" && t.ServiceID === s.ID);
-                const totalTasks = tasks.filter((t) => t.ServiceID === s.ID);
-                if (totalTasks.length > runningTasks.length) {
-                    serviceStateMap.set(s.ID, "replicating");
-                }
             }
         }