Implemented debug artifacts for the distributor notification adapter

docs/operations.md

@@ -91,6 +91,19 @@ workspace/
     storm/
       YYYY-MM-DD/
         <run_id>.render.json
+  notifications/
+    daily/
+      YYYY-MM-DD/
+        <run_id>.distributor.json
+    three-day/
+      YYYY-MM-DD/
+        <run_id>.distributor.json
+    weekend/
+      YYYY-MM-DD/
+        <run_id>.distributor.json
+    storm/
+      YYYY-MM-DD/
+        <run_id>.distributor.json
   reports/
     daily/
       <run_id>.md
@@ -122,6 +135,7 @@ Each generated report writes metadata that links:
 - prompt input data package path
 - preflight output path
 - managed Markdown report path
+- distributor notification debug artifact path, when notification is attempted
 
 Batch summaries include report status, error text when applicable, notification
 outcome when attempted, valid period, and known artifact paths for each
@@ -153,6 +167,16 @@ not trigger notification. A notification failure fails that report. In a batch,
 other reports continue, the failed report includes notification fields in the
 JSON summary, and the batch returns nonzero.
 
+Each notification attempt writes a debug artifact under `notifications/`. The
+artifact records the rendered bundle ID, idempotency key, managed source path,
+bundle-relative path, bundle created timestamp, accepted upload response, and
+the latest distributor run status response when available. Weatherreporter polls
+status until distributor reports `succeeded` or `failed`, or until the configured
+notification timeout expires. The run status includes the distributor status,
+error text, and raw run report JSON, which can show actions such as
+`replace_older`, `skip_same`, `skip_destination_newer`, or `failed`. Token values
+are not written.
+
 Weatherreporter is responsible for selecting the managed Markdown report,
 constructing a source bundle, and submitting it to the configured distributor
 HTTP endpoint. Distributor remains responsible for destination routing,