Add Today planning module scaffold

docs/internal/briefing.md

@@ -33,7 +33,7 @@ Outputs:
   `weather_story`
 - `module.Output` values for derived stanzas:
   `derived_daily_summary`, `derived_daypart_summaries`, `precip_timing`,
-  `outdoor_windows`, and `tomorrow_planning`
+  `outdoor_windows`, `today_planning`, and `tomorrow_planning`
 
 Every registered composition entry has a builder. Unknown or unimplemented
 module IDs fail validation instead of being skipped.
@@ -42,13 +42,17 @@ Tomorrow Report supports the Daily-style civil-day modules plus
 `tomorrow_planning` and `hourly_forecast`; those outputs feed the Tomorrow
 GeneratedText prompt package and embedded Markdown template.
 
+`today_planning` is a Today-specific deterministic planning stanza with
+morning readiness, commute/school/workday concerns, outdoor planning, and
+late-day change-watch fields. It is compatible with `report.Today` only.
+
 Hourly Report supports source and valid-period modules that operate over its
 rolling six-hour period: `metadata`, `current_conditions`, `hourly_forecast`,
 `precip_timing`, `alert_digest`, `spc_convective_outlooks`,
 `area_forecast_discussion`, `spc_convective_discussion`, and `weather_story`.
 It does not support daily/daypart-only modules such as
-`derived_daily_summary`, `derived_daypart_summaries`, `outdoor_windows`, or
-`tomorrow_planning`.
+`derived_daily_summary`, `derived_daypart_summaries`, `outdoor_windows`,
+`today_planning`, or `tomorrow_planning`.
 
 Prompt-facing module values use local, human-readable date and time labels
 where the LLM is expected to reason about report content. Canonical timestamps

docs/internal/module.md

@@ -42,6 +42,7 @@ The registry recognizes these IDs:
 - `spc_convective_discussion`
 - `weather_story`
 - `outdoor_windows`
+- `today_planning`
 - `tomorrow_planning`
 
 Every registered module has a builder. Report composition entries that refer to