Fix duplicate watcher posts and restore 22-step E2E flow

atvm/docs/automation/status-template.md

@@ -78,21 +78,25 @@ Use this as the default ATVM automation run-status template for:
   - `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`
 - See `/home/aw/code/cds/atvm/docs/automation/examples.md` for `cmc-e2e` examples.
 - Resolve kernel values by cross-referencing hostnames against `/home/aw/code/cds/atvm/inventory/vm-inventory.md`.
 - If no kernel value can be verified from `vm-inventory.md`, use `unknown`.