Rename rolling report to hourly

docs/roadmap/generated-text.md

@@ -4,8 +4,8 @@
 
 This roadmap defines planned work to move selected reports from full Markdown
 LLM generation to deterministic Markdown rendering with structured LLM-filled
-text slots. The first target report is the rolling next-hours report, now named
-`hourly` rather than `near_term`.
+text slots. The first target report is the rolling next-hours report, named
+`hourly`.
 
 This feature is not implemented yet, so this document lives under
 `docs/roadmap/`.
@@ -67,15 +67,14 @@ not become a second application logic layer.
   Schema dependency in the first implementation.
 - Do not generate schemas or templates from inline Go.
 - Start with the rolling next-hours report only.
-- Rename the planned `near_term` report to `hourly`.
-- Do not keep both `near_term` and `hourly` public report IDs.
+- Use `hourly` as the only public report ID for the rolling next-hours
+  report.
+- Do not keep compatibility aliases from retired roadmap terminology.
 - Do not add a generic workflow engine or plugin system.
 
 ## Hourly Report Target
 
-The planned `near_term` report should become the `hourly` report.
-
-Target report identity:
+The rolling next-hours report target identity is:
 
 - report ID: `hourly`
 - CLI command: `weatherreporter generate hourly`
@@ -143,7 +142,7 @@ Keep the first schema small. Example shape:
 
 ```json
 {
-  "summary": "Brief near-term overview.",
+  "summary": "Brief hourly overview.",
   "timing": "Plain-language timing of notable changes.",
   "impacts": "Practical impacts for the next few hours.",
   "confidence": "Optional confidence or uncertainty note."