Add daily planning module

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`.