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.
Document ATVM automation defaults to always include --ignore_force_shutdown on cmc-templates.py commands and to use --use_specified_plugin iscsi unless explicitly overridden.
Update the ATVM automation guide, folder-level AGENTS instructions, and run learnings so future runs follow the same defaults.
Clarify ATVM automation status handling so status requests default to live run data from the automation VM. If no automation is active, fall back to the most recent historical run artifacts and logs.
Also document that categorized runs must always be reconstructed as a single full run across all category batches or cloud sub-runs, rather than reporting only the current or latest batch.
Update:
- atvm/atvm-automation-guide.md
- atvm/AGENTS.md
- atvm/atvm-automation-runs.md
Update git-guide.md to document the repository URL used for this workspace as the current origin.
Require showing the exact git commit command alongside proposed commit messages.
Wait for explicit approval before creating a commit.
Document the repo-specific git workflow for /home/aw/code/cds. Require drafting commit messages for user review before running git commit, and keep commits scoped to the approved change.
Record the operator preference to stop immediately when a requested ATVM config file is missing. Update the ATVM guide, local agent instructions, and run learnings to avoid searching for or substituting alternate config files without explicit direction.
- show failed machines with a longer failure description on the same status line
- keep Notes for broader context beyond the machine-specific failure reason
- update the ATVM automation guide and AGENTS rules to match
- record the reporting preference in atvm-automation-runs.md
- keep atvm-automation-examples.md limited to reusable example commands
- move example-file role guidance into AGENTS.md and atvm-automation-guide.md
- document that all ATVM automation run types use the same status display format
- record the status-format rule as a run learning in atvm-automation-runs.md
- Treat atvm-automation-examples.md as reference material rather than default operator intent.
- Use only explicitly requested options, plus maintained mandatory blacklist handling.
- Record the rule as a run learning in atvm-automation-runs.md.
Stop defaulting to cypress.atvm-config.ts in ATVM guidance.
Prefer gold-named config files unless explicitly told otherwise.
Update automation examples to use cypress.atvm-config-gold.ts.
Record the run learning explaining why the old default is unreliable.
Add atvm144-suse15.0 to the ATVM automation blacklist because it crashes when creating a migration session.
Update maintained exclude examples to include the new blacklist entry.
Tighten status reporting guidance to require one machine per line.
Add a Notes section for failure reasons and operator-facing context.
Record the new run learnings in atvm-automation-runs.md.
