Skip to content

Scriptorium v4.1.0

Choose a tag to compare

@lutzseverino lutzseverino released this 10 Nov 19:10
· 25 commits to main since this release
scriptorium-v4.1.0
837697d

Scriptorium v4.1.0 is a compatible capability release after scriptorium-v4.0.0.

  • Publish and consume body-backed triage contracts (#148, PR #157): read Repo Canon v1/v2 decisions, preserve authenticated original intake, publish bodies with separate immutable attestations, and recover publication checkpoints across restart. Trusted repository mode and cutoff records govern activation; installing this bridge alone retains legacy/prepared behavior.
  • Validate configured image-storage paths before admission (#153, PR #155), report inaccessible or invalid paths at configuration load, and distinguish measurement failures from storage pressure before reclamation.
  • Document model guidance (#126).
  • Pin the configuration schema, same-tag documentation links and configuration examples to this release. Dependency pins are unchanged.

Configuration versions 3 and 2 remain supported; the host/factory schema versions and sandbox image contract do not change. Existing v4 hosts need no configuration migration for this compatible release. Before upgrading a v3 host, follow the v4 host migration, including canonical .scriptorium/ repository inputs, explicit host models.effort, and token-command permissions arguments. Coordinate the repository-input adoption with the host upgrade.

For body-contract rollout, install the bridge in legacy/prepared mode, adopt compatible prepared Canon, freeze and drain triage publication, capture the trusted inventory and immutable cutoff, then reevaluate and confirm v2 decisions before unfreezing. Keep publication held if an intermediate delivery lane cannot operate. See body-backed triage contracts. Unknown protocol formats hold; Seams-wrapper compatibility remains tracked in #156.

Publication does not install or activate this release on any host or adopter.

Release verification

  • Release PR: #158.
  • Reviewed head: d01d756287aaddacee912de2d659fc56ff0c7b39.
  • Merge commit: 837697dff1711ef12781636aed544d3de6d4e5ea.
  • Annotated tag scriptorium-v4.1.0: object d78d7b74ddc4202a2cdd0f86e33dea8079daa8f9, remote peeled target 837697dff1711ef12781636aed544d3de6d4e5ea.
  • Complete reviewed-head/merge tree comparison passed before tagging. Manifest is 4.1.0 and all reviewed dependency pins are unchanged.
  • Full local validation passed on Node 24.22.2 and 26.13.0 with pnpm 11.28.8: each 835 tests, 823 passed, zero failed, twelve skipped (nine Docker tests without local Docker and three unavailable pinned Claude CLI tests).
  • Runtime CI and required Test, final PR metadata, and Sandbox image passed on the reviewed head, including Docker tests in CI. No CI reruns were needed.
  • Independent Standards and Spec release review passed with zero findings. Configured current-head review completed without findings; a separate paginated review-thread read returned zero threads.
  • Published at 2026-11-10T19:10:13Z. Remote refs, release view, release-list visibility and latest lookup confirm an annotated tag at the merge and an ordinary release, neither draft nor prerelease.
  • Post-publication pnpm release:check https://raw.githubusercontent.com/lutzseverino/scriptorium/scriptorium-v4.1.0/schemas/factory-configuration.schema.json passed from the released checkout at 19:10:33Z: public schema, supported/invalid fixtures and both same-tag documentation links resolve correctly.
  • No new finding was observed. Known Seams-wrapper limitation #156 remains outside this compatible bridge release.