Add SPC convective outlook briefing module

docs/internal/briefing.md

@@ -28,7 +28,8 @@ Outputs:
   supported reports, fact requirements, missing-data behavior, and builder
 - `module.Output` values for source-oriented stanzas:
   `metadata`, `current_conditions`, `narrative_forecast`, `hourly_forecast`,
-  `alert_digest`, `area_forecast_discussion`, and `weather_story`
+  `alert_digest`, `spc_convective_outlooks`,
+  `area_forecast_discussion`, and `weather_story`
 - `module.Output` values for derived stanzas:
   `derived_daily_summary`, `derived_daypart_summaries`, `precip_timing`,
   `outdoor_windows`, and `tomorrow_planning`
@@ -86,6 +87,9 @@ return an error for invalid required inputs.
   forecast discussion, and weather story stanzas.
 - Alert digest output distinguishes checked empty alert data from missing alert
   source data.
+- SPC convective outlook output distinguishes checked empty outlook data from
+  missing outlook source data and omits GeoJSON geometry from prompt-facing
+  fields.
 
 ## Tests
 

docs/internal/module.md

@@ -37,6 +37,7 @@ The registry recognizes these IDs:
 - `derived_daypart_summaries`
 - `precip_timing`
 - `alert_digest`
+- `spc_convective_outlooks`
 - `area_forecast_discussion`
 - `weather_story`
 - `outdoor_windows`
@@ -45,9 +46,9 @@ 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.
+The package also defines the `spc_convective_discussion` ID and empty option
+struct for the collected contract. It is not a registered module in the
+briefing registry until its builder exists.
 
 ## Options