Add manual Storm Report generation

docs/cli.md

@@ -2,11 +2,10 @@
 
 `weatherreporter generate daily`, `weatherreporter generate tomorrow`,
 `weatherreporter generate three-day`, `weatherreporter generate weekend`,
+`weatherreporter generate storm`,
 `weatherreporter run morning`, and `weatherreporter run evening` currently
 write Markdown reports through `scriptorium`, after writing managed preparation
-artifacts and running `scriptorium render` as a preflight check. Unsupported
-report generation still resolves configuration, report definitions, and valid
-periods, then returns a not-implemented error.
+artifacts and running `scriptorium render` as a preflight check.
 
 ## Shortest Useful Command
 
@@ -35,6 +34,12 @@ weatherreporter generate three-day --out ./three-day.md
 weatherreporter generate weekend --out ./weekend.md
 ```
 
+For a focused manual Storm Report:
+
+```sh
+weatherreporter generate storm --start 2026-05-29T18:00 --end 2026-05-30T06:00 --out ./storm.md
+```
+
 ## Command Overview
 
 ```text
@@ -47,15 +52,16 @@ weatherreporter run morning
 weatherreporter run evening
 ```
 
-`generate daily`, `generate tomorrow`, `generate three-day`, and
-`generate weekend` write a briefing snapshot, prompt input data package, render
-preflight output, Markdown report, and metadata file under the configured
-workspace. `run evening` generates the Tomorrow Planning Brief. `run morning`
-generates Daily Today and the 3-Day Outlook, plus Weekend Outlook except on
-Sunday. Run commands continue remaining reports after an independent report
-failure, print a JSON aggregate summary to stdout, write compact report status
-logs to stderr, and return nonzero when any report failed. Other `generate`
-commands resolve one report request and stop before report generation.
+`generate daily`, `generate tomorrow`, `generate three-day`,
+`generate weekend`, and `generate storm` write a briefing snapshot, prompt
+input data package, render preflight output, Markdown report, and metadata file
+under the configured workspace. `generate storm` requires explicit `--start`
+and `--end` bounds for the event window. `run evening` generates the Tomorrow
+Planning Brief. `run morning` generates Daily Today and the 3-Day Outlook, plus
+Weekend Outlook except on Sunday. Run commands continue remaining reports after
+an independent report failure, print a JSON aggregate summary to stdout, write
+compact report status logs to stderr, and return nonzero when any report
+failed.
 
 ## Flags
 
@@ -63,7 +69,7 @@ commands resolve one report request and stop before report generation.
 - `--config PATH`: load configuration from `PATH` instead of `/usr/local/etc/weatherreporter/config.yml`.
 - `--units VALUE`: override configured Weather API units.
 - `--tz NAME`: override configured Weather API timezone.
-- `--out PATH`: optional Markdown report copy for `generate daily`, `generate tomorrow`, `generate three-day`, and `generate weekend`; reserved for later generated report output on other `generate` commands.
+- `--out PATH`: optional Markdown report copy for `generate daily`, `generate tomorrow`, `generate three-day`, `generate weekend`, and `generate storm`.
 - `--out-dir PATH`: optional directory for extra Markdown report copies from `run morning` and `run evening`.
 - `--date YYYY-MM-DD`: optional date for `generate daily`; defaults to the current local date in the configured timezone.
 - `--start TIME`: required start time for `generate storm`.

docs/internal/briefing.md

@@ -6,7 +6,8 @@ This document describes the implemented briefing package boundary.
 
 `internal/briefing` builds structured report-specific briefing packages from
 forecast summaries and report metadata. The package currently implements Daily
-Today, Daily Tomorrow, 3-Day Outlook, and Weekend Outlook briefing content.
+Today, Daily Tomorrow, 3-Day Outlook, Weekend Outlook, and Storm Report
+briefing content.
 
 ## Inputs and Outputs
 
@@ -45,6 +46,11 @@ Output:
 - Weekend content uses the same daily outlook summaries and adds planning
   inputs for best outdoor windows, worst weather windows, rain/storm timing,
   comfort concerns, and confidence or uncertainty context.
+- Storm content uses the explicit event window and includes event headline
+  inputs, hazards, most-likely scenario inputs, reasonable worst-case inputs,
+  confidence and uncertainty inputs, watch items, active alerts, relevant
+  hourly and narrative forecast periods, and available discussion or weather
+  story context.
 - Briefing JSON is written atomically by `briefing.Save`.
 
 ## Failure Behavior
@@ -55,6 +61,8 @@ Output:
   one derived daily summary in the outlook period.
 - Weekend briefing construction requires a Weekend report definition and at
   least one derived daily summary in the weekend period.
+- Storm briefing construction requires a Storm Report definition and a forecast
+  bundle.
 - Save failures include path and operation context.
 
 ## Tests
@@ -64,6 +72,7 @@ Inspect:
 - `internal/briefing/daily_test.go`
 - `internal/briefing/three_day_test.go`
 - `internal/briefing/weekend_test.go`
+- `internal/briefing/storm_test.go`
 - `internal/app/app_test.go`
 - `internal/cli/root_test.go`
 

docs/internal/prompt-input.md

@@ -11,8 +11,8 @@ This document describes the implemented prompt input package boundary.
 
 Input:
 
-- `briefing.Package` containing Daily-family, 3-Day Outlook, or Weekend Outlook
-  content
+- `briefing.Package` containing Daily-family, 3-Day Outlook, Weekend Outlook,
+  or Storm Report content
 
 Output:
 

docs/operations.md

@@ -9,6 +9,7 @@ weatherreporter generate daily --date 2026-05-29
 weatherreporter generate tomorrow
 weatherreporter generate three-day
 weatherreporter generate weekend
+weatherreporter generate storm --start 2026-05-29T18:00 --end 2026-05-30T06:00
 weatherreporter run morning
 weatherreporter run evening
 ```
@@ -18,7 +19,8 @@ period, build the prompt input data package, run `scriptorium render`, run
 `scriptorium run`, and write inspectable artifacts under the configured
 workspace. The evening run resolves only the Tomorrow Planning Brief. The
 morning run generates Daily Today and the 3-Day Outlook, plus Weekend Outlook
-except on Sunday.
+except on Sunday. Storm Report generation is manual and uses the explicit
+`--start` and `--end` bounds as its valid period.
 
 Scheduled run commands print a JSON aggregate summary to stdout and compact
 per-report status lines to stderr. If one report fails, remaining independent
@@ -44,6 +46,10 @@ workspace/
       YYYY-MM-DD/
         <run_id>.briefing.json
         <run_id>.metadata.json
+    storm/
+      YYYY-MM-DD/
+        <run_id>.briefing.json
+        <run_id>.metadata.json
   data-packages/
     daily/
       YYYY-MM-DD/
@@ -54,6 +60,9 @@ workspace/
     weekend/
       YYYY-MM-DD/
         <run_id>.data_package.json
+    storm/
+      YYYY-MM-DD/
+        <run_id>.data_package.json
   preflight/
     daily/
       YYYY-MM-DD/
@@ -64,6 +73,9 @@ workspace/
     weekend/
       YYYY-MM-DD/
         <run_id>.render.json
+    storm/
+      YYYY-MM-DD/
+        <run_id>.render.json
   reports/
     daily/
       <run_id>.md
@@ -71,11 +83,14 @@ workspace/
       <run_id>.md
     weekend/
       <run_id>.md
+    storm/
+      <run_id>.md
 ```
 
 The Markdown report is written to a RunID-managed report path. When `--out` is
-provided to `generate daily`, `generate tomorrow`, `generate three-day`, or
-`generate weekend`, the managed report is also copied to that path.
+provided to `generate daily`, `generate tomorrow`, `generate three-day`,
+`generate weekend`, or `generate storm`, the managed report is also copied to
+that path.
 
 For `run morning` and `run evening`, `--out-dir PATH` writes extra Markdown
 copies using each report definition's default filename, such as `daily.md`,
@@ -123,6 +138,9 @@ Weekend Outlook generation compares against a prior compatible Weekend briefing
 snapshot for the same weekend window when one exists. Friday evening and
 Saturday runs may narrow the valid start while keeping the same Monday endpoint.
 
+Storm Report generation currently leaves Recent Changes empty. Its explicit
+event window is still recorded in briefing and metadata artifacts.
+
 When no prior comparable snapshot exists, or no configured threshold is crossed,
 the Recent Changes list is empty.