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/watcher-service/atvm_run_watcher.py

@@ -532,13 +532,18 @@ def build_status_markdown(
         f"- integration/plugin path: `{metadata['integration_plugin']}`",
         f"- scope of this run: {metadata['scope_description']}",
         "",
-        "**FUNCTIONALLY:**",
-        "- verify VM setup and power state",
-        "- power on, obtain IP address, and verify hostname reachability",
-        "- uninstall existing CMC if present",
-        "- prepare source and destination disks and validate source-side data",
-        "- install CMC and execute the requested ATVM migration workflow",
-        "- finalize reporting, cleanup, and the final `check-xml-files.ts` validation step",
+        "**TEST 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",
         "",
         "**SUMMARY:**",
         "",