docs(atvm): require explicit approval before any atvm_prep execution

AGENTS.md

@@ -14,6 +14,7 @@ Always let the user review the proposed commit scope and commit message first, a
 ## ATVM Prep Script Guardrail
 
 - Do not run `/root/atvm_prep/atvm_prep.py` unless the operator explicitly asks for an `atvm_prep` task.
+- For any `atvm_prep` execution request, always show the planned command first and wait for explicit operator approval before running it.
 
 ## Exact VM Name Guardrail
 

atvm/AGENTS.md

@@ -104,6 +104,7 @@ This file defines how to operate and maintain the ATVM workspace in `/home/aw/co
 - For VM power, shutdown, startup, snapshot, or maintenance requests, operate only on the exact VM names provided by the operator.
 - If any requested VM name is missing or not found, stop immediately and report the missing names; do not infer, substitute, or search for replacement VMs unless the operator explicitly requests a discovery/mapping step.
 - For `atvm_prep` requests, infer common option values from operator shorthand when intent is clear.
+- For any `atvm_prep` execution request, always present the exact planned `atvm_prep.py` command first and wait for explicit operator approval before running it.
 - `atvm_prep` datastore shorthand mapping for `-n`:
   - `Gold` -> `AutomatedTest-VMBootImg-Gold`
   - `Gold2` -> `AutomatedTest-VMBootImg-Gold-2`

atvm/docs/automation/atvm-prep-reference.md

@@ -56,6 +56,9 @@ For requests in this workspace, operator shorthand may be expanded as follows:
 - If only one side of the pair is supplied (`-c` or `-e`), auto-fill the other side from this mapping.
 - If both are supplied but conflict, stop and confirm before execution.
 
+4. Approval rule
+- Always show the exact planned `atvm_prep.py` command and wait for explicit operator approval before execution.
+
 ## Operational Flow
 High-level behavior across modes: