diff --git a/tests/cmc-upgrade-test.md b/tests/cmc-upgrade-kernel-test.md
similarity index 92%
rename from tests/cmc-upgrade-test.md
rename to tests/cmc-upgrade-kernel-test.md
index bcddf01..6d25dc8 100644
--- a/tests/cmc-upgrade-test.md
+++ b/tests/cmc-upgrade-kernel-test.md
@@ -1,4 +1,4 @@
-# CMC Upgrade Test Template
+# CMC Upgrade Kernel Test Template
 
 ## Purpose
 Validate CMC behavior across staged kernel upgrades on a cloned VM, including reinstall, migration health, service health, and cleanup.
@@ -51,7 +51,8 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
 ## Safety Rules
 - Delete only the clone created for this test.
 - If the clone is missing or identity is uncertain, stop and do not delete any other VM.
-- If kernel availability checks do not meet criteria, stop, power off clone, and remove clone/disks.
+- If any blocker occurs after clone creation, stop the test and leave the cloned VM powered on for manual inspection.
+- Do not delete or power off the clone on blocker-fail outcomes.
 
 ## Test Procedure
 1. Remove offline hosts in `skidamarink` using MCP offline-host cleanup.
@@ -103,11 +104,15 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including re
 41. Create a local migration (10GB -> 11GB) via `cirrusdata` and wait for initial sync completion.
 42. Confirm machine is online in `skidamarink` using `cirrusdata`.
 43. SSH and verify MTDI, Galaxy Migrate services/driver are up.
-44. Power off cloned machine.
-45. Delete cloned VM and its disks from vCenter inventory.
-46. Final cleanup checkpoint:
+44. Success-path cleanup only: power off cloned machine.
+45. Success-path cleanup only: delete cloned VM and its disks from vCenter inventory.
+46. Success-path final cleanup checkpoint:
    - Run MCP offline-host cleanup for `skidamarink`.
    - If the cloned VM is still marked online at the end of the test, remove that cloned VM host entry specifically.
+47. Blocker-fail path after clone creation:
+   - Stop test immediately after recording failure details.
+   - Leave cloned VM powered on and present in inventory for manual inspection.
+   - Do not run clone power-off/delete steps in blocker-fail path.
 
 ## Stop Conditions
 - Cannot verify clone identity.
@@ -153,7 +158,7 @@ Use one cumulative results file and append one new section per tested host.
 - Local migration #2 (10GB -> 11GB) initial sync: `PASS|FAIL` - notes
 - Online in skidamarink after latest upgrade: `PASS|FAIL` - notes
 - MTDI/Galaxy Migrate service+driver health after latest upgrade: `PASS|FAIL` - notes
-- Clone power off and deletion: `PASS|FAIL` - notes
+- Clone power off and deletion (success path only): `PASS|FAIL|N/A` - notes
 
 ### Final Outcome
 - Overall result: `PASS|FAIL|PARTIAL`