Prepare reports for Promptkit migration

docs/roadmap/future.md

@@ -7,8 +7,7 @@ status; current behavior is documented outside `docs/roadmap/`.
 
 Status: Proposed and unimplemented.
 
-Manual Storm Report generation is implemented; see the [CLI reference](../cli.md).
-Automatic storm-event evaluation remains unimplemented.
+Storm reporting, whether manual or automatic, is unimplemented.
 
 Possible direction:
 
@@ -16,7 +15,7 @@ Possible direction:
    story context, hourly thresholds, and material forecast changes.
 2. Evaluate candidates through Scriptorium or another narrow evaluator adapter.
 3. Persist storm lifecycle state.
-4. Generate or update Storm Reports only when a meaningful event is present.
+4. Generate or update a storm report only when a meaningful event is present.
 5. Suppress ordinary low-impact thunder or rain chances.
 
 Possible lifecycle states:
@@ -29,8 +28,8 @@ Possible lifecycle states:
 - `resolved`
 
 Before implementation, the design must preserve scheduled report behavior,
-manual Storm Report generation, inspectable evaluator failures, and fixture
-coverage for deterministic candidate detection.
+inspectable evaluator failures, and fixture coverage for deterministic
+candidate detection.
 
 ## Future Report Types
 
@@ -59,7 +58,7 @@ Possible future modules:
   Changes
 - `weekend_planning` if weekend-specific planning guidance needs a dedicated
   deterministic stanza
-- `storm_window_summary` if manual or automatic Storm Reports need a dedicated
+- `storm_window_summary` if manual or automatic storm reports need a dedicated
   prompt-facing storm-window module
 - separate AFD section aliases, such as `afd_key_messages`,
   `afd_short_term_text`, and `afd_long_term_text`, if separate stanzas prove