[flyingrobots]

Outcome

Prepare @git-stunts/git-cas v7.1.0 from merged reservation implementation 4782052. Package, JSR and runtime version metadata agree; release notes describe admission, irreversible arming, pinned evidence, bounded inspection and the limits of the guarantee. Current publication identity is separated from historical v6.5.11 evidence, and the reservation cycle retrospective records the maintainer-directed review override honestly.

Refs #162. Publication and the fresh registry consumer keep that issue open after this PR merges.

Validation

The first guarded Docker candidate run caught version-constant drift, an unpackaged documentation link, and a stale latest-release assertion. Commit 362ae05 repairs them. All 14 release checklist steps now have passing evidence on that head across guarded Docker phases; see the detailed verification comment for counts, artifact identities and the failed combined-worker Deno phase superseded for its required check by a fresh isolated run. No tag, npm publication, or WARP adoption is claimed by this PR.

No reservation protocol or dependency range change is included. The runtime package-version constant advances to 7.1.0, including producer-version metadata on newly stored manifests.

[coderabbitai]

Caution

Review failed

The pull request is closed.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[flyingrobots]

Release candidate verification at 362ae05e3d0bbd3ce48fe215490aa439adb732c9

All 14 release checklist steps have passing evidence across the guarded COPY-only phases on identical complete copied source. Unit observations: Node 2,407 passed/3 skipped; Bun launcher 2,407/3; Deno 2,398/12. Integration: 351 passed per runtime. Total: 8,265 passing observations and 18 existing skips. Lint, the three maintained examples, public/schema/reservation declarations, build stamp, npm pack inventory and JSR dry-run pass. A fresh installed local tarball passes the public reservation lifecycle/refusal/reopen/GC consumer in both Git formats. Production audit reports zero findings.

The combined worker phase is not a passing run: after the first five suites passed, Deno integration encountered subprocess-start failures (203 failed, 14 passed, 134 skipped). The same source's isolated Deno integration passed all 351. Its cgroup PID high-water was 272/512 with zero limit events; the failed phase did not retain PID counters, so no exact root cause is claimed. Final merged-main verification will use separate runtime phases in the same reusable worker, matching the ordinary release workflow's isolated-runtime posture. The failed logs and receipts remain retained.

Candidate tarball: 848,292 bytes; SHA-256 1c46966055e3f62f6a23ee26bff8f39f91186c443dc8e46a1d51c2e98ec8bb90; SHA-512 integrity sha512-jtzKYiynx/SbmEBg73RkXwxy7EMwTqHc0nUy+s2h5Vu/0MsBSJvrgbjG/+4Ws7TZ5wnxoZ2K71C3Xv8nA94nXw==. This is the locally built candidate; publication may produce different build-timestamp bytes and must be identified separately.

Resource limits were 4 CPU, 8 GiB memory, 512 PIDs, read-only root and 3 GiB data tmpfs with bounded auxiliary tmpfs/logs. Both complete source snapshots agree. No dependency range or reservation protocol changed during release preparation. Current-head hosted CI and merge disposition remain separate from these local results. No tag or registry artifact has been published yet.

[flyingrobots]

Following the maintainer's instruction to admin-merge the validated work, merge this release preparation at exact head 362ae05e3d0bbd3ce48fe215490aa439adb732c9. All five current hosted validation jobs pass, all release checklist steps have passing scoped local evidence as recorded above, and the fully paginated snapshot has no submitted reviews, inline threads or review requests. CodeRabbit began processing after this PR became ready; it has not submitted a review. The earlier skipped status is not approval. The maintainer-directed admin instruction is the merge authorization. Any concrete feedback arriving during merged-main validation will be reconciled before tagging.

The final merged-main release checklist, immutable signed tag, publication workflow and fresh registry consumer still follow this merge. No publication is claimed here.