Replace legacy daily report with generated text daily report

docs/internal/briefing.md

@@ -39,6 +39,10 @@ Outputs:
 Every registered composition entry has a builder. Unknown or unimplemented
 module IDs fail validation instead of being skipped.
 
+Daily Report supports the Daily-style civil-day modules plus `daily_planning`
+and `hourly_forecast`; those outputs feed the dated Daily GeneratedText prompt
+package and embedded Markdown template.
+
 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.
@@ -53,8 +57,8 @@ 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.
+It is compatible only with the `daily` report ID value. The default Daily
+Report composition includes it.
 
 Hourly Report supports source and valid-period modules that operate over its
 rolling six-hour period: `metadata`, `current_conditions`, `hourly_forecast`,

docs/internal/module.md

@@ -49,6 +49,28 @@ 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.
 
+## Daily Composition
+
+The default Daily Report module order is:
+
+1. `metadata`
+2. `current_conditions`
+3. `narrative_forecast`
+4. `derived_daily_summary`
+5. `derived_daypart_summaries`
+6. `precip_timing`
+7. `alert_digest`
+8. `spc_convective_outlooks`
+9. `area_forecast_discussion`
+10. `spc_convective_discussion`
+11. `weather_story`
+12. `outdoor_windows`
+13. `daily_planning`
+14. `hourly_forecast`
+
+The embedded Daily template uses selected deterministic fields from these
+module outputs after GeneratedText validation.
+
 ## Today Composition
 
 The default Today Report module order is:
@@ -98,7 +120,7 @@ module outputs after GeneratedText validation.
 `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.
+day. The default Daily Report composition includes it.
 
 The output uses this shape:
 

docs/internal/prompt-input.md

@@ -68,9 +68,9 @@ Prompt-facing module intervals use local `period_begins` and `period_ends`
 labels; canonical report metadata and source timestamps remain structured
 timestamps where applicable.
 
-Today Report, Tomorrow Report, and Hourly Report module snapshots use the same
-package schema and categories when converted into prompt input. The default
-hourly module list places
+Daily Report, Today Report, Tomorrow Report, and Hourly Report module snapshots
+use the same package schema and categories when converted into prompt input.
+The default hourly module list places
 `precip_timing` under `derived_summaries`, alert and SPC outlooks under
 `applicable_risk_products`, AFD/SPC discussion/weather story under
 `narrative_products`, and current/hourly data under `raw_data`. It does not
@@ -78,10 +78,11 @@ include civil-day summary stanzas. Generated-text and render context artifacts
 are produced later in app orchestration and are not part of the YAML data
 package.
 
-The default Today and Tomorrow module lists include civil-day summary stanzas,
-planning stanzas, and `hourly_forecast` in the data package before structured
-GeneratedText is requested from Scriptorium. Today uses `today_planning`;
-Tomorrow uses `tomorrow_planning`.
+The default Daily, Today, and Tomorrow module lists include civil-day summary
+stanzas, planning stanzas, and `hourly_forecast` in the data package before
+structured GeneratedText is requested from Scriptorium. Daily uses
+`daily_planning`, Today uses `today_planning`, and Tomorrow uses
+`tomorrow_planning`.
 
 Current categories are:
 

docs/internal/report-registry.md

@@ -29,25 +29,25 @@ Each report definition declares:
 
 Report-owned helpers map public command names and config keys to report IDs.
 The generate command names are `daily`, `today`, `tomorrow`, `hourly`,
-`three-day`, `weekend`, and `storm`. Config keys also accept underscore and
-legacy descriptive aliases such as `daily_today`, `three_day_outlook`,
+`three-day`, `weekend`, and `storm`. Config keys also accept selected
+underscore and descriptive aliases such as `three_day_outlook`,
 `weekend_outlook`, and `storm_report`.
 
-`daily` resolves to the existing Daily Today report ID `daily_today`.
-`today` resolves to the independent Today report ID `today`. `reports.today`
-is not an alias for `reports.daily` or `reports.daily_today`.
+`daily` resolves to the dated Daily Report ID `daily`. `today` resolves to the
+independent Today report ID `today`. `reports.today` is not an alias for
+`reports.daily`, and `reports.daily_today` is not a supported config key.
 
 Markdown report definitions use the `scriptorium_markdown` generation mode.
-Their template and structured-text schema identifiers are empty. Today Report,
-Tomorrow Report, and Hourly Report declare `generated_text_template`; the app
-uses their template and schema identifiers to validate generated text and render
-embedded Markdown templates.
+Their template and structured-text schema identifiers are empty. Daily Report,
+Today Report, Tomorrow Report, and Hourly Report declare
+`generated_text_template`; the app uses their template and schema identifiers
+to validate generated text and render embedded Markdown templates.
 
 ## Reports
 
 | Report | ID | Prompt | Generation mode | Artifact group | Batch copy | Prior compatibility |
 | --- | --- | --- | --- | --- | --- | --- |
-| Daily Today | `daily_today` | `weather.daily_report` | `scriptorium_markdown` | `daily` | `daily.md` | Daily Today |
+| Daily Report | `daily` | `weather.daily_generated_text` | `generated_text_template` | `daily` | `daily.md` | Daily Report |
 | Today Report | `today` | `weather.today_generated_text` | `generated_text_template` | `today` | `today.md` | Today Report |
 | Tomorrow Report | `tomorrow` | `weather.tomorrow_generated_text` | `generated_text_template` | `tomorrow` | `tomorrow.md` | Tomorrow Report |
 | Hourly Report | `hourly` | `weather.hourly_generated_text` | `generated_text_template` | `hourly` | `hourly.md` | Hourly Report |
@@ -59,8 +59,8 @@ All report definitions are eligible for generation.
 
 ## Valid Periods
 
-- Daily Today covers the selected local civil day, or the current local civil
-  day when no date override is supplied.
+- Daily Report covers the selected local civil day and requires an explicit
+  date.
 - Today Report covers the selected local civil day, or the current local civil
   day when no date override is supplied.
 - Tomorrow Report covers the next local civil day from generation time.
@@ -91,14 +91,13 @@ report override keys.
 
 The app supplies `weather_api.timezone` as a loaded `time.Location`. Batch
 output path copying uses batch output names from report definitions. Report
-module overrides can use short keys such as `today`, `tomorrow`, and `hourly`,
-canonical report IDs such as `daily_today`, or descriptive names such as
-`three_day_outlook`.
+module overrides can use short keys such as `daily`, `today`, `tomorrow`, and
+`hourly`, or descriptive names such as `three_day_outlook`.
 
 ## Batch Membership
 
 Morning batches include Today Report, 3-Day Outlook, and Weekend Outlook
-except on Sunday. Evening batches include Tomorrow Report. Daily Today and
+except on Sunday. Evening batches include Tomorrow Report. Daily Report and
 Hourly Report are not part of a scheduled batch.
 
 ## State And App Usage