wip

Author: jopemachine

src/ai/backend/manager/data/deployment/types.py

@@ -157,7 +157,7 @@ class DeploymentSubStatus(enum.StrEnum):
 
     Each lifecycle type can define its own sub-status enum by
     inheriting from this class.  For example, DEPLOYING handlers
-    use ``DeploymentSubStep`` (provisioning, progressing, …).
+    use ``DeploymentSubStep`` (provisioning, rolling_back, …).
     """
 
 
@@ -202,10 +202,11 @@ class DeploymentStatusTransitions:
         need_retry: Target lifecycle when handler fails but can retry
         expired: Target lifecycle when time elapsed in current state
         give_up: Target lifecycle when retry count exceeded
-        rewind: Target lifecycle when handler needs to return to a previous
-            sub-step (e.g. progressing -> provisioning in rolling update).
-            Unlike need_retry, rewind does NOT increment phase_attempts
-            because it represents normal forward progress, not a failure.
+        rewind: Target lifecycle when route mutations were executed but
+            the deployment stays in the same sub-step (e.g. PROVISIONING
+            → PROVISIONING after create/drain).  Unlike need_retry, rewind
+            does NOT increment phase_attempts.  Each rewind creates a
+            separate history record (allow_merge=False) for progress tracking.
     """
 
     success: DeploymentLifecycleStatus | None = None