Rename rolling report to hourly

docs/internal/briefing.md

@@ -38,7 +38,7 @@ Outputs:
 Every registered composition entry has a builder. Unknown or unimplemented
 module IDs fail validation instead of being skipped.
 
-Near-Term Report supports source and valid-period modules that operate over its
+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`.
@@ -67,7 +67,7 @@ builders run. Configured `location` values are prompt context only; Weather API
 `sourceLocationId` and `sourceLocation` remain source provenance.
 
 `area_forecast_discussion` uses optional `sections` configuration to include a
-subset of discussion fields. Near-Term Report defaults this module to
+subset of discussion fields. Hourly Report defaults this module to
 `key_messages` and `short_term`.
 
 `spc_convective_outlooks` uses collected SPC run metadata and derived

docs/internal/facts.md

@@ -27,7 +27,7 @@ Outputs:
   report-period SPC convective outlooks and discussions, daily summaries,
   daypart summaries, and Storm Report window summary
 
-Near-Term Report uses the generic valid-period hourly and narrative selection
+Hourly Report uses the generic valid-period hourly and narrative selection
 for its rolling six-hour window. Its derived facts include precipitation timing
 from the selected hourly periods, alert overlaps for the six-hour period, and
 SPC outlooks/discussions overlapping that period. It does not build daily
@@ -68,7 +68,7 @@ and inspection.
 - Invalid timezone names return an error.
 - Missing required hourly forecast data returns the underlying forecast
   derivation error for reports that require daily summaries.
-- Near-Term Report can derive its default module facts without daily or
+- Hourly Report can derive its default module facts without daily or
   daypart summaries.
 - Missing optional narrative, alert, discussion, daily, or weather story data
   produces empty or nil derived fields.

docs/internal/module.md

@@ -47,9 +47,9 @@ 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.
 
-## Near-Term Composition
+## Hourly Composition
 
-The default Near-Term Report module order is:
+The default Hourly Report module order is:
 
 1. `metadata`
 2. `current_conditions`
@@ -61,7 +61,7 @@ The default Near-Term Report module order is:
 8. `spc_convective_discussion`
 9. `weather_story`
 
-Near-Term Report does not include daily or daypart summary modules by default.
+Hourly Report does not include daily or daypart summary modules by default.
 Its `area_forecast_discussion` item is configured to include only
 `key_messages` and `short_term`.
 

docs/internal/prompt-input.md

@@ -68,7 +68,7 @@ Prompt-facing module intervals use local `period_begins` and `period_ends`
 labels; canonical report metadata and source timestamps remain structured
 timestamps where applicable.
 
-Near-Term Report uses the same package schema and categories. Its default
+Hourly Report uses the same package schema and categories. Its default
 package includes `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
@@ -112,7 +112,7 @@ None.
 ## Skip And Resume Behavior
 
 None. Recent Changes is always present as an `items` list and may be empty.
-Near-Term Report currently writes an empty `items` list.
+Hourly Report currently writes an empty `items` list.
 
 ## Failure Behavior
 

docs/internal/report-registry.md

@@ -31,7 +31,7 @@ Each report definition declares:
 | --- | --- | --- | --- | --- | --- |
 | Daily Today | `daily_today` | `weather.daily_report` | `daily` | `daily.md` | Daily Today, Daily Tomorrow |
 | Daily Tomorrow | `daily_tomorrow` | `weather.daily_report` | `daily` | `tomorrow.md` | Daily Today, Daily Tomorrow |
-| Near-Term Report | `near_term` | `weather.near_term_report` | `near-term` | `near-term.md` | Near-Term Report |
+| Hourly Report | `hourly` | `weather.hourly_report` | `hourly` | `hourly.md` | Hourly Report |
 | 3-Day Outlook | `three_day` | `weather.three_day_outlook` | `three-day` | `three-day.md` | 3-Day Outlook |
 | Weekend Outlook | `weekend` | `weather.weekend_outlook` | `weekend` | `weekend.md` | Weekend Outlook |
 | Storm Report | `storm` | `weather.storm_report` | `storm` | `storm.md` | Storm Report |
@@ -43,7 +43,7 @@ All report definitions are eligible for generation.
 - Daily Today covers the selected local civil day, or the current local civil
   day when no date override is supplied.
 - Daily Tomorrow covers the next local civil day from generation time.
-- Near-Term Report covers the half-open six-hour period from generation time in
+- Hourly Report covers the half-open six-hour period from generation time in
   the effective report timezone. The duration is an internal report constant,
   not a configuration field.
 - 3-Day Outlook covers the interval from generation time through local midnight
@@ -69,13 +69,12 @@ IDs, then uses the registry for report policy.
 
 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 the `near_term` or `near-term` keys for Near-Term
-Report.
+module overrides can use the `hourly` key for Hourly Report.
 
 ## Batch Membership
 
 Morning batches include Daily Today, 3-Day Outlook, and Weekend Outlook except
-on Sunday. Evening batches include Daily Tomorrow. Near-Term Report is not part
+on Sunday. Evening batches include Daily Tomorrow. Hourly Report is not part
 of a scheduled batch.
 
 ## State And App Usage