Replace FUNCTIONALLY with TEST FLOW in ATVM status output

- update the ATVM status template to replace the FUNCTIONALLY section with a TEST FLOW section that shows the generic numbered run steps once for the whole test
- update the ATVM automation guide to describe TEST FLOW as the standard status-report section instead of FUNCTIONALLY
- update the watcher-generated status output so Mattermost and local status responses use the same TEST FLOW section
- add a 2026-03-27 run learning recording the move from FUNCTIONALLY to TEST FLOW for future ATVM reporting

atvm/docs/automation/run-learnings.md

@@ -192,3 +192,22 @@ This file stores run-specific examples only when a run produced a new learning r
 - Action for future runs:
   - Do not mention expected, harmless `reset-failed` output in routine run updates.
   - Only mention it if it actually prevents watcher startup or becomes relevant to debugging.
+
+## 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 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:
+    - `1. Verifying set up`
+    - `2. Power on and obtain ip address and host name`
+    - `3. Uninstall cmc if still exist`
+    - `4. Setting up disk`
+    - `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`