Document Today report workflow

docs/operations.md

@@ -10,6 +10,7 @@ Generation commands:
 
 ```text
 weatherreporter generate daily --date 2026-05-29
+weatherreporter generate today
 weatherreporter generate tomorrow
 weatherreporter generate hourly
 weatherreporter generate three-day
@@ -23,12 +24,16 @@ a JSON module snapshot, build a YAML prompt input data package, run
 workspace. Markdown-path reports then run `scriptorium run` directly to the
 managed Markdown report path.
 
-`generate tomorrow` and `generate hourly` use the generated-text-template
-workflow. They run structured `scriptorium run` to raw GeneratedText JSON,
-validate the structured text, save a render context, and render the managed
-Markdown report from embedded templates. `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.
+`generate today`, `generate tomorrow`, and `generate hourly` use the
+generated-text-template workflow. They run structured `scriptorium run` to raw
+GeneratedText JSON, validate the structured text, save a render context, and
+render the managed Markdown report from embedded templates. `generate today`
+covers the selected or current local civil day. `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.
+
+`generate daily` remains the existing Daily Today report and is independent of
+`generate today`.
 
 When distributor notification is enabled, weatherreporter uploads the managed
 Markdown report after report rendering succeeds and final metadata is saved.
@@ -42,14 +47,14 @@ weatherreporter run morning
 weatherreporter run evening
 ```
 
-`run morning` generates Daily Today and the 3-Day Outlook, plus Weekend Outlook
+`run morning` generates Today Report and the 3-Day Outlook, plus Weekend Outlook
 except on Sunday. `run evening` generates the Tomorrow Report. 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. 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`,
+extra Markdown copies using report default filenames such as `today.md`,
 `three-day.md`, `weekend.md`, and `tomorrow.md`; these copies are not used as
 distributor upload sources.
 
@@ -64,6 +69,14 @@ workspace/
       YYYY-MM-DD/
         <run_id>.modules.json
         <run_id>.metadata.json
+    today/
+      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
     three-day/
       YYYY-MM-DD/
         <run_id>.modules.json
@@ -96,6 +109,9 @@ workspace/
     daily/
       YYYY-MM-DD/
         <run_id>.data_package.yaml
+    today/
+      YYYY-MM-DD/
+        <run_id>.data_package.yaml
     three-day/
       YYYY-MM-DD/
         <run_id>.data_package.yaml
@@ -115,6 +131,9 @@ workspace/
     daily/
       YYYY-MM-DD/
         <run_id>.render.json
+    today/
+      YYYY-MM-DD/
+        <run_id>.render.json
     three-day/
       YYYY-MM-DD/
         <run_id>.render.json
@@ -134,6 +153,9 @@ workspace/
     daily/
       YYYY-MM-DD/
         <run_id>.distributor.json
+    today/
+      YYYY-MM-DD/
+        <run_id>.distributor.json
     three-day/
       YYYY-MM-DD/
         <run_id>.distributor.json
@@ -152,6 +174,8 @@ workspace/
   reports/
     daily/
       <run_id>.md
+    today/
+      <run_id>.md
     three-day/
       <run_id>.md
     weekend/
@@ -173,6 +197,7 @@ RunIDs are based on generation time plus report ID:
 
 ```text
 20260529T100000.123456789Z_daily_today
+20260529T100000.123456789Z_today
 ```
 
 Each generated report writes metadata that links:
@@ -214,6 +239,8 @@ The default idempotency key appends RunID to the rendered bundle ID so each
 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`.
+For Today, the default report ID and artifact group values are both `today`,
+and the batch output filename value is `today.md`.
 
 Notification happens after final metadata save for generated reports. Weather
 API, module snapshot, data-package, render preflight, Scriptorium run,
@@ -267,11 +294,12 @@ Recent Changes are computed from structured module snapshots, not rendered
 Markdown or YAML text.
 
 Daily Today compares with prior Daily Today snapshots for the same valid local
-date. Tomorrow Report compares with prior Tomorrow Report snapshots for the
-same valid local date. 3-Day Outlook compares with prior compatible 3-Day
-snapshots for the same valid local date. Weekend Outlook compares with prior
-compatible Weekend snapshots for the same weekend window. Hourly Report and
-Storm Report leave Recent Changes empty.
+date. Today Report compares with prior Today Report snapshots for the same
+valid local date. Tomorrow Report compares with prior Tomorrow Report snapshots
+for the same valid local date. 3-Day Outlook compares with prior compatible
+3-Day snapshots for the same valid local date. Weekend Outlook compares with
+prior compatible Weekend snapshots for the same weekend window. Hourly Report
+and Storm Report leave Recent Changes empty.
 
 When no prior comparable snapshot exists, or no configured threshold is crossed,
 `recentChanges.items` is empty.
@@ -284,10 +312,10 @@ A failed generation run may still leave useful artifacts:
   preflight JSON and metadata are written for inspection.
 - If `scriptorium run` exits nonzero after writing a report, the managed report
   and metadata remain available.
-- Hourly generated-text failures preserve available intermediate artifacts,
-  such as the structured run result, raw generated-text JSON, validated
-  generated text, and render context. Metadata links those paths when it can be
-  safely written.
+- Generated-text failures for Today, Tomorrow, and Hourly reports preserve
+  available intermediate artifacts, such as the structured run result, raw
+  generated-text JSON, validated generated text, and render context. Metadata
+  links those paths when it can be safely written.
 - If distributor notification fails, report artifacts and final metadata remain
   available, but the report or batch command returns nonzero.
 - For batch commands, inspect the stdout JSON summary first, then inspect the