Repository navigation
Scriptorium v4.0.0
Scriptorium v4.0.0 is a major release from scriptorium-v3.0.1 in this repository.
Changes
- Add triage, implement and review run kinds, version 3 repository configuration, repository model policy and trusted pipeline triggers (#115, #117).
- Preserve version 2 behavior alongside version 3 in the N/N−1 compatibility window (#124). Version 2 remains implement-only.
- Read repository inputs only from
.scriptorium/config.jsonand.scriptorium/Dockerfile, and publish the optional editor schema pinned to this release (#125). - Narrow sandbox tokens by run kind; post framed run results from the host, and maintain run and action comments; supply continuation and host facts through the shared prompt (#116, #118, #119, #120).
- Pick up issues in configured priority order (#121).
- Add a read-only host status command with launch-budget reporting, explicit host reasoning effort and model guidance, and enforce implement capacity across providers (#136, #135, #137).
Impact
This release changes repository input paths, repository configuration, sandbox token-command arguments and run/comment contracts. Repository configuration versions 3 and 2 are supported; the directory rename and new run/action comment templates apply to both. Hosts require explicit models.effort; repositories choosing version 3 must supply its run-kind contract. Existing recorded runs retain their selected model and effort when resumed.
Migration
- Prepare a candidate host configuration with explicit
models.effort(set"high"to retain the previous effort), and validate it with the candidate's read-onlystatuscommand. - Update the platform token command to accept the sandbox permissions JSON argument after
<owner>/<name>, mint a token narrowed to exactly that set or fail, and verify the App grants every requested permission. A repository token request still supplies only the repository argument. The candidate status command does not validate this external command. - Before a v4 host serves a repository, move its inputs to
.scriptorium/config.jsonand.scriptorium/Dockerfile. Retain version 2 for implement-only behavior, or adopt version 3 after the host supports it. The path rename is required for both versions; there is no legacy-path fallback. - Review custom comment templates for the new run/action contract, then promote the host in a separately approved maintenance window. Repository adoption and the live host switch are separate work.
This release publishes artifacts only. It does not install or deploy the host or change any adopter.
Documentation pinned to this release: host operation and migration, repository configuration and compatibility, sandbox images, and configuration schema.
Known findings carried forward
These remain tracked separately: #107, #139, #140, #141, #144, and #147.
Release verification
- Release PR: #150.
- Reviewed head:
8bd6d2a3709bc12d4a62e4f79b8b080e704a357f. - Merge commit and tag target:
d744de1968d5d4d99caf8a4b7eb6f949786f21cf. The entire merged tree matches the reviewed tree; manifest version and dependency pins were checked before tagging. - Annotated tag object:
0ac8292133c08669a88ee0370ac106587aacece0; remote peeled target matches the merge commit. GitHub confirms an ordinary, published release (neither draft nor prerelease), visible in the release list and selected as latest. - Frozen-lockfile install and full
pnpm validatepassed on Node.js 24.22.2 and 26.13.0 with pnpm 11.28.8. Each successful run had 780 passed, zero failed and 12 environment skips. Node 26 first reproduced #107; a full unchanged-head rerun passed. No failure was waived. - Runtime CI, Sandbox image, and PR metadata passed on the reviewed head; no CI reruns were needed. Both internal review axes and the configured external reviewer completed without an unresolved release defect. The independent release exercise passed 120 selected tests plus direct synthetic CLI checks.
- After publication,
pnpm release:check https://raw.githubusercontent.com/lutzseverino/scriptorium/scriptorium-v4.0.0/schemas/factory-configuration.schema.jsonpassed: the public schema, supported and invalid fixtures, and both same-tag documentation links resolved and validated. - Additional documentation follow-up: #151 clarifies the version 3 factory-triage exception in the readiness guide.