eric/narratio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 27 Wiki Activity

27 Releases 30 Tags

RSS Feed
  • v3.1.0 40cbf42438
    Compare

    Narratio v3.1.0
    All checks were successful
    ci/woodpecker/push/verify Pipeline was successful
    Details
    ci/woodpecker/tag/release Pipeline was successful
    Details
    Stable

    eric released this 2026-09-29 18:02:18 +00:00 | 0 commits to main since this release

    Narratio v3.1.0

    This minor release adds explicit provider-credential forwarding to Scriptorium
    for trim bounds generation and artifact analysis.

    Compatibility and upgrade

    Existing pipelines remain valid. An omitted, null, or empty
    pipeline.scriptorium.credentials list continues to forward no provider keys.
    When Scriptorium needs a credential, provision its environment variable through
    Narratio's existing environment or secrets-directory mechanism and list the
    exact name in the pipeline, for example:

    scriptorium:
  credentials: [OPENROUTER_API_KEY]

    Selected references must resolve to nonempty values when Narratio loads the
    pipeline, even if the current command will not run Scriptorium. A Narratio
    overlay replaces the complete list, and [] clears it. After correcting a
    failed trim or analysis invocation, retry normally; successful work need not be
    forced solely because a credential was added or rotated. See
    Scriptorium credentials and the
    401 troubleshooting guide.

    Changes

    • Forward selected, already-resolved credential names and values to Scriptorium
      for trim, analysis, character-family generation, and render-debug calls.
      Scriptorium still owns provider and profile selection; Narratio does not add
      a model-request --api-key-env override.
    • Register selected values for captured subprocess-output and failure-diagnostic
      redaction. Inspection and invocation metadata contain credential names, never
      their values. This protection does not scan files Scriptorium writes directly.
    • Reuse the credential-forwarding boundary shared with Audita and Notarius.
      Retire the completed Scriptorium credential-forwarding bug report from the
      source roadmap; its history remains in Git.

    COPYRIGHT | LICENSE | ATTRIBUTION

    Downloads