diff --git a/tests/cmc-upgrade-kernel-test.md b/tests/cmc-upgrade-kernel-test.md
index c6c49a2..225389f 100644
--- a/tests/cmc-upgrade-kernel-test.md
+++ b/tests/cmc-upgrade-kernel-test.md
@@ -26,6 +26,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including CM
 ## CMC Tooling
 - For all CMC-related actions in this test, use the `cirrusdata` skill/CLI path.
 - Exception: host cleanup is not handled by that skill yet; use the Cirrus Data MCP tools for offline-host cleanup and cloned-host cleanup.
+- After the cloned VM is deleted from vCenter, immediately remove the matching cloned host entry and migration sessions from the CMC project; do not wait for the CMC UI to mark the deleted clone host offline.
 - For every CMC install command in this test, always include installer option: `-no-prebuilt-mtdi-nexus`.
 
 ## Kernel Package Rules
@@ -103,7 +104,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including CM
 - [ ] 16. Determine the base clone name `aw999-[source-without-atvmxxx-]`. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 17. From vCenter, check whether the base clone name already exists. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 18. If needed, choose the next available suffixed clone name using `aw999-[source-without-atvmxxx-]-1`, then `-2`, then `-N` as needed. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
-- [ ] 19. From vCenter, clone the source VM on `AutomatedTest-UnitTesting` using the resolved clone VM name from steps 16-18, pass only the clone VM name as the destination, and default it to `CDS1-ESX165` / `192.168.1.165` unless overridden. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
+- [ ] 19. From vCenter, clone the source VM on `AutomatedTest-UnitTesting` using the resolved clone VM name from steps 16-18, pass only the clone VM name as the destination, default it to `CDS1-ESX165` / `192.168.1.165` unless overridden, and explicitly use `govc vm.clone -on=false` so the cloned VM remains powered off until after FC PCI passthrough removal is complete. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 20. From vCenter, detach the 2 FC PCI adapters from the cloned VM. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 21. From vCenter, verify both FC passthrough devices are no longer present on the clone. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 22. From vCenter, power on the clone. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
@@ -158,7 +159,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including CM
 - [ ] 71. Only after steps 66-70 all pass, begin success-path cleanup. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 72. From vCenter, power off the cloned machine. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 73. From vCenter, delete the cloned VM and its disks from inventory. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
-- [ ] 74. Using Cirrus Data MCP tools, run final host cleanup for `skidamarink`, remove the cloned host entry for this test clone only, and verify the cloned host entry plus all migration sessions for the cloned host are gone. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
+- [ ] 74. Using the Cirrus Data Cloud skill and Cirrus Data MCP tools after the cloned VM has been deleted from vCenter, immediately remove the cloned host entry for this test clone only from `skidamarink` and verify the cloned host entry plus all migration sessions for the cloned host are gone; do not wait for the CMC UI to mark the deleted clone host offline. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 75. Blocker-fail path after clone creation, as an alternate to steps 71-74: leave the cloned VM powered on and present in inventory for manual inspection, then continue to step 76. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.
 - [ ] 76. Append the current run only to `/home/cirrus/cds/tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-results.md` with the required host metadata, kernel progression, execution summary, final outcome, and total test duration; do not create or update any other result, run-specific result, or summary files. Verify this step completed successfully, then re-read `tests/cmc-upgrade-kernel-test.md` to confirm the next step before performing it.