Harden scheduled report runs

docs/cli.md

@@ -52,8 +52,10 @@ weatherreporter run evening
 preflight output, Markdown report, and metadata file under the configured
 workspace. `run evening` generates the Tomorrow Planning Brief. `run morning`
 generates Daily Today and the 3-Day Outlook, plus Weekend Outlook except on
-Sunday. Other `generate` commands resolve one report request and stop before
-report generation.
+Sunday. Run commands continue remaining reports after an independent report
+failure, print a JSON aggregate summary to stdout, write compact report status
+logs to stderr, and return nonzero when any report failed. Other `generate`
+commands resolve one report request and stop before report generation.
 
 ## Flags
 
@@ -62,6 +64,7 @@ report generation.
 - `--units VALUE`: override configured Weather API units.
 - `--tz NAME`: override configured Weather API timezone.
 - `--out PATH`: optional Markdown report copy for `generate daily`, `generate tomorrow`, `generate three-day`, and `generate weekend`; reserved for later generated report output on other `generate` commands.
+- `--out-dir PATH`: optional directory for extra Markdown report copies from `run morning` and `run evening`.
 - `--date YYYY-MM-DD`: optional date for `generate daily`; defaults to the current local date in the configured timezone.
 - `--start TIME`: required start time for `generate storm`.
 - `--end TIME`: required end time for `generate storm`.

docs/operations.md

@@ -20,6 +20,11 @@ workspace. The evening run resolves only the Tomorrow Planning Brief. The
 morning run generates Daily Today and the 3-Day Outlook, plus Weekend Outlook
 except on Sunday.
 
+Scheduled run commands print a JSON aggregate summary to stdout and compact
+per-report status lines to stderr. If one report fails, remaining independent
+reports are still attempted. The command returns nonzero after the run when any
+report failed.
+
 ## Filesystem Layout
 
 The default workspace root is `workspace`.
@@ -72,6 +77,10 @@ The Markdown report is written to a RunID-managed report path. When `--out` is
 provided to `generate daily`, `generate tomorrow`, `generate three-day`, or
 `generate weekend`, the managed report is also copied to that path.
 
+For `run morning` and `run evening`, `--out-dir PATH` writes extra Markdown
+copies using each report definition's default filename, such as `daily.md`,
+`three-day.md`, `weekend.md`, or `tomorrow.md`.
+
 ## Run Identifiers
 
 Run IDs are based on generation time plus report ID, such as:
@@ -96,6 +105,9 @@ Each generated report writes metadata that links:
 - preflight output path
 - rendered report path
 
+Run summaries include each report ID, prompt ID, RunID, status, error text when
+applicable, valid period, and artifact paths known to the application.
+
 ## Recent Changes
 
 When a prior comparable Daily briefing snapshot exists for the same valid local
@@ -124,5 +136,9 @@ If `scriptorium run` exits nonzero after writing a report, the generated report
 and metadata remain available for inspection. Exit code `2` is still returned as
 an error because it indicates validation failed, even if report output exists.
 
+For scheduled runs, inspect stdout first for the aggregate JSON summary, then
+use the per-report artifact paths in that summary to inspect briefing,
+data-package, preflight, metadata, and rendered report files.
+
 The application does not currently implement resume, cleanup, archive, or
 remote storage behavior.