- add the per-run ATVM watcher service package under atvm/watcher-service, including the Python watcher, systemd template unit, helper scripts, and deployment docs - document the watcher-service install and operating model, including one-run-per-instance behavior, Mattermost posting rules, and the best-practice /opt/atvm-watcher-service install path - clarify ATVM run approval semantics so `approve` means run without watcher and `approve with watcher` means run and start the watcher - update the ATVM automation guide and AGENTS rules so watcher usage and approval behavior are explicit and consistent
ATVM Workspace
This folder contains the ATVM setup workflow, ATVM Cypress automation workflow, and the lab inventory/reference material used to operate them.
Start Here
- Setup/bootstrap workflow:
docs/setup/guide.md
- ATVM Cypress automation workflow:
docs/automation/guide.md
- Shared maintenance conventions:
docs/workflow/conventions.md
- Environment inventory and credentials:
inventory/overview.md
Layout
scripts/- executable scripts used by setup/bootstrap
docs/setup/- setup procedure and setup run learnings
docs/automation/- automation procedure, reusable examples, and automation run learnings
docs/workflow/- conventions for how this workspace is structured and maintained
inventory/- environment inventory, credentials, reserved IPs, and reference maps
archive/imported-notes/- preserved original long-form notes that were reorganized into the current structure
Practical Guidance
- Use
guide.mdfiles for authoritative workflow behavior. - Use
examples.mdfor reusable command patterns only. - Use
run-learnings.mdonly when a run produced a new lasting lesson. - For detailed ATVM automation test results, especially per-host failures, use
/root/cdc-e2e-cyp-12.17.4/cypress/cmcReporteron the automation controller. - Use
inventory/for persistent environment information such as hosts, credentials, and IP assignments. - Use
archive/imported-notes/when you need the original full historical notes in their original layout.