Fix duplicate watcher posts and restore 22-step E2E flow

atvm/docs/automation/run-learnings.md

@@ -205,21 +205,25 @@ This file stores run-specific examples only when a run produced a new learning r
     - `1. Verifying set up`
     - `2. Power on and obtain ip address and host name`
     - `3. Uninstall CMC if still exists`
-    - `4. Setting up disk`
+    - `4. Setting up disk on the host`
     - `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`
-    - `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`
+    - `10. Verify data for cmotion`
+    - `11. Trigger revert cmotion and do I/O test before and during cmotion`
+    - `12. Verify data for revert cmotion`
+    - `13. Trigger cmotion again`
+    - `14. Finalize cutover`
+    - `15. Create migration report`
+    - `16. Delete migration session`
+    - `17. Verify local destination disk`
+    - `18. Remove enabled FC integration`
+    - `19. Remove host and volumes`
+    - `20. Uninstall CMC`
+    - `21. Clean up iSCSI targets`
+    - `22. Power off`
 
 ## Run Learning: 2026-03-27 (Start watcher before runner when watcher is requested)
 - Observed failure mode:
@@ -240,3 +244,11 @@ This file stores run-specific examples only when a run produced a new learning r
   - Do not rely only on `/tmp/<build-name>.log` for non-categorized watcher result recovery.
   - When final `check-xml-files.ts` validation is present but host XML is absent, recover host completion from the latest matching per-host reporter artifact within the run window.
   - Keep non-categorized watcher notes accurate; do not describe that failure as a categorized sub-run issue.
+
+## Run Learning: 2026-03-27 (Non-categorized watcher runs must post once and show the full 22-step E2E flow)
+- Observed failure mode:
+  - A non-categorized watcher run for `cmc-e2e` sent two Mattermost posts for the same build.
+  - The posted `TEST FLOW:` list only showed 18 steps even though the current `cmc-e2e` ATVM flow has 22 steps.
+- Action for future runs:
+  - For non-categorized runs, post only the parent run status and do not also post the single synthetic subrun.
+  - Keep the static `cmc-e2e` watcher flow aligned with the current 22-step ATVM E2E sequence.