Add a current conditions block to the briefing/data-package

docs/internal/briefing.md

@@ -22,6 +22,8 @@ Outputs:
 
 - `briefing.Package` with common metadata and one report-specific content
   object for Daily, 3-Day, Weekend, or Storm Report
+- optional `currentConditions` prompt context from normalized
+  `/conditions/current` data when available
 - optional JSON file written by `briefing.Save`
 
 ## Boundaries
@@ -36,6 +38,8 @@ The package receives configured units and timezone from the app layer. Daypart
 configuration is consumed by `internal/forecast` before briefing builders run.
 Configured `location` values are prompt context only; Weather API
 `sourceLocationId` and `sourceLocation` remain source provenance.
+Current conditions are copied from the normalized `/conditions/current` bundle
+source only; observation station and timestamp fields remain provenance.
 
 ## External Adapters Used
 

docs/internal/prompt-input.md

@@ -18,8 +18,9 @@ Outputs:
 
 - `promptinput.Package` containing schema version, RunID, report metadata,
   briefing content, Recent Changes, and source warnings. Briefing content
-  includes configured location context, discussion key messages, and
-  short/long-term AFD narratives when the Weather API provides them.
+  includes configured location context, current conditions when available,
+  discussion key messages, and short/long-term AFD narratives when the Weather
+  API provides them.
 - optional JSON file written by `promptinput.Save`
 
 ## Boundaries

docs/internal/weather-data.md

@@ -6,7 +6,8 @@ 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.
+derivation and briefing builders. Briefing builders expose normalized current
+conditions as prompt context when `/conditions/current` is available.
 
 ## Inputs And Outputs