Wire hourly generated text rendering

docs/operations.md

@@ -11,24 +11,27 @@ Generation commands:
 ```text
 weatherreporter generate daily --date 2026-05-29
 weatherreporter generate tomorrow
+weatherreporter generate hourly
 weatherreporter generate three-day
 weatherreporter generate weekend
 weatherreporter generate storm --start 2026-05-29T18:00 --end 2026-05-30T06:00
 ```
 
-Each implemented Markdown generation command resolves a report period, fetches
-a Weather API bundle, builds a JSON module snapshot, builds a YAML prompt input
-data package, runs `scriptorium render`, runs `scriptorium run`, and writes
-managed artifacts under the configured workspace.
-When distributor notification is enabled, weatherreporter uploads the managed
-Markdown report after `scriptorium run` succeeds and final metadata is saved.
-`--out PATH` writes an extra Markdown copy for the current generated report; it
-is not used as the distributor upload source.
+Markdown-path generation commands resolve a report period, fetch a Weather API
+bundle, build a JSON module snapshot, build a YAML prompt input data package,
+run `scriptorium render`, run `scriptorium run`, and write managed artifacts
+under the configured workspace. When distributor notification is enabled,
+weatherreporter uploads the managed Markdown report after `scriptorium run`
+succeeds and final metadata is saved. `--out PATH` writes an extra Markdown
+copy for Markdown-path generated reports; it is not used as the distributor
+upload source.
 
-`generate hourly` is an explicit command shell. It covers the six-hour rolling
-period from generation time in the effective report timezone and is not part of
-scheduled morning or evening batches, but its rendering workflow is not
-implemented yet.
+`generate hourly` covers the six-hour rolling period from generation time in
+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.
 
 Batch commands:
 
@@ -71,6 +74,10 @@ workspace/
       YYYY-MM-DD/
         <run_id>.modules.json
         <run_id>.metadata.json
+        <run_id>.generated_text.raw.json
+        <run_id>.generated_text.run.json
+        <run_id>.generated_text.json
+        <run_id>.render_context.json
     storm/
       YYYY-MM-DD/
         <run_id>.modules.json
@@ -156,6 +163,7 @@ Each generated report writes metadata that links:
 - prompt input data package path
 - preflight output path
 - managed Markdown report path
+- generated text schema ID and generated-text artifact paths for Hourly Report
 - distributor notification debug artifact path, when notification is attempted
 
 Batch summaries include report status, error text when applicable, notification
@@ -185,9 +193,11 @@ 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. Weather API, module snapshot,
-data-package, render preflight, Scriptorium run, and metadata-save failures do
-not trigger notification. A notification failure fails that report.
+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.
 In a batch, other reports continue, the failed report includes notification
 fields in the JSON summary, and the batch returns nonzero.