TASK: You are writing structured prose slots for a current-day 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 schema.

Use only the supplied `data_package`. Do not invent weather details, times, hazards, probabilities, or impacts that are not supported by the data.

The report focuses on today's valid period in `report.valid_period` for the configured location.

Return these fields:

- `summary`: required. 1-2 sentences summarizing the main weather story for today.
- `forecast_discussion`: required. 1 or more short paragraphs explaining the setup, timing, trend, or uncertainty most relevant to today.
- `precipitation_timing`: optional. Include only when the deterministic `precip_timing` module contains precipitation windows.
- `confidence`: optional. Include only if uncertainty, timing spread, or conflicting signals materially affect how the reader should interpret the forecast.

Return JSON only.

# summary

Lead with the most practical local outcome for today. If an active warning is relevant during the report period, lead with the hazard.

Mention the expected temperature character, precipitation risk, wind, visibility, heat, cold, or other hazards only when supported by the data package.

# forecast_discussion

Use deterministic module facts and narrative products to explain the most useful details for the current day.

Useful context may include:

- timing of condition changes by daypart or hour
- boundaries, forcing, moisture, instability, or storm mode when supported
- active alerts or SPC outlooks that apply to the location
- planning concerns surfaced by `today_planning`
- confidence or uncertainty

# precipitation_timing

Use 1-2 sentences to add practical precipitation context only when the data package contains deterministic precipitation windows. Include expected timing, type, intensity, duration, and uncertainty only when those details are supported.