Require approval before ATVM command execution

Update the ATVM automation guidance so exact planned commands must always be shown for operator review before any execution. Require explicit approval before running cmc-templates.py, run-sorry-cypress.py, or any other ATVM run command, and require fresh approval whenever the displayed command set changes. Also record the new approval rule in the ATVM run-learning notes and operator instruction file.

atvm/atvm-automation-guide.md

@@ -29,7 +29,10 @@ Run ATVM CMC automation tests on the designated automation VM without unintended
 - Always report whether automation is currently running.
 - If running, ask whether to terminate; terminate only with explicit approval.
 - After termination approval, terminate first, then present planned command(s), then wait for separate execution approval.
-- Before any run, always show exact planned command(s) and wait for explicit approval.
+- Before any run, always show exact planned command(s) exactly as they will be executed and wait for explicit approval.
+- Never execute `cmc-templates.py`, `run-sorry-cypress.py`, or any other ATVM run command until the operator explicitly approves the displayed command(s).
+- Approval is required even for preparation-only steps such as template generation.
+- If the operator changes any part of the request after commands are displayed, rebuild the commands, show the updated commands, and wait for fresh approval before executing anything.
 - Execute only after explicit approval (for example `approve`).
 - After execution, report immediate success/failure only.
 - Do not actively monitor completion unless explicitly requested.
@@ -42,9 +45,12 @@ Run ATVM CMC automation tests on the designated automation VM without unintended
 - Test execution: `./run-sorry-cypress.py`
 
 Typical sequence:
-1. Run `cmc-templates.py` with requested template/options.
-2. Wait for `cmc-templates.py` to fully finish and confirm success.
-3. Run `run-sorry-cypress.py` with matching config and build name.
+1. Build the exact `cmc-templates.py` and `run-sorry-cypress.py` commands for the request.
+2. Show those exact commands to the operator.
+3. Wait for explicit approval.
+4. Run `cmc-templates.py` with the approved options.
+5. Wait for `cmc-templates.py` to fully finish and confirm success.
+6. Run `run-sorry-cypress.py` with the matching approved config and build name.
 
 ## Config File / Gold Disk Mapping
 - `cypress.atvm-config-gold.ts` -> Gold Disk 1
@@ -121,13 +127,15 @@ Before any new automation request:
 
 ## Approval Workflow (Mandatory)
 1. Build exact command(s) for the request.
-2. Present them verbatim as planned commands.
+2. Present them verbatim as planned commands before running anything.
 3. Wait for explicit approval.
-4. Run only approved command(s), no extra options.
+4. Run only approved command(s), no extra options and no silent substitutions.
 5. When both template generation and the Cypress runner are requested, run them sequentially, not in parallel.
 6. Do not launch `run-sorry-cypress.py` until `cmc-templates.py` has exited successfully and finished updating the intended config/spec files.
-7. If monitoring was not requested, report immediate success/failure for each command.
-8. If monitoring was requested, keep monitoring until completion and report final outcome.
+7. Treat displayed commands as a review gate: do not execute either command until the operator has had a chance to review them and explicitly approve.
+8. If the operator asks to change plugin, config, filters, build name, Gold Disk, or scope after commands are shown, discard the old plan, show the revised commands, and wait for new approval.
+9. If monitoring was not requested, report immediate success/failure for each command.
+10. If monitoring was requested, keep monitoring until completion and report final outcome.
 
 ## Requested Test Style
 When asked for one VM or a VM set: