# ATVM Status Template Use this as the default ATVM automation run-status template for: - local status responses in the terminal - Mattermost status posts after a completed run ## Layout ```md ## ATVM Run Status ### **COVERAGE:** - template: `` - datastore/config family: `` - migration style: `` - integration/plugin path: `` - scope of this run: `` **FUNCTIONALLY:** - - - **SUMMARY:** | Metric | Value | |---|---:| | finished | | | passed | | | failed | | | skipped | | **HOSTS:** | Host | Status | Detail | |---|---|---| | | ✅ PASS | completed | | | ⚠️ FAIL | | | | ⏳ RUN | in progress | | | ⏭️ SKIP | | **TIMING:** | Metric | Value | |---|---| | start | | | end | | | total | | | quickest | - or n/a | | longest | - or n/a | | average | or n/a | **NOTES:** - - ``` ## Rules - Keep `COVERAGE:`, `FUNCTIONALLY:`, `SUMMARY:`, `HOSTS:`, `TIMING:`, and `NOTES:` in that order. - Use the title format: - `## ATVM Run Status` - `### ` - Use flat bullet lists for `COVERAGE:` and `FUNCTIONALLY:`. - Use Markdown tables for `SUMMARY:`, `HOSTS:`, and `TIMING:`. - Use one host per row in the `HOSTS:` section. - For completed hosts, prefer: - `✅ PASS` - `⚠️ FAIL` - For in-progress or skipped hosts, use: - `⏳ RUN` - `⏭️ SKIP` - Keep `Detail` concise. - Put broader context under `NOTES:`, not in the host table. - `COVERAGE:` should describe what the run was intended to cover without listing target hosts. - `FUNCTIONALLY:` should describe the intended workflow steps at a high level, even if the run failed before completing them. - Use the same template for Mattermost and local operator-visible status output.