Document Scriptorium session recap integration

docs/integrations/scriptorium.md

@@ -217,23 +217,40 @@ Narratio should treat non-zero exit codes as failed stage execution, but may rec
 
 ## 17. Suggested Narratio Configuration Shape
 
-Illustrative (not required schema):
+Illustrative `pipeline.yml` shape:
 
 ```yaml
 scriptorium:
+  binary: scriptorium
   config_path: /etc/scriptorium/config.yml
-  stages:
+  timeout: 10m
+  render_debug: false
+  artifacts:
     session_recap:
+      enabled: true
       prompt_id: dnd.session_recap
       profile_id: local-quality   # optional
-      inputs: [transcript, glossary, previous_recap]
-      vars: [session_id, session_date, campaign_name]
-      output_path_template: artifacts/{session_id}/session_recap.md
-      timeout: 2m
-      render_debug: false
+      output_path: artifacts/session_recap.md
+      timeout: 10m
+      render_debug: false          # optional artifact override
+      inputs:
+        transcript:
+          source: processed_transcript
+          required: true
+        previous_recap:
+          source: previous_session_artifact
+          artifact: session_recap
+          path: ""                 # optional
+          required: false
+      vars:
+        session_id: true
+        session_date: true
+        campaign_name: true
+        previous_session_id: true
+        output_kind: session_recap
 ```
 
-The key idea: map Narratio stage/artifact names to prompt ID, optional profile, expected inputs, and output destination.
+The key idea: map Narratio artifact names to prompt ID, optional profile, expected inputs, vars, and output destination.
 
 ## 18. Testing Strategy for Narratio Integration
 
@@ -317,6 +334,6 @@ Possible later extensions:
 
 - HTTP API integration
 - S3 artifact references if Scriptorium adds S3 reader support
-- storing render diagnostics alongside generated artifacts
+- richer render diagnostics and policy controls
 - token budgeting/prompt-size checks
 - batch execution if Scriptorium later adds batch support