-
eric released this
2026-09-28 03:01:38 +00:00 | 0 commits to main since this releaseScriptorium v0.15.0
This minor release changes Scriptorium's application grant to GPL version 3 or
later, aligns its repository policies and attribution notices, and updates the
selected Promptkit and ConfigKit patch releases.Licensing and upgrade impact
Scriptorium's application source and binaries are now distributed under
GPL-3.0-or-later. Review COPYRIGHT
and LICENSE
before redistributing or incorporating this version. Material adapted from
Standard Repository Policies remains separately licensed under CC-BY-SA-4.0;
the attribution notices
identify its scope and license text. Existing dependency grants are unchanged,
and earlier tagged releases retain their own published terms.Dependency updates
Scriptorium now selects Promptkit v0.11.2 and ConfigKit v0.4.2. The current
CLI,
HTTP API,
and configuration
references describe the executable contracts.Downloads
-
2026-09-26 18:40:04 +00:00 | 14 commits to main since this releaseScriptorium v0.14.0
This minor release adopts Promptkit v0.11.0 and ConfigKit v0.4.0, adds
application-configuration inspection, and exposes request retry controls,
whole-run deadlines, and optional terminal execution reports.Configuration migration
Scriptorium now uses ConfigKit for application configuration. This intentionally
changes accepted input and precedence:- An existing empty file is invalid; use
{}for an empty mapping. Explicit
empty strings and zeroes replace lower values, whilenullis accepted only
for nullable fields.--config ''is invalid. An explicitly empty server
address reaches the standard HTTP server rather than restoring:8080. - YAML decoding is stricter: unknown fields, additional documents,
anchors/aliases, unsupported scalar forms, and other inputs rejected by
ConfigKit now fail. Theconfigkitkey is reserved, and ConfigKit's source
and resource limits apply. Backend parameter integers use itsint64shape. - File-backed configurations can explicitly import path or glob fragments and
select one named overlay with--config-overlay. These files stay under the
selected configuration file's canonical directory. Application path values
remain relative to the process working directory. Only explicitly supplied
application CLI flags override file or overlay settings.
Use
config validate,config show,config sources, andconfig explainto
inspect application settings without creating an engine or contacting a model.
Validation is not a provider probe or complete Promptkit definition check;
effective output is not guaranteed reloadable. Inspection keeps ordinary
extra_paramsvalues, including historical values, andapi_key_envreference
names visible. Keep secrets out of parameters and protect inspection output;
actual API-key values remain with Promptkit and are never resolved by ConfigKit.
Request retry overrides and Promptkit credential requirements are separate
from application configuration.Promptkit and execution changes
Promptkit v0.11.0 uses its
/v2catalogs. Thedeepseek-3-2,
deepseek-4-flash, anddeepseek-4-proprofile IDs are removed without aliases;
select an available catalog profile, a maintained Promptkit profile, or a
complete application-owned profile.Promptkit's built-in transient retry default is two additional attempts. This
can increase provider calls, latency, and cost; an application or request
retry override of zero disables additional attempts. Repair generations have
their own retry budgets. Generation timeouts apply per attempt. CLI
--run-timeoutand HTTPrun_timeout_secondsadd optional whole-run deadlines;
an expired HTTP execution returns504 deadline_exceeded, caller cancellation
returns408 request_canceled, and a live-context provider-attempt failure
remains a 502 response.CLI
--execution-reportand HTTPinclude_execution_reportexpose optional
terminal reports. Reports are absent when no terminal observation exists, can
contain sensitive identifiers, and do not replace result usage. CLI report
writes are separate and nontransactional; HTTP report bytes count toward the
response-size limit.For complete behavior, see the
CLI,
configuration,
HTTP API,
and operations
references. The repository now includes
dependency attribution and license texts.Downloads
- An existing empty file is invalid; use
-
2026-08-29 15:39:22 +00:00 | 41 commits to main since this releaseScriptorium v0.13.0
Promptkit v0.9 Adoption
Scriptorium now uses
Promptkitv0.9.0
and supports the complete Promptkit v0.9 prompt and profile definition format
through its configured directory sources. This includes prompt versions,
optional inputs, all supported message roles, cache control, session templates,
output schemas and repair budgets, profile inheritance, backend selection,
provider controls, optional credential environment names, and JSON-compatible
extra parameters.Promptkit remains the canonical owner of definition parsing and framework
validation. Scriptorium continues to own its CLI, HTTP, configuration,
presentation, and deployment contracts.Application Features
runandrendercan select an explicit prompt version and can execute
prompts that do not declare or reference inputs.- CLI and HTTP requests can provide a direct session ID. Reasoning controls can
inherit, replace, or explicitly clear the selected profile value. - Application configuration can register custom OpenAI-compatible backends
with optional credential environment names, extra parameters, concurrency
limits, and queue policy. inspect promptandinspect profileprovide deterministic text or JSON
views without invoking a model. Profile inspection does not read credential
values or require a prompt definition.- Prepared output, CLI summaries, and HTTP metadata report effective backend
identity when available. - HTTP requests rejected by backend capacity policy return
503with the
stablecapacity_exceededcode. One server-scoped Promptkit engine enforces
those limits across concurrent requests.
See the versioned application contracts for exact behavior:
- CLI reference
- HTTP API reference
- Configuration reference
- Operations guide
- Promptkit v0.9 format reference
Compatibility And Operations
There are no intentional removals from the v0.12 application interfaces. The
Promptkit upgrade does enforce its current definition-safety rules, including
supported message roles, absolute HTTP or HTTPS endpoints, contained content
and schema paths, bounded repair budgets, and JSON-compatible extra parameters.
Definitions rejected by these rules must be corrected before use.Credential values remain outside configuration, definition files, CLI flags,
and HTTP payloads. Named environment sources are optional unless a selected
Promptkit profile explicitly requires a key. A positive repair budget permits
additional provider calls and can increase latency, token use, and cost.The HTTP service retains only the shared operational state needed for backend
admission and in-flight request handling. Scriptorium does not retain durable
conversation, workflow, checkpoint, or resume state.Downloads
-
2026-07-28 19:55:31 +00:00 | 59 commits to main since this releaseScriptorium v0.12.0
Breaking Project Boundary
Scriptorium is now an executable-only CLI and HTTP application. This is a
breaking change for Go consumers: the former root Go package is not included,
and no compatibility facade is provided.Scriptorium
v0.11.1was the final framework-bearing release. Former Go
consumers should follow the
migration guide
and adopt
Promptkitv0.1.0
for in-process prompt preparation and execution.Application Interfaces
The Scriptorium command-line and HTTP application interfaces remain. Their
canonical documentation defines the supported commands, configuration,
requests, responses, operational behavior, and deployment responsibilities:Framework Dependency And Consumers
The released Scriptorium binaries use Promptkit
v0.1.0as their framework
dependency. Promptkit owns the reusable engine, source formats, profiles,
generation boundary, and validation contracts. See the
Promptkit Go consumer guide
for that supported API.All known downstream Go consumers were migrated to Promptkit before this
release.Downloads