Complete stateless execution remediation

docs/operations.md

@@ -40,8 +40,12 @@ Without `--out-dir`, batch reports are written beneath the current directory.
 Morning runs Today, Tomorrow, and every eligible dated Daily Report; evening
 runs Tomorrow and the same eligible Daily Reports. Eligible Daily dates begin
 after tomorrow and require complete hourly coverage for their local civil day.
-A batch collects once, processes each selected report independently, and keeps
-successful outputs if another report fails.
+A batch collects once, determines the complete report set, and validates every
+final output destination before executing its first report prompt. A destination
+collision, such as a directory named `tomorrow.md`, stops the batch before any
+report output is created or replaced. After successful validation, each selected
+report processes independently and successful outputs remain available if
+another report fails.
 
 When `notify.distributor.enabled` and batch notification are enabled,
 Weatherreporter sends one Distributor upload only after every selected output
@@ -50,6 +54,9 @@ files remain at their selected destinations. A batch notification failure also
 leaves all successfully published report files in place. Distributor source
 files are those operator-owned Markdown outputs; rendered bundle paths and
 delivery status appear in the result, not in a local notification receipt.
+Report counters count report items only. A batch notification failure therefore
+returns a failed batch status even when all report counters show success; the
+top-level notification result contains the delivery diagnostic.
 
 For a single report, Distributor notification follows the atomic output write.
 See the [configuration reference](config.md) for pipeline, bundle,