Add Tomorrow planning brief generation

docs/operations.md

@@ -2,15 +2,18 @@
 
 ## Normal Workflow
 
-The implemented Daily generation workflow is:
+The implemented Daily-family generation workflows are:
 
 ```text
 weatherreporter generate daily --date 2026-05-29
+weatherreporter generate tomorrow
+weatherreporter run evening
 ```
 
-The command fetches weather data, builds the Daily briefing, builds the prompt
-input data package, runs `scriptorium render`, runs `scriptorium run`, and
-writes inspectable artifacts under the configured workspace.
+These commands fetch weather data, build a Daily briefing for the resolved
+valid date, build the prompt input data package, run `scriptorium render`, run
+`scriptorium run`, and write inspectable artifacts under the configured
+workspace. The evening run resolves only the Tomorrow Planning Brief.
 
 ## Filesystem Layout
 
@@ -36,8 +39,9 @@ workspace/
       <run_id>.md
 ```
 
-The Markdown report is written to the managed report path. When `--out` is
-provided, the managed report is also copied to that path.
+The Markdown report is written to a RunID-managed report path. When `--out` is
+provided to `generate daily` or `generate tomorrow`, the managed report is also
+copied to that path.
 
 ## Run Identifiers
 
@@ -67,7 +71,9 @@ Each Daily generation writes metadata that links:
 
 When a prior comparable Daily briefing snapshot exists for the same valid local
 date, the app compares structured briefing data before writing the prompt input
-data package. Meaningful changes are included under `recentChanges.items`.
+data package. Daily Today and Daily Tomorrow can compare with each other when
+they cover the same valid local date. Meaningful changes are included under
+`recentChanges.items`.
 
 When no prior comparable snapshot exists, or no configured threshold is crossed,
 the Recent Changes list is empty.