Forward Scriptorium credentials through the shared adapter path

docs/troubleshooting.md

@@ -739,6 +739,20 @@ manifest-owned.
 Relevant references: [Operations: Stage Execution and Continuation Behavior](./operations.md#stage-execution-and-continuation-behavior)
 and [Manifest Internals](./internal/manifest.md#transcribe-owned-speaker-state).
 
+## Scriptorium returns HTTP 401 during trim or analyze
+
+Check that Narratio's pipeline selects the credential names required by
+Scriptorium, for example `scriptorium.credentials: [OPENROUTER_API_KEY]`.
+Provision the values through the existing environment or secrets directory;
+exporting a key without selecting it does not forward it to the child process.
+See [Scriptorium credentials](config.md#scriptorium-credentials).
+
+Once corrected, retry the failed run normally; forcing previously successful
+transcription or analysis is unnecessary. If authentication still fails, check
+the selected Scriptorium backend, credential validity, and provider access
+without printing keys. A 401 can indicate an invalid key as well as a missing
+one.
+
 ## Scriptorium private input changed without a rerun
 
 Symptom: