Require explicit confirmation for reboot plugin both

atvm/docs/automation/run-learnings.md

@@ -426,3 +426,13 @@ This file stores run-specific examples only when a run produced a new learning r
   - If this failure recurs, treat it as a host/storage investigation first, not just a watcher-formatting issue.
   - Check whether the FC reboot-validation step actually created `diskname2Reboot.md5` on `/root/tmp/fcDisk` before the md5 verification step ran.
   - Check whether repeated iSCSI auth failures or multipath churn during the same boot window are interfering with the expected disk/file state.
+
+## Run Learning: 2026-03-30 (`cmc-reboot` with Pure `both` needs an explicit warning/confirmation gate)
+- Observed operator requirement:
+  - For reboot runs, using both FC and iSCSI together is not a normal default choice.
+  - There may be a "chicken before the egg" timing problem where iSCSI disks are not attached before mTDI / CMC services start.
+  - The operator wants `both` on `cmc-reboot` to trigger a warning and an explicit reconfirmation instead of being treated like a routine plugin selection.
+- Action for future runs:
+  - If a planned `cmc-reboot` command includes `--use_specified_plugin both`, call out the FC+iSCSI timing risk before execution.
+  - Ask the operator to explicitly confirm that `both` is really intended for that reboot run.
+  - Otherwise prefer `fc` or `iscsi`, but not both.