Remove legacy distributor report path config

docs/config.md

@@ -101,15 +101,6 @@ contains all managed Markdown reports from that batch.
   Default: `weatherreporter.{location_id}.{report_id}`.
 - `idempotency_key_template`: template for single-report distributor
   idempotency keys. Default: `{bundle_id}.{run_id}`.
-- `report_path_templates`: ordered list of templates for Markdown report paths
-  inside distributor bundles. For `generate <report>`, each rendered path maps
-  to the generated report's managed Markdown source. For `run morning` and
-  `run evening`, the templates are rendered once per included report and each
-  rendered path maps that report's managed Markdown source into the one batch
-  bundle. Default:
-  ```yaml
-  - "{valid_start_date}/{artifact_group}/{valid_start_date}-{artifact_group}-{run_id}.md"
-  ```
 - `batch.enabled`: whether batch distributor notification config is active
   when distributor notification is enabled. Default: `true`.
 - `batch.pipeline_id_template`: template for batch distributor pipeline IDs.

docs/internal/app-orchestration.md

@@ -163,10 +163,11 @@ all planned reports finish, app orchestration evaluates batch notification:
 3. If any planned report failed, the batch notification result is `skipped`
    with reason `one or more reports failed`, and distributor is not called.
 4. If every report succeeded, app orchestration renders batch pipeline, bundle
-   ID, and idempotency key templates, renders `report_path_templates` for each
-   included report, validates every managed source path and bundle path, checks
-   duplicate bundle paths across the batch, calls the notifier once with a
-   multi-file request, and saves a batch notification debug artifact.
+   ID, and idempotency key templates, renders report-specific distributor
+   paths for each included report, validates every managed source path and
+   bundle path, checks duplicate bundle paths across the batch, calls the
+   notifier once with a multi-file request, and saves a batch notification
+   debug artifact.
 
 Batch notification failure records a top-level failed notification, increments
 the aggregate batch failure count, and returns an aggregate batch error without

docs/internal/distributor-adapter.md

@@ -61,12 +61,12 @@ and bundle paths from:
 - `pipeline_id_template`
 - `bundle_id_template`
 - `idempotency_key_template`
-- `report_path_templates`
+- report-specific path templates
 
 For batch uploads, the app layer renders pipeline ID, bundle ID, and
-idempotency key from `notify.distributor.batch.*`, renders
-`report_path_templates` once per included report, and passes the resulting
-multi-file request to this adapter.
+idempotency key from `notify.distributor.batch.*`, resolves report-specific
+path templates once per included report, and passes the resulting multi-file
+request to this adapter.
 
 The token value is read from the environment variable named by `token_env`
 after config loading and `secrets.directory` processing.

docs/operations.md

@@ -256,17 +256,16 @@ top-level `notification` object with fields such as `status`, `reason`,
 Distributor notification is configured with `notify.distributor` and is
 disabled by default. For `generate <report>`, weatherreporter uploads the
 managed Markdown report path recorded in the report result and metadata. That
-single source file can be mapped to one or more configured bundle paths. By
-default, it is mapped to one dated report path. Extra copies written by `--out`
-or `--out-dir` are operator conveniences only.
+single source file is mapped to report-specific bundle paths. Extra copies
+written by `--out` or `--out-dir` are operator conveniences only.
 
 For `run morning` and `run evening`, per-report notification is suppressed. If
 `notify.distributor.enabled` and `notify.distributor.batch.enabled` are both
 true, the batch uploads once after all reports finish successfully. The upload
 contains one file mapping set per included report. Each mapping uses the
-managed Markdown report as the source and renders `report_path_templates` using
-that report's normal template values. All rendered bundle paths across the
-batch must be unique. If any report fails, weatherreporter records a top-level
+managed Markdown report as the source and report-specific path templates for
+that report. All rendered bundle paths across the batch must be unique. If any
+report fails, weatherreporter records a top-level
 notification status of `skipped` with reason `one or more reports failed` and
 does not call distributor. If batch notification is disabled, run commands do
 not fall back to per-report uploads.

docs/troubleshooting.md

@@ -300,15 +300,15 @@ Relevant docs: [Configuration reference](config.md),
 Symptom: a batch returns nonzero with duplicate bundle path context before a
 distributor run ID is accepted.
 
-Likely cause: `notify.distributor.report_path_templates` rendered the same
+Likely cause: report-specific distributor path templates rendered the same
 bundle-relative path for two included reports in the same batch.
 
 Diagnostic: inspect the error in stdout or stderr. The validation error
 includes the duplicate bundle path plus the report IDs, RunIDs, and managed
 source paths involved.
 
-Safe fix: change `notify.distributor.report_path_templates` so every report in
-a batch renders a unique path. Include values such as `{artifact_group}`,
+Safe fix: configure a per-report distributor path override so every report in a
+batch renders a unique path. Include values such as `{artifact_group}`,
 `{valid_start_date}`, `{batch_output_name}`, or `{run_id}` when needed.
 
 Relevant docs: [Configuration reference](config.md),
@@ -411,7 +411,7 @@ Diagnostic: inspect stdout JSON or stderr status lines for
 `notificationError` or the top-level batch notification `error`. Confirm
 `notify.distributor.endpoint`,
 `notify.distributor.pipeline_id_template`,
-`notify.distributor.report_path_templates`, and token configuration. Token
+report-specific distributor paths, and token configuration. Token
 values are redacted from weatherreporter errors.
 
 If the upload was accepted but destination output did not change, inspect the