Notify hourly generated reports after success

docs/operations.md

@@ -31,7 +31,10 @@ the effective report timezone and is not part of scheduled morning or evening
 batches. It builds the same module snapshot and data package, runs
 `scriptorium render` as preflight, runs structured `scriptorium run` to raw
 GeneratedText JSON, validates the structured text, saves a render context, and
-renders the managed Markdown report from the embedded hourly template.
+renders the managed Markdown report from the embedded hourly template. When
+distributor notification is enabled, hourly uploads the managed Markdown report
+after final metadata is saved. `--out PATH` writes an extra Markdown copy and
+is not used as the distributor upload source.
 
 Batch commands:
 
@@ -193,11 +196,10 @@ report generation has a distinct retry identity. The default bundle path uses
 the valid-period start date, artifact group, and RunID. Distributor owns
 destination merge, retention, and derived snapshot behavior such as `latest`.
 
-Notification happens after final metadata save for Markdown-path generation.
-Weather API, module snapshot, data-package, render preflight, Scriptorium run,
-and metadata-save failures do not trigger notification. Hourly generated-text
-reports write the managed Markdown report and generated-text artifacts but do
-not notify distributor yet. A notification failure fails that report.
+Notification happens after final metadata save for generated reports. Weather
+API, module snapshot, data-package, render preflight, Scriptorium run,
+generated-text validation, template rendering, and metadata-save failures do
+not trigger notification. A notification failure fails that report.
 In a batch, other reports continue, the failed report includes notification
 fields in the JSON summary, and the batch returns nonzero.