Repository navigation
Prepare judgment-pack-devkit v0.14.0 - #76
Conversation
Signed-off-by: kikashy <kikashy@hotmail.com>
|
Independent complete-release review of judgment-pack-devkit v0.14.0 and PR #76. Release range: Reviewer: OpenAI / Findings: none. Reviewed the complete release diff against its contracts and release notes, applicable instructions, operating policy and release procedure. Reused the #74 clean-room security evidence and independent #72, #75 and #73 review records. The changes preserve admission, wrapper controls and publication gates; the notes accurately state replay, RSS-guard and rollout limitations. PR #76 contains only the version, five headers and release notes. Versioned source copies and generated instructions match. The candidate archive identifies the reviewed head, and all 59 packaged regular files match its contents. Package smoke evidence reports Validation reused:
Remaining gates: merge, successful main CI at the merged commit, signed annotated tag, release-evidence admission, rebuilding the final archive from that commit, checksum and provenance verification, protected publication approval, and post-publication asset verification. This establishes source-candidate review completion. Published artifacts are not yet available. No tracked files or Git state changed; no publishing performed. Disposition:
|
|
🎉 Thank you for your contribution to Judgment Pack! If you’d like another task, choose a path that interests you: |
|
Published judgment-pack-devkit v0.14.0.
Before publication, the draft notes matched the tagged source, the exact two assets matched their API digests, the tarball matched a reproducible archive of the released commit byte-for-byte, and both attestations verified against the repository, release workflow, tag ref and exact source digest. The existing release environment was approved under the maintainer's explicit release authorization after those checks. After publication, release
Disposition: all release gates complete. Consumer adoption remains separately authorized work; no consumer copies changed. |
Milestone:
v0.14.0. Release preparation for the completed #70 → #65 → #69 → #71 batch, merged through #74, #72, #75 and #73.Change
Set the kit version and all five version headers to
0.14.0, and add release notes describing the changes, evidence and operating limits. The notes preserve the distinction between live API plan replay and hosted execution, cooperative RSS guarding and containment, and kit publication and consumer adoption.No product logic, consumer repository or release workflow changes.
Acceptance mapping
Checks
Clean candidate:
eaafb806a06f20e0e1ce48ed891f5a5a9c8f92bf; no uncommitted diff. Executedscripts/dev/check.sh --allonce under the configured shared lock. Only the machine-local interpreter path is omitted:The archived candidate's
bin/jpdev --versionandbin/jpdev envpassed. Its archive is preparation evidence; final published bytes were rebuilt from and verified against the signed tag's commit.Review and release status
Merged as
9f555498a9e4c35d426ca1ce45352abf3363cbb3, with tree equality to the reviewed candidate verified. Exact-head CI41318039623passed. The independent complete-release review reports no findings and identifies the same-vendor reviewer and model. Main CI41318438052passed. Release v0.14.0 is published, immutable and latest. Release workflow41318695912passed; signed tag, draft approval, checksums, reproducible archive, both provenance attestations and post-publication asset verification are complete. No consumer rollout.