Update teh schema for the weather hourly report

prompts/pipeline-weather/hourly/hourly_generated_text.user.md

@@ -1,4 +1,4 @@
-You are writing structured text slots for a short-term weather report.
+You are writing structured prose slots for a short-term hourly weather report.
 
 The calling application will render the final Markdown report. Your job is not
 to write the full report. Return only a JSON object matching the configured
@@ -14,27 +14,31 @@ Write for a general local audience. Be clear, practical, and concise.
 
 Return these fields:
 
-- `summary`: 1-2 sentences summarizing the main weather story for the valid
-  period.
-- `timing`: 1-3 sentences explaining when the most important changes or hazards
-  are expected during the valid period.
-- `impacts`: 1-3 sentences explaining practical impacts for people planning
-  travel, outdoor activity, errands, commuting, or similar near-term decisions.
+- `summary`: required. 1-2 sentences summarizing the main weather story for the
+  valid period.
+- `forecast_discussion`: required. 1-3 sentences explaining the broader setup,
+  trend, or forecast reasoning most relevant to the valid period.
+- `precipitation_timing`: optional. Include only when the deterministic
+  `precip_timing` module contains precipitation windows. Use 1-2 sentences to
+  add practical context that is not already stated by the deterministic window
+  bullets.
 - `confidence`: optional. Include only if uncertainty, timing spread, or
   conflicting signals materially affect how the reader should interpret the
   forecast.
 
 Guidance:
 
-- Prefer location-applicable risk products, active alerts, and overlapping SPC
+- Do not repeat deterministic current conditions, alert bullets, hourly forecast
+  bullets, or precipitation-window bullets verbatim.
+- Prefer active alerts, location-applicable risk products, and overlapping SPC
   products for hazard wording.
 - Use the hourly forecast and precipitation timing modules for timing details.
 - Use current conditions only for immediate context; do not let them override
   the forecast.
-- Use AFD key messages and short-term discussion for context, but keep regional
-  or broad discussion tied back to the configured location and valid period.
+- Use AFD key messages and short-term discussion for forecast reasoning, but
+  keep regional or broad discussion tied back to the configured location and
+  valid period.
 - Mention lack of active alerts or risk products only if that is useful context.
-- Do not repeat deterministic tables or lists verbatim.
 - Do not include Markdown headings, bullets, or code fences.
 - Do not include fields outside the schema.
 - If a field cannot be supported by the data, keep it brief and conservative.