Add SPC convective outlook data contracts

docs/internal/facts.md

@@ -20,7 +20,8 @@ Inputs:
 Outputs:
 
 - `facts.CollectedFacts` with normalized source facts plus separate source
-  provenance and warnings
+  provenance and warnings. SPC convective outlook source data is carried
+  through when present in the bundle.
 - `facts.DerivedFacts` with valid-period forecast slices, alert overlaps,
   daily summaries, daypart summaries, and Storm Report window summary
 
@@ -55,6 +56,7 @@ and inspection.
   derivation error for reports that require daily summaries.
 - Missing optional narrative, alert, discussion, daily, or weather story data
   produces empty or nil derived fields.
+- Missing optional SPC convective outlook data produces a nil collected field.
 
 ## Tests
 

docs/internal/module.md

@@ -45,6 +45,10 @@ The registry recognizes these IDs:
 Every registered module has a builder. Report composition entries that refer to
 unknown or unimplemented module IDs fail validation instead of being skipped.
 
+The package also defines `spc_convective_outlooks` and
+`spc_convective_discussion` IDs and empty option structs for the collected
+contract. They are not registered modules in the briefing registry.
+
 ## Options
 
 Most modules use an empty options struct. `area_forecast_discussion` accepts:

docs/internal/weather-data.md

@@ -21,7 +21,8 @@ Outputs:
 
 - `weatherdata.Bundle` with observation, current conditions, hourly forecast,
   narrative forecast, active alerts, discussion, latest weather story, source
-  records, and source warnings
+  records, source warnings, and an optional typed SPC convective outlook field
+  when that source has been populated
 - optional saved bundle JSON through app fetch helpers
 
 ## Boundaries