Add daily planning module

docs/internal/briefing.md

@@ -33,7 +33,8 @@ Outputs:
   `weather_story`
 - `module.Output` values for derived stanzas:
   `derived_daily_summary`, `derived_daypart_summaries`, `precip_timing`,
-  `outdoor_windows`, `today_planning`, and `tomorrow_planning`
+  `outdoor_windows`, `today_planning`, `tomorrow_planning`, and
+  `daily_planning`
 
 Every registered composition entry has a builder. Unknown or unimplemented
 module IDs fail validation instead of being skipped.
@@ -50,13 +51,18 @@ package and embedded Markdown template.
 morning readiness, commute/school/workday concerns, outdoor planning, and
 late-day change-watch fields. It is compatible with `report.Today` only.
 
+`daily_planning` is a dated Daily deterministic planning stanza with morning
+readiness, commute/school/workday concerns, and overnight change-watch fields.
+It is compatible only with the `daily` report ID value. No active default
+report composition includes it yet.
+
 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`,
-`today_planning`, or `tomorrow_planning`.
+`today_planning`, `tomorrow_planning`, or `daily_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

@@ -44,6 +44,7 @@ The registry recognizes these IDs:
 - `outdoor_windows`
 - `today_planning`
 - `tomorrow_planning`
+- `daily_planning`
 
 Every registered module has a builder. Report composition entries that refer to
 unknown or unimplemented module IDs fail validation instead of being skipped.
@@ -92,6 +93,22 @@ The default Tomorrow Report module order is:
 The embedded Tomorrow template uses selected deterministic fields from these
 module outputs after GeneratedText validation.
 
+## Daily Planning
+
+`daily_planning` emits dated daily planning facts for the `daily` report ID.
+Its output stanza is also named `daily_planning`. The module is supported only
+by that report ID and depends on daily summaries for the selected local civil
+day. No active default report composition includes it yet.
+
+The output uses this shape:
+
+- `morning_readiness`
+- `commute_school_workday_concerns`
+- `overnight_change_watch`
+
+The type is `briefing.DailyPlanningModule`; it is independent from
+`briefing.TomorrowPlanningModule`.
+
 ## Today Planning
 
 `today_planning` emits current-day planning facts for Today Report. Its output
@@ -99,13 +116,12 @@ stanza is also named `today_planning`. The module is supported only by Today
 Report and depends on daily and daypart summaries for the current local civil
 day.
 
-The output uses the same shape as Tomorrow planning:
+The output uses this shape:
 
 - `morning_readiness`
-- `commute`
+- `commute_school_workday_concerns`
 - `outdoor_planning`
-- `things_to_watch`
-- `confidence`
+- `late_day_change_watch`
 
 The type is `briefing.TodayPlanningModule`; it is independent from
 `briefing.TomorrowPlanningModule`.