Show full template test flow in ATVM status

atvm/docs/automation/run-learnings.md

@@ -195,22 +195,31 @@ This file stores run-specific examples only when a run produced a new learning r
 
 ## Run Learning: 2026-03-27 (Replace FUNCTIONALLY with TEST FLOW in status output)
 - Observed requirement:
-  - The operator wants the status format to show the generic numbered ATVM test flow rather than a vague high-level `FUNCTIONALLY:` summary.
+  - The operator wants the status format to show the full numbered ATVM test flow for the active template rather than a vague high-level `FUNCTIONALLY:` summary.
+  - Each ATVM template can have its own test-flow step list.
   - The step list should appear once for the whole run, not repeated per host.
 - Action for future runs:
   - Replace the `FUNCTIONALLY:` section with `TEST FLOW:` in ATVM status output.
-  - Use the generic numbered run flow:
+  - Resolve `TEST FLOW:` from the ATVM template name instead of hardcoding one shared list for every template.
+  - For `cmc-e2e`, use this numbered run flow:
     - `1. Verifying set up`
     - `2. Power on and obtain ip address and host name`
-    - `3. Uninstall cmc if still exist`
+    - `3. Uninstall CMC if still exists`
     - `4. Setting up disk`
-    - `5. Copy cmc install command from GUI`
-    - `6. Install cmc`
+    - `5. Copy CMC install command from GUI`
+    - `6. Install CMC`
     - `7. Create migration session`
     - `8. Tracking Changes`
     - `9. Trigger cmotion and do I/O test before actual cutover`
-    - `...`
-    - `22. Power off`
+    - `10. Verify migration remains healthy during I/O activity`
+    - `11. Prepare for cutover`
+    - `12. Stop application / stop test I/O`
+    - `13. Run final sync`
+    - `14. Confirm destination is fully up to date`
+    - `15. Perform cutover`
+    - `16. Validate destination host / disk state`
+    - `17. Run post-cutover checks`
+    - `18. Power off`
 
 ## Run Learning: 2026-03-27 (Start watcher before runner when watcher is requested)
 - Observed failure mode: