Updated the distributor bundle path template

docs/internal/app-orchestration.md

@@ -90,8 +90,9 @@ generation returns an error after writing output, the managed report and
 metadata remain inspectable. Notification is not attempted after Weather API,
 briefing, prompt input, render, Scriptorium run, or metadata-save failures.
 When notification is attempted, the debug artifact records request identity,
-including rendered pipeline ID, accepted upload fields, distributor status
-fields, raw status report JSON when available, and redacted failure context.
+including rendered pipeline ID, bundle paths, accepted upload fields,
+distributor status fields, raw status report JSON when available, and redacted
+failure context.
 `--out` copies are never used as notification source files.
 
 ## Batch Workflow
@@ -141,5 +142,5 @@ Inspect:
 - Render preflight precedes Scriptorium report generation.
 - Recent Changes are computed from structured briefing snapshots.
 - Metadata links artifacts produced for a run.
-- Distributor notification uses the managed Markdown report path, not extra
-  output copies.
+- Distributor notification maps the managed Markdown report path to configured
+  bundle paths; extra output copies are not upload sources.

docs/internal/distributor-adapter.md

@@ -21,8 +21,7 @@ Inputs:
 - pipeline ID
 - bundle ID
 - idempotency key
-- source Markdown report path
-- bundle-relative Markdown path
+- source Markdown report path and bundle-relative path mappings
 - bundle created timestamp
 - context for cancellation
 
@@ -55,24 +54,24 @@ The adapter is built from `notify.distributor` config:
 - `token_env`
 - `timeout`
 
-The app layer renders pipeline ID, bundle ID, idempotency key, and bundle path
+The app layer renders pipeline ID, bundle ID, idempotency key, and bundle paths
 from:
 
 - `pipeline_id_template`
 - `bundle_id_template`
 - `idempotency_key_template`
-- `report_path_template`
+- `report_path_templates`
 
 The token value is read from the environment variable named by `token_env`
 after config loading and `secrets.directory` processing.
 
 ## Upload Behavior
 
-The adapter calls distributor `UploadFiles` with exactly one file:
+The adapter calls distributor `UploadFiles` with one or more file mappings:
 
 - pipeline ID: the rendered distributor workflow selector
 - source path: the managed Markdown report path selected by app orchestration
-- bundle path: the rendered bundle-relative report path
+- bundle paths: rendered bundle-relative report paths
 - created: the report generation timestamp
 
 The adapter creates a distributor upload client with the configured endpoint,
@@ -91,11 +90,11 @@ with the status report preserved.
 ## Failure Behavior
 
 The adapter validates required endpoint, token env name, token value, pipeline
-ID, bundle ID, idempotency key, source path, bundle path, and upload client
-inputs before uploading.
+ID, bundle ID, idempotency key, upload files, source paths, bundle paths, and
+upload client inputs before uploading.
 
 Upload failures include endpoint, pipeline ID, bundle ID, idempotency key,
-source path, and bundle path context. Token values are redacted from adapter
+source paths, and bundle paths context. Token values are redacted from adapter
 errors.
 
 Distributor idempotency conflicts are exposed as a weatherreporter-owned

docs/internal/state.md

@@ -94,7 +94,8 @@ prepared by creating their parent directory; Scriptorium writes the report body
 to the prepared path. Extra Markdown copies are handled by app orchestration.
 Distributor notification debug artifacts are written atomically when
 notification is attempted and include rendered distributor pipeline ID, bundle
-ID, idempotency key, upload status, latest run status, and redacted errors.
+ID, idempotency key, bundle paths, upload status, latest run status, and
+redacted errors.
 
 Inspection helpers read existing metadata, briefing, and data package files.
 Missing metadata directories return no inspection records or no prior snapshot