Implement support for NWS weather stories

docs/integrations/weatherapi.md

@@ -53,7 +53,8 @@ The adapter sends these query parameters:
 - `tz`: from `weather_api.timezone` on hourly forecast, narrative forecast, and
   discussion requests
 
-Alerts do not receive `precision` or `tz`.
+Alerts do not receive `precision` or `tz`. Weather story requests receive only
+`format=json`.
 
 ## Endpoints Used
 
@@ -65,6 +66,7 @@ The adapter fetches these endpoints once per bundle:
 - `/forecast/narrative`
 - `/alerts/active`
 - `/discussion`
+- `/weatherstories/latest`
 
 `weatherreporter` does not call day-slice forecast endpoints or discussion
 subsection endpoints. Report-period selection and daypart summarization happen
@@ -86,10 +88,11 @@ source-specific `missing_source.sources` policy:
 - `narrative` for `/forecast/narrative`
 - `alerts` for `/alerts/active`
 - `discussion` for `/discussion`
+- `weather_story` for `/weatherstories/latest`
 
-The adapter also creates missing stub source records for `daily` and
-`weather_story` because those source slots exist in the internal bundle but are
-not fetched from the Weather API.
+The adapter also creates a missing stub source record for `daily` because that
+source slot exists in the internal bundle but is not fetched from the Weather
+API.
 
 Policy behavior:
 
@@ -126,6 +129,8 @@ types in `internal/forecast/bundle.go`, including:
 - forecast run metadata and `periods`
 - active alert run data
 - discussion metadata, key messages, and short/long-term section text
+- latest weather story title, description, timing, priority, order, alt text,
+  and download URL
 
 The adapter intentionally keeps upstream transport and envelope details inside
 `internal/adapters/weatherapi`; downstream packages consume the normalized

docs/internal/briefing.md

@@ -24,6 +24,8 @@ Outputs:
   object for Daily, 3-Day, Weekend, or Storm Report
 - optional `currentConditions` prompt context from normalized
   `/conditions/current` data when available
+- optional structured `weatherStory` context on report-specific briefing
+  objects when `/weatherstories/latest` is available
 - optional JSON file written by `briefing.Save`
 
 ## Boundaries

docs/internal/prompt-input.md

@@ -19,8 +19,8 @@ Outputs:
 - `promptinput.Package` containing schema version, RunID, report metadata,
   briefing content, Recent Changes, and source warnings. Briefing content
   includes configured location context, current conditions when available,
-  discussion key messages, and short/long-term AFD narratives when the Weather
-  API provides them.
+  structured weather story context when available, discussion key messages, and
+  short/long-term AFD narratives when the Weather API provides them.
 - report metadata includes `currentLocalDate`, the generation date formatted as
   `YYYY-MM-DD` in the effective report timezone.
 - optional JSON file written by `promptinput.Save`

docs/internal/weather-data.md

@@ -7,7 +7,7 @@ This document describes Weather API ingestion into `forecast.Bundle`.
 `internal/adapters/weatherapi` fetches normalized weather data from one
 configured Weather API endpoint and assembles the bundle consumed by forecast
 derivation and briefing builders. Briefing builders expose normalized current
-conditions as prompt context when `/conditions/current` is available.
+conditions and weather story context when those sources are available.
 
 ## Inputs And Outputs
 
@@ -20,9 +20,9 @@ Inputs:
 Outputs:
 
 - `forecast.Bundle` with observation, current conditions, hourly forecast,
-  narrative forecast, active alerts, discussion, source records, and source
-  warnings
-- stub source records for daily forecast and weather story source slots
+  narrative forecast, active alerts, discussion, latest weather story, source
+  records, and source warnings
+- stub source record for the daily forecast source slot
 - optional saved bundle JSON through app fetch helpers
 
 ## Boundaries

docs/roadmap/future.md

@@ -12,8 +12,7 @@ evaluation remains deferred.
 Proposed direction:
 
 1. detect candidate events deterministically from alerts, forecast discussion,
-   weather story context when available, hourly thresholds, and material
-   forecast changes;
+   weather story context, hourly thresholds, and material forecast changes;
 2. evaluate candidates through Scriptorium or another narrow evaluator adapter;
 3. persist storm lifecycle state;
 4. generate or update Storm Reports only when a meaningful event is present;