anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make watcher the default ATVM approval path

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 12:24:21 -04:00
parent c60542e0e5
commit 95eeba60cd
3 changed files with 13 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
atvm/docs/automation/guide.md
View File

@@ -41,8 +41,8 @@ Run ATVM CMC automation tests on the designated automation VM without unintended
- 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 ATVM run commands only after explicit approval.
- Treat `approve` as approval to run without the watcher service.
- Treat `approve with watcher` as approval to run and also start the per-run watcher service for that build.
- Treat `approve` as approval to run and also start the per-run watcher service for that build.
- Treat `approve without watcher` as approval to execute the ATVM run without starting the watcher.
- When `--categorize` is used with watcher enabled, treat the watcher as a sequential grouped-run watcher:
- it must post one final Mattermost status per completed categorized group/sub-run
- it must stay active between grouped sub-runs while the parent categorized request is still running
@@ -162,8 +162,8 @@ Before any new automation request:
2. Present them verbatim as planned commands before running anything.
3. Wait for explicit approval.
4. When the watcher is available, present the watcher-start command separately from the core run commands.
5. Treat `approve` as approval to execute the ATVM run without starting the watcher.
6. Treat `approve with watcher` as approval to execute the ATVM run and start the watcher for that build.
5. Treat `approve` as approval to execute the ATVM run and start the watcher for that build.
6. Treat `approve without watcher` as approval to execute the ATVM run without starting the watcher.
7. If the run uses `--categorize` and the watcher is requested, include `--categorize` on the watcher start command too so the watcher tracks sequential categorized sub-runs correctly.
8. Run only approved command(s), no extra options and no silent substitutions.
9. When both template generation and the Cypress runner are requested, run them sequentially, not in parallel.