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

atvm: resolve automation status from local workflow artifacts

Browse Source 
Clarify that ATVM automation status requests refer to the local atvm
folder workflow and the automation VM at 192.168.3.190, not Cirrus
project operations such as the atvm - cypress project.

Update the ATVM guide and AGENTS notes to prefer local evidence in this
order when reporting status:
- active runner processes
- live automation VM files
- shell history for the last launch command
- historical reporter artifacts

Record the new run learning in atvm-automation-runs.md so future status
requests use the correct source of truth.
This commit is contained in:
anthony.wen
2026-03-18 08:22:24 -04:00
parent 8d2e245c6b
commit 51d782d964
3 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
atvm/AGENTS.md
View File

@@ -115,6 +115,7 @@ When the operator asks for run status, report in this order:
Status details:
- Use the same status display format for every ATVM automation status response regardless of template type (`e2e`, `systemOS`, `reboot`, `migrateops`, and others).
- Treat references to the "ATVM automation run" or "automation run" as referring to the local ATVM automation workflow in `/home/aw/code/cds/atvm` and the automation VM at `192.168.3.190`, not to Cirrus project operations with similar names.
- Treat a status request as a request for live status by default.
- Use the live run log on the automation VM when available.
- If no automation is currently running, fall back to the most recent historical run artifacts and logs.