Trim internal fallback details from ATVM notes

atvm/docs/automation/guide.md

@@ -239,6 +239,7 @@ Status-report expectations:
 - Order the status sections as `SUMMARY:`, `HOSTS:`, `TIMING:`, `COVERAGE:`, `TEST FLOW:`, then `NOTES:`.
 - Keep `NOTES:` focused on operator-facing value such as the Currents run URL, real anomalies, failure context, or material fallback behavior.
 - Do not include generic watcher bookkeeping messages in `NOTES:` such as artifact-detection confirmations.
+- Do not include internal watcher fallback notes in `NOTES:` such as `check-xml-files.ts` validation confirmations or reporter-artifact recovery details.
 - The `HOSTS:` table includes `Host`, `Kernel`, `Status`, and `Detail` columns in that order.
 - In `COVERAGE:`, describe the template, datastore/config family, migration style, and plugin/integration path, but do not list target hosts there.
 - In `TEST FLOW:`, show the template-specific numbered run flow once for the whole test, not per host.

atvm/docs/automation/run-learnings.md

@@ -274,6 +274,7 @@ This file stores run-specific examples only when a run produced a new learning r
 - Action for future runs:
   - Reserve `NOTES:` for meaningful operator-facing content such as the Currents run URL, real anomalies, failure context, and important fallback behavior.
   - Do not include generic artifact-detection confirmations in the posted `NOTES:` section.
+  - Do not include internal fallback notes such as "`check-xml-files.ts` validation passed" or "host details were derived from reporter artifacts" in the posted `NOTES:` section.
 
 ## Run Learning: 2026-03-27 (Categorized grouped XML may need host recovery from the subrun's per-host artifact)
 - Observed failure mode:

atvm/docs/automation/status-template.md

@@ -74,6 +74,7 @@ Use this as the default ATVM automation run-status template for:
 - When available, put the persistent Currents run URL in `NOTES:` so operators can open the exact recorded run directly.
 - Keep `NOTES:` limited to meaningful operator-facing items such as the Currents link, real anomalies, failure context, or important fallback behavior.
 - 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.
 - `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.