Report distributor notification outcomes in batches

docs/cli.md

@@ -40,7 +40,9 @@ explicit event-window bounds with `--start` and `--end`.
 except on Sunday. `run evening` generates the Tomorrow Planning Brief. Batch
 runs continue independent reports after a failure, print a JSON summary to
 stdout, write compact status lines to stderr, and return nonzero when any report
-failed.
+failed. When notification is configured, batch summaries and status lines include
+notification status, accepted distributor run ID, or notification error fields
+for each attempted report.
 
 `inspect` commands read existing workspace artifacts and emit JSON to stdout.
 They do not fetch weather data or invoke `scriptorium`.

docs/operations.md

@@ -32,9 +32,11 @@ weatherreporter run evening
 except on Sunday. `run evening` generates the Tomorrow Planning Brief. Batch
 commands print a JSON summary to stdout, write compact per-report status lines
 to stderr, continue independent reports after one report fails, and return
-nonzero when any report failed. `--out-dir PATH` writes extra Markdown copies
-using report default filenames such as `daily.md`, `three-day.md`,
-`weekend.md`, and `tomorrow.md`.
+nonzero when any report failed. When notification is configured, the summary and
+status lines include notification status, accepted distributor run ID, or
+notification error fields for each attempted report. `--out-dir PATH` writes
+extra Markdown copies using report default filenames such as `daily.md`,
+`three-day.md`, `weekend.md`, and `tomorrow.md`.
 
 ## Filesystem Layout
 
@@ -117,8 +119,9 @@ Each generated report writes metadata that links:
 - preflight output path
 - managed Markdown report path
 
-Batch summaries include report status, error text when applicable, valid
-period, and known artifact paths for each attempted report.
+Batch summaries include report status, error text when applicable, notification
+outcome when attempted, valid period, and known artifact paths for each
+attempted report.
 
 ## Inspection