Skip to content

Releases

Scriptorium v4.1.2

Choose a tag to compare

@lutzseverino lutzseverino released this 12 Nov 20:33
scriptorium-v4.1.2
f4db9ed

Compatible fix since Scriptorium v4.1.1.

  • Count factory-managed sandboxes by whether their agent has exited, independently of result publication and final run settlement. Exited runs awaiting publication or an ending no longer consume implement or provider capacity (#180, the fix for #170).
  • Restore sandbox capacity for retained exited work after upgrade or supported restart without editing records, deleting results, raising caps, clearing claims or creating replacement attempts. Late stop decisions cannot time out an already exited run. Publication, readiness, review and settlement retain their existing gates.
  • Keep status JSON version 1 and its counting: "non-ended-runs" marker; the marker denotes agent-exit occupancy, as documented in the release-pinned host guide.

No configuration migration is required: configuration versions 3 and 2 remain supported, and the sandbox image contract is unchanged. Live recovery acceptance remains separate in #179.

Known limits remain deferred: #174 reports a hold-resume launch-order test flake; #154 reports a capacity lifecycle test timeout waiting for run exit. These inherited test defects are not fixed by this release. Other existing compatibility and quota/backoff work remains tracked separately in #156 and #171.

Configuration: release-pinned guide. Sandbox images: release-pinned guide.

Release verification

  • Release PR: #182, merged at 2026-11-12T20:33:01Z.
  • Merge commit and annotated tag target: f4db9edb45cc74cbe6e19d1a89384ec8dee3bc40.
  • Reviewed head: f93981ced2f1f5ab5141bbb0241b4fb4f7fc4fec; the full released tree equals the reviewed tree.
  • Frozen installs and full validation passed on Node 24.22.2 and 26.13.1, each with 891 tests, 879 passes, zero failures and 12 local environment skips. Hosted Node 24/26 validation, aggregate Test, PR metadata and Sandbox image passed on the reviewed head, including Docker acceptance; no job rerun was needed.
  • Independent Standards review passed; Spec review passed after two release-note/body wording corrections. Configured review completed on the reviewed head with no findings.
  • Published at 2026-11-12T20:33:21Z. Remote annotated tag, ordinary release, public release list and latest endpoint verified.
  • Public pnpm release:check passed at 2026-11-12T20:33:35Z: the tag-pinned configuration schema, supported/invalid fixtures and both same-tag documentation links resolved and passed.

Scriptorium v4.1.1

Choose a tag to compare

@lutzseverino lutzseverino released this 12 Nov 14:52
scriptorium-v4.1.1
fdd4b5e

Compatible fixes and maintenance since Scriptorium v4.1.0.

  • Resume prepared triage publication when valid intake has no validator result, then wait for the matching source/revision notice before readiness. Recover interrupted evidence/readiness writes and keep per-run publication holds from blocking sibling results (#173; fixes #169).
  • Supply ps through the agent layer's procps package, including Debian slim bases; agent layer version 5 rebuilds affected sandbox image pairs (#159).
  • Declare required checks, test both supported babysit runtime contracts, and adopt Repo Canon v0.27.0 with Repository Standards CLI 11.0.1 (#163, #165, #166).

No configuration migration is required: configuration versions 3 and 2 remain supported. This publication performs no host installation or live recovery; that acceptance remains tracked in #172. Existing v3 compatibility (#156), status/capacity (#170), quota/backoff (#171), and the host launch-order test flake (#174) remain separate.

Configuration: release-pinned guide. Sandbox images: release-pinned guide.

Release verification

  • Release PR: #175.
  • Reviewed head: 5dc042f0b1dbadb6f7a34d4fb3883f39397dce62.
  • Merge commit and peeled annotated tag: fdd4b5eb6c5b0a8071eef1f7bde17029d345d1ee; the entire merge tree matched the reviewed head before tagging.
  • Local full validation passed on Node 24.22.2 and 26.13.1: 879 tests each, 867 passed, zero failed, 12 environment skips. Hosted both-major CI, including Docker acceptance, and required PR metadata/Test passed on the reviewed head. No CI reruns.
  • Independent Standards and Spec review passed with no findings. Configured Codex review completed on the reviewed head with no findings; no review threads remain.
  • The public release list and latest endpoint confirm an ordinary release, neither draft nor prerelease, published 2026-11-12T14:52:53Z.
  • Public pnpm release:check passed at 2026-11-12T14:53:05Z: release-pinned configuration schema, supported/invalid fixtures and both same-tag documentation links resolved successfully.

Scriptorium v4.1.0

Choose a tag to compare

@lutzseverino lutzseverino released this 10 Nov 19:10
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.

Scriptorium v4.0.0

Choose a tag to compare

@lutzseverino lutzseverino released this 09 Nov 03:47
scriptorium-v4.0.0
d744de1

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.json and .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

  1. Prepare a candidate host configuration with explicit models.effort (set "high" to retain the previous effort), and validate it with the candidate's read-only status command.
  2. 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.
  3. Before a v4 host serves a repository, move its inputs to .scriptorium/config.json and .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.
  4. 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 validate passed 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.json passed: 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.

Scriptorium v3.0.1

Choose a tag to compare

@lutzseverino lutzseverino released this 04 Nov 14:26
scriptorium-v3.0.1
5e7ecf2

Scriptorium v3.0.1 is a compatible patch over scriptorium-v3.0.0.

  • Fix release-hold reasons so they never name any of the run's own PRs, including runs owning several PRs (#102, #110). Merge eligibility is unchanged.
  • Include repository maintenance from the Repo Canon v0.22.0 adoption (#106) and domain documentation for future run kinds (#109). The future v4 pipeline is not implemented in this release.

No configuration-schema, dependency-pin or sandbox-contract changes; no migration is required from v3.0.0. Hosts on older majors still require the v3 migration.

Documentation: factory configuration, host usage.

Release verification:

  • Release PR: #111.
  • Squash merge: 5e7ecf2593cd534cfb9050a7385dbda71b5102f9.
  • Reviewed head: 107670846f80c249df5a73980f6ca308dc16b896; entire merged tree is identical.
  • Frozen install and full validation passed on Node.js 24.22.2 and 26.13.0 with pnpm 11.28.8 (580 tests each, 568 passed, 0 failed, 12 local environment skips). Both Node.js CI jobs, aggregate Test, PR metadata and Sandbox image passed. Configured review completed without findings.
  • Remote annotated tag 0ce6141df3d18b11f3a880357aa7d3216fffa873 peels to the exact merge commit.
  • Ordinary release verified: neither draft nor prerelease, visible in the release list and selected as latest.

Scriptorium v3.0.0

Choose a tag to compare

@lutzseverino lutzseverino released this 01 Nov 17:36
scriptorium-v3.0.0
3a74e2b

Scriptorium v3.0.0 is a breaking release from scriptorium-v2.3.0 in this repository.

  • Configuration version 2 names the skill and its arguments; provider adapters render the invocation (#96, #100).
  • The factory reads the validator's posted repo-canon/issue-contract-state/v1 result instead of interpreting contracts. contractResult.marker and contractResult.author are required. Repo Canon v0.21.0 publishes that format (#98, #103).
  • Optional labels.hold supports the repository-level factory:hold, pausing pickups and merge relaunches while existing runs settle (#95, #101).
  • Parents stay open until their blockers close (#99).
  • The package removes marked; Sandcastle 0.12.0 and Postern 1.3.0 remain pinned. Host configuration and sandbox image contracts are unchanged.

Impact

This release needs a deliberate host update. Version 1 factory configurations and version 2 configurations without contractResult are refused; issues without a current compatible approving validator result are held. There is no configuration compatibility layer.

Migration

  1. Plan a coordinated host and repository switch. The homelab updater supports only majors 1 and 2 and never installs a new major on its own. Publishing this release leaves the host on v2.x; a later, separate homelab change must admit major 3.
  2. Prepare each repository's configuration version 2: replace prompt with skill and arguments, remove {skillPrefix}, and add contractResult.marker and contractResult.author. Repo Canon values are repo-canon:issue-contract-state and github-actions[bot]. Ensure its validator publishes repo-canon/issue-contract-state/v1. Repo Canon adopters move to configuration version 2 through a later Repo Canon release carrying repo-canon#797; v0.21.0 supplies the result format but not that configuration migration. Older hosts refuse version 2 and pause those repositories during the switch.
  3. In that separate host change, install v3.0.0 and verify configuration acceptance, current approving results and resumed pickup. Scriptorium already has version 2 configuration, but its installed validator still posts the older unversioned result: its issues remain held after v3 installs until its Repo Canon update brings v1 results. No Repo Canon adoption is part of this release.

Factory configuration and migration · Host readiness · Release procedure · Repo Canon v0.21.0 result format

Release verification

  • Release PR: #104
  • Reviewed head: a8e7a4d9627518ad431cb708b18c9a3fe6e1a4c5; merge commit: 3a74e2b4126d041b9bdfabb23c70aef975c2f2e0.
  • The complete reviewed and merged trees are identical; merged manifest is 3.0.0 and lockfile pins match review.
  • Node.js 24.22.2 and 26.13.0 frozen installs and pnpm validate passed: each 578 tests, 566 passed, 0 failed, 12 skipped locally (Docker access and pinned Claude CLI unavailable). Both Node CI jobs, aggregate Test, PR metadata and Sandbox image passed. Configured review completed on the exact head with no findings; no review threads remained.
  • Remote annotated tag object 5db39bc23de98724b650fa251e6d7c41fa37e558 peels to the merge commit above.
  • GitHub release is published, neither draft nor prerelease, visible in the releases list and selected as latest.
  • Known validator-update gap remains tracked by #90. Host and adopter changes are separate follow-up work.

Scriptorium v2.3.0

Choose a tag to compare

@lutzseverino lutzseverino released this 31 Oct 17:06
scriptorium-v2.3.0
1f89927

Changes since scriptorium-v2.2.0

  • Preserve parent readiness across sub-issue links made by people authorized under the readiness policy (#91; implements #80).
  • Inspect complete link-addition history through runtime Postern 1.3.0. Every addition at or after readiness must have an authorized actor; unknown times and unauthorized, bot, excluded or unknown actors hold the parent. A later authorized link never hides an earlier unauthorized one.
  • Retain the latest-link-time fallback where complete history is unsupported, and retain body-edit and contract-revision readiness gates. Failed history reads do not grant readiness.

Compatibility and installation

This is a compatible capability release. Host configuration and factory configuration schema (version 1) remain unchanged, as does the sandbox image contract. No configuration migration is required. The runtime Postern pin advances from 1.0.0 to 1.3.0; the release-age exception names only that exact version.

See parent readiness and the release procedure.

Host installation is separate and requires a maintenance grant. This release run performs no installation or restart.

Release verification

  • Release PR: #92
  • Squash merge: 1f899278a1591d645df0c02ac8280426fca75aa2, merged through Repo Canon babysit after required checks passed and the configured reviewer completed on reviewed head 3ba5ce65b2d5a1e3a1a9911aa62139dcb2093299 without findings or unresolved threads.
  • Whole-tree comparison: PASS. Reviewed head and merge have identical tree 67aebea75e983b49265330c8c9e96aac9f71ecc5. Merge manifest reports 2.3.0; reviewed lockfile pins, including Postern 1.3.0 and Sandcastle 0.12.0, are preserved.
  • Remote annotated tag: scriptorium-v2.3.0, object 494bff13dacb0063fe2c13398510e31d88e0cd3c, peels to the exact squash merge above.
  • Publication: verified neither draft nor prerelease; visible in the repository's release list.
  • Validation on the unchanged reviewed head: frozen install and pnpm validate passed on Node.js 24.22.0 and 26.13.0 with pnpm 11.28.8 (563 passed, 0 failed, 12 Docker-dependent skips each locally). CI passed both supported-runtime jobs, aggregate Test, PR metadata and Sandbox image. Whole-change git diff --check passed.

Scriptorium v2.2.0

Choose a tag to compare

@lutzseverino lutzseverino released this 31 Oct 10:10
scriptorium-v2.2.0
72bb81c

Changes since scriptorium-v2.1.0

  • Relaunch stale factory PRs to recover merges (#84), resume factory-owned PRs and close completed issues (#85).
  • Maintain one comment per actionable hold reason and enforce an optional host model allowlist (#87; implements #74).
  • Hold factory merges while another open PR carries a repository's configured release-hold label (#88; implements #77).
  • Scope external-review policy guidance to repositories declaring that policy (#82).
  • Record the owner's standing delegation for patch and minor releases (#81).

Host installation and configuration

Installation is separate and requires a maintenance grant. Existing configurations remain valid: the factory schema stays at version 1, and the sandbox image contract and dependency pins are unchanged.

To enable model restrictions, set optional models.allowed in the host configuration to unique provider/model names without @effort. Include the default, retry and every permitted label-selected model, then restart the host. Omitting the list preserves unrestricted selection. A disallowed model holds new, retried, interrupted, paused and merge-relaunched work rather than substituting another model. See host configuration.

To enable release holds, configure each served repository's optional labels.releaseHold (for example, factory:release-hold), create that repository-owned label, and apply it to release PRs until they merge or close. Scriptorium's current repository configuration omits this optional key. This release provides the host side; the mid-run merge guard additionally needs the companion Repo Canon #742 babysit change. See repository configuration and release holds and release procedure.

Publication verification

  • Release PR: #89, squash-merged through babysit.
  • Merge commit: 72bb81c93b476e76760177df834ff928b744ae1b.
  • Reviewed head: ce8845d5563ccdaa697dd83f6fb3ec942f61f3d4; whole-tree diff against the merge passed (tree 416b4ece1416305d4fc8a2b19d13005a330baa73). Manifest version is 2.2.0; reviewed dependency pins match.
  • Frozen install and pnpm validate passed on Node.js 24.22.0 and 26.13.0 with pnpm 11.28.8: 556 tests passed, 0 failed, 12 skipped locally on each major (Docker unavailable). Upstream digest verification passed.
  • PR CI passed: both Node.js runtime jobs, aggregate Test, PR metadata and Sandbox image. Configured review completed on the exact head with no findings; no unresolved review threads.
  • Remote annotated tag object: 1b84e50a2794d5a19bac98abcdd46501eb0578d5; it peels to the merge commit above.
  • GitHub Release is public, neither draft nor prerelease, appears in the repository release list, and was published by lutzseverino under the standing minor-release delegation.
  • Host installation was not performed; it requires a separate maintenance grant.

Scriptorium v2.1.0

Choose a tag to compare

@lutzseverino lutzseverino released this 30 Oct 20:13
scriptorium-v2.1.0
eabd421

Scriptorium v2.1.0 is a compatible minor release from scriptorium-v2.0.0.

  • Add opt-in storage admission before new sandbox image builds, with explicit local store mappings, reserve/recovery thresholds, persistent holds and private diagnostics. Existing images remain reusable and running work can finish. Add an independent byte target for the dedicated factory builder cache; shared daemon cache is left to the operator (#72).
  • Bind pickup, retries and readiness-dependent parent handling to the current reviewed Agent Brief revision, holding safely when approval or comment-history evidence is missing (#69).
  • Clear active factory labels from closed issues, including claims with an open PR (#68).
  • Assess outgoing protected paths against the refreshed default branch, avoiding false failures from changes already delivered there (#67).
  • Make skip-label launch tests independent of arrival order and support both babysit adoption interfaces (#61, #64).
  • Adopt Repo Canon v0.19.0 and v0.19.1, including trusted review configuration, updated workflow guidance and standards tooling (#65, #71).

No mandatory migration is required from v2.0.0. Existing host configurations keep their builder and behavior. Storage admission and cache byte limits are opt-in; explicitly verify native local store and cache filesystem mappings before enabling them. Admission coordinates one host process and cannot reserve disk space against external workloads.

See the host guide and storage admission reference, sandbox image guide, and release procedure.

Publication verification

  • Release PR: #73, squash-merged after all checks passed and external review completed with no findings.
  • Merge commit: eabd42101c67f0d0305726898f2260e8003b9261.
  • Reviewed head: 3b8daadd9bbd88ecd4119b06e7c949adfdc349ee. Full-tree comparison passed; both trees are b23dd2121d37c2eb0f12d9b242748a4f829f602e.
  • Manifest at the merge commit declares 2.1.0; regenerated lockfile retains the reviewed dependency pins.
  • Remote annotated tag object: 82daf272da996b05dfac83937295ae85ee4c9ebe, peeling to the exact merge commit above.
  • GitHub release is neither draft nor prerelease, appears in the release list, and is the latest release.
  • Both GitHub-generated source archives (tarball and zipball) downloaded successfully; all 395 file/symlink entries in each match the tagged Git archive. No separate binary assets are published by this source-only release procedure.
  • Local pnpm validate passed on Node.js 24.22.0 and 26.13.0: 467 passed, 12 capability skips, zero failures per major. CI passed on both supported majors with Docker: 476 passed, 3 skips, zero failures each. Required PR metadata and aggregate Test, plus Sandbox image, passed.

Scriptorium v2.0.0

Choose a tag to compare

@lutzseverino lutzseverino released this 26 Oct 13:39
scriptorium-v2.0.0
008d359

Scriptorium 2.0.0 installs and develops with pnpm 11 (the package pins 11.28.8) instead of npm. The toolchain also moves to TypeScript 7, oxlint and Prettier, and a single pnpm validate runs every check.

When an ended or orphaned run keeps its claim because its pull request is still open, the factory now posts one notice saying so, instead of holding the issue silently. Repositories can customize the wording with the optional comments.awaitingMerge template.

The sandbox image and the host installation keep pnpm's content store outside the checkout, so runs never leave a .pnpm-store/ in the working tree.

Impact

Host installation changes. A release tree has pnpm-lock.yaml and no package-lock.json, so an installer that runs npm ci can't prepare it. The host configuration schema and the factory configuration schema (version 1) are unchanged. Existing repository configurations keep loading, and comments.awaitingMerge is optional.

Migration

In this order:

  1. Provide pnpm 11.28.8 on the host's operational PATH.
  2. Install production dependencies with pnpm install --prod --frozen-lockfile --ignore-scripts, with a writable store directory outside the release tree.
  3. Let the updater admit the 2.x stream deliberately; hosts stay on their pinned major otherwise.
  4. Only then let it take 2.0.0. Keep the retained 1.x tree for rollback.

See the host guide and the factory configuration reference.

Verification

Release commit 008d3594c249e74b4fa8b21488b6bb124c602228, from release pull request #59 (reviewed head 69aadecb2d0a1e502af36d8bbe8201b17424a4fd; the trees are identical). The annotated tag scriptorium-v2.0.0 peels to the release commit. The release is neither a draft nor a prerelease and appears in the release list. Required CI passed on Node.js 24 and 26, along with the sandbox image and PR metadata checks, and Codex found no issues. Node.js 24's test job needed re-runs for a missing runner Docker daemon and an order-dependent test, tracked as #60.