Expand ATVM coverage details with run options

atvm/docs/automation/status-template.md

@@ -42,8 +42,10 @@ Use this as the default ATVM automation run-status template for:
 **COVERAGE:**
 - template: `<template-name>`
 - datastore/config family: `<config family>`
+- config file: `<config-file-name>`
 - migration style: `<high-level test style>`
 - integration/plugin path: `<integration/plugin>`
+- run options: `<operator-relevant options such as --ignore_force_shutdown>`
 - scope of this run: `<batch or run scope>`
 
 **TEST FLOW:**
@@ -76,6 +78,7 @@ Use this as the default ATVM automation run-status template for:
 - Do not include generic watcher bookkeeping lines in `NOTES:` such as "run artifacts were detected" or "final reporting artifacts were detected."
 - Do not include internal fallback notes in `NOTES:` such as "`check-xml-files.ts` validation passed" or "host details were derived from reporter artifacts."
 - `COVERAGE:` should describe what the run was intended to cover without listing target hosts.
+- `COVERAGE:` should also include operator-relevant run options such as the config filename and important flags like `--ignore_force_shutdown`.
 - `TEST FLOW:` should describe the template-specific numbered run flow once for the whole test, not per host.
 - The watcher resolves `TEST FLOW:` from the run template name.
 - `cmc-e2e` currently uses this flow: