Merge commit 'd5563c5736f489b48e91ca338f61c1e993337065'
This commit is contained in:
@@ -62,7 +62,7 @@ The compatible application versions are selected through these variables:
|
||||
| Variable | Default |
|
||||
| --- | --- |
|
||||
| `dnd_pipeline_audita_version` | `v2.0.1` |
|
||||
| `dnd_pipeline_narratio_version` | `v3.0.0` |
|
||||
| `dnd_pipeline_narratio_version` | `v3.1.0` |
|
||||
| `dnd_pipeline_notarius_version` | `v0.8.1` |
|
||||
| `dnd_pipeline_seriatim_version` | `v1.5.0` |
|
||||
| `dnd_pipeline_scriptorium_version` | `v0.15.0` |
|
||||
@@ -196,12 +196,26 @@ force all stages to rerun. The role performs no session migration.
|
||||
| `dnd_pipeline_scriptorium_transient_retries` | `null`; native default |
|
||||
| `dnd_pipeline_narratio_audita_credentials` | `[AUDITA_LLM_API_KEY]` |
|
||||
| `dnd_pipeline_narratio_notarius_credentials` | `[OPENROUTER_API_KEY]` |
|
||||
| `dnd_pipeline_narratio_scriptorium_credentials` | `[OPENROUTER_API_KEY]` |
|
||||
|
||||
`dnd_pipeline_audita_output_schema` is also the Narratio Audita-adapter schema;
|
||||
it is the shared cross-application boundary. Other Narratio-local controls,
|
||||
including reports, timeouts, debug rendering, presentation, and bounds prompt
|
||||
profile selection, remain Narratio defaults.
|
||||
|
||||
Narratio v3.1.0 forwards the selected Scriptorium credential names for trim,
|
||||
analysis, character families, and render-debug calls. The Scriptorium and
|
||||
Notarius lists independently default to the existing `OPENROUTER_API_KEY` name;
|
||||
using the same provisioned value does not couple their selections. Inventory
|
||||
may replace the Scriptorium list, set `[]` to forward nothing, or set `null` to
|
||||
omit the field. Each selected name must resolve to a nonempty value when
|
||||
Narratio loads configuration, even for inspection commands. Values may come
|
||||
from Narratio's process environment or its existing secrets directory;
|
||||
`dnd_pipeline_secrets` is optional file provisioning, not the only source.
|
||||
After upgrading and provisioning the selected key, retry a failed trim or
|
||||
analysis normally. Do not force already successful work solely because a
|
||||
credential was added or rotated.
|
||||
|
||||
### Storage and publication policy
|
||||
|
||||
The suite selects Narratio's S3 backend and the established Backblaze-compatible
|
||||
|
||||
Reference in New Issue
Block a user