Remove legacy distributor report path config

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.