Document Today report workflow

docs/internal/briefing.md

@@ -42,6 +42,10 @@ 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 Report supports the Daily-style civil-day modules plus `today_planning`
+and `hourly_forecast`; those outputs feed the Today 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.

docs/internal/generatedtext.md

@@ -9,9 +9,8 @@ This document describes structured generated-text handling in
 generated-text-template reports and builds curated render contexts for
 templates. It also owns the generated-text catalog that connects report
 definitions to validators, render-context builders, schema assets, and template
-assets. The implemented contracts are Today, Tomorrow Report, and Hourly
-Report. Today support is internal until a report definition references the
-`today` schema and template IDs.
+assets. The implemented contracts are Today Report, Tomorrow Report, and Hourly
+Report.
 
 ## Inputs And Outputs
 
@@ -50,7 +49,9 @@ The hourly generated text JSON accepts:
 JSON when blank.
 
 The Today generated text JSON accepts the same public fields and validation
-rules as Tomorrow:
+rules as Tomorrow. It is selected by the active Today report definition through
+schema ID `today`, template ID `today`, and prompt ID
+`weather.today_generated_text`:
 
 ```json
 {

docs/internal/module.md

@@ -48,6 +48,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.
 
+## Today Composition
+
+The default Today 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. `hourly_forecast`
+14. `today_planning`
+
+The embedded Today template uses selected deterministic fields from these
+module outputs after GeneratedText validation.
+
 ## Tomorrow Composition
 
 The default Tomorrow Report module order is:
@@ -70,6 +92,24 @@ The default Tomorrow Report module order is:
 The embedded Tomorrow template uses selected deterministic fields from these
 module outputs after GeneratedText validation.
 
+## Today Planning
+
+`today_planning` emits current-day planning facts for Today Report. Its output
+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:
+
+- `morning_readiness`
+- `commute`
+- `outdoor_planning`
+- `things_to_watch`
+- `confidence`
+
+The type is `briefing.TodayPlanningModule`; it is independent from
+`briefing.TomorrowPlanningModule`.
+
 ## Hourly Composition
 
 The default Hourly Report module order is:

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.
 
-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
+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,9 +78,10 @@ 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 Tomorrow module list includes civil-day summary stanzas,
-`tomorrow_planning`, and `hourly_forecast` in the data package before
-structured GeneratedText is requested from Scriptorium.
+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`.
 
 Current categories are:
 

docs/internal/report-registry.md

@@ -33,6 +33,10 @@ The generate command names are `daily`, `today`, `tomorrow`, `hourly`,
 legacy descriptive aliases such as `daily_today`, `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`.
+
 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
@@ -88,7 +92,7 @@ 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 accepted aliases such as
+canonical report IDs such as `daily_today`, or descriptive names such as
 `three_day_outlook`.
 
 ## Batch Membership

docs/internal/reporttemplate.md

@@ -6,9 +6,8 @@ in `internal/reporttemplate`.
 ## Purpose
 
 `internal/reporttemplate` owns repository-native report templates and companion
-GeneratedText JSON schemas. The implemented template contracts are Today,
-Tomorrow Report, and Hourly Report. Today assets are available internally until
-a report definition selects them.
+GeneratedText JSON schemas. The implemented template contracts are Today
+Report, Tomorrow Report, and Hourly Report.
 
 The package embeds assets from:
 
@@ -36,6 +35,10 @@ The implemented template IDs are `today`, `tomorrow`, and `hourly`. The
 implemented schema IDs are also `today`, `tomorrow`, and `hourly`, backed by
 matching `*.generated_text.schema.json` files.
 
+The Today generated-text prompt source is
+`internal/reporttemplate/prompts/today.generated_text.md`, selected by prompt
+ID `weather.today_generated_text`.
+
 ## Boundaries
 
 This package owns embedded asset lookup, Go template parsing, and Markdown