[kikashy]

Prepare v0.7.0 for the issue #30 cleanup change merged in PR #31. Synchronize the kit version and vendored script headers, and add the release notes covering ownership seals, conservative deletion checks, transcript thresholds, scratch-local TMPDIR and operating limits.

Checks

The required full local checklist passed:

== check summary (dev.json) ==
PASS     diff-check               0s
PASS     local-paths              0s
PASS     agent-docs               0s
    sync-agent-docs: CLAUDE.md matches AGENTS.md
    sync-agent-docs: CLAUDE.md matches AGENTS.md
PASS     bash-n                   0s
    bash -n: every script parses
PASS     json                     0s, python <home>/.pyenv/versions/3.8.20/bin/python3 (Python 3.8.20)
    parsed 6 JSON documents
PASS     shellcheck               4s
    shellcheck: clean
PASS     tests                    58s
    420 passed, 0 failed
== 7 passed, 0 failed, 0 skipped, 0 not run ==

The interpreter path is redacted. Version and vendored-source parity checks pass. Existing implementation evidence is recorded in PR #31.

Release review

CI run 39961375337 passes for c4fd4cbd37d11c5fe4456054c642f3643de9ebf4; lint, tests and DCO are green. The original independent reviewer completed the full v0.6.0-to-v0.7.0 review after green CI, with no findings. One package build and four unpacked CLI probes passed. Verbatim release review and dispositions. The reviewer retained its explicit gpt-6.1-sol/high launch under the user-authorized same-vendor exception. The protected release approval remains in place, and release immutability is enabled.

Every commit is signed off. A Codex session prepared this change.

[kikashy]

v0.7.0 release review

Preparation PR: #32

Reviewed candidate: c4fd4cbd37d11c5fe4456054c642f3643de9ebf4.

Complete release base: v0.6.0, commit 8993f8448337d7f7fa6a2f4ed8a0f0b197a492b7.

Ready for the normal protected release workflow. No release findings or unresolved code-review decisions. Original findings R1, R2 and R3 remain fixed. Signing, merge/tag ancestry, the protected release approval, published artifact attestations and installation verification remain the coordinator's subsequent release steps.

This is the required complete release review, reusing the original independent clean-room review and targeted reread. The reviewer retained its explicit gpt-6.1-sol/high launch because the release introduces a deletion boundary. The user's temporary same-vendor exception applies; this is not cross-vendor compliance.

Scope and conclusions

Assessed the complete change set since v0.6.0 against the issue, cleanup policy, CLI documentation, release notes and docs/releasing.md, combining the prior full implementation review with the fix reread and release preparation diff. The release contains one decision line: explicit cleanup plus scratch-contained builder temporary files and their supporting tests/documentation. No unrelated implementation changes were found.

Verified directly against the retained clean fix checkout that every tracked implementation/test/documentation file remains identical to reviewed head eea02d969338de33605d700f26b5e78b1dd4ec81, except the expected four version/header substitutions and new release notes. The release clone does not contain that old unmerged commit object, so the comparison used the retained checkout's tracked-file contents without fetching or changing Git metadata. tree-comparison.json records the exact five changed paths. The preparation diff from merged issue30 head confirms the same scope.

The release notes agree with the assessed contracts: no implicit cleanup roots, explicit session enrollment and disposal inventories, seven-day age default, inclusive transcript-only 10 MiB logical-byte floor, keep exclusions, Git/publication/PR verification, process and filesystem refusals, cache/scratch eligibility throughout removal, builder TMPDIR placement and mutation-copy exclusions. The notes state the operating limits: unmarked historical roots cannot be adopted, complete initial Linux host process/mount/root visibility is required, ambient Git configuration is disabled, and removal is not transactional or isolated from a malicious same-user process.

Version 0.7.0, both versioned script headers, template/vendored check-script identity, and the versioned handover-script body agree. Packaging includes the new lib/clean.py, updated CLI, policy, brief and release notes; the installed-layout CLI can locate and execute its cleanup module.

Evidence

• Exact-candidate CI run 39961375337: completed SUCCESS.
• Supplied final checklist: 7 passed, 0 failed, including 420 repository tests passed, 0 failed.
• Reused prior 67-test focused cleanup evidence and independently verified safeguards: original 43 cleanup + 4 shell mutations caught, followed by 18 fix/threshold + 1 final-directory mutation caught. The associated implementation is unchanged, so no broad suite or unchanged mutation campaign was repeated.
• Built the release package once with the workflow's git archive path list and gzip -n -9; verified its checksum, safe prefix, required source contents and 48 archive members.
• Unpacked-package probes passed: jpdev --version reports jpdev 0.7.0; jpdev env exits 0; no-root jpdev clean reports zero candidates/removals/refusals in dry-run mode; cleanup help exposes --min-transcript-bytes and its 10485760 default.

Local package for the reviewed preparation commit:

f14b44db7f2a35b18f0a792536393577331942204b039ad27844b07c005c3572  judgment-pack-devkit-0.7.0.tgz

This digest identifies the local package of the reviewed candidate, not a future published artifact. If the final tagged merge commit differs, the coordinator must verify the release's own digest and provenance at that commit; archive timestamps can change even when the source tree matches. Detailed results are in package-results.json, tree-comparison.json, checksums.txt and the four package-probe logs beside this report.

Limits and operational stop

No production host-wide deletion or real GitHub PR/network probe was added during release review. The prior disposable deletion probes used the explicit process-evidence fixture seam. Release workflow protection, signing credentials and published attestations were not exercised or altered by this reviewer.

The coordinator reported that operational cleanup's dry run refused the session root for missing enrollment. That refusal remains respected: no override, historical enrollment or existing-data deletion was attempted as part of this review. Release readiness does not authorize bypassing that cleanup decision.

The release-review checkout remains clean at the exact reviewed HEAD. All generated files and package contents are confined to new release-review scratch. No checkout mutation, commit, push, posting, merge, tagging, release publication, installation or cleanup of preexisting data was performed. The original review and reread reports are preserved. Release review is complete.

Dispositions

Finding	Disposition
Release review	No findings; proceed through the existing protected workflow.
Prior R1, R2 and R3	Remain resolved as recorded in PR #31.
Operational cleanup refusal	Respected; unmarked session data retained.

Release prerequisites verified by the coordinator: the existing release environment has a required maintainer reviewer; repository release immutability is now enabled as required by docs/releasing.md.

[github-actions]

🎉 Thank you for your contribution to Judgment Pack!

If you’d like another task, choose a path that interests you:

• Go runtime
• Judgment desk
• Gateway and provenance
• Python and evaluator experiments
• Specification and documentation
• Agent harness and adapters

[kikashy]

v0.7.0 release and installation record

Published release: https://github.com/Judgment-Pack/judgment-pack-devkit/releases/tag/v0.7.0

The signed annotated tag v0.7.0 names main commit d0c0a0152b8a601bde80b0b5a4f9d3bd481edc1f. Its tree matches reviewed release-preparation head c4fd4cbd37d11c5fe4456054c642f3643de9ebf4. This follows implementation PR #31 for issue #30 and release preparation PR #32.

The independent release review and dispositions are recorded verbatim at #32 (comment). The original clean-room review used explicit gpt-6.1-sol/high, with the same reviewer assessing fixes and the complete release diff. This used the user's temporary same-vendor exception; it is not cross-vendor compliance. Original findings R1, R2 and R3 are fixed, and the release review found no unresolved code decisions.

Release workflow https://github.com/Judgment-Pack/judgment-pack-devkit/actions/runs/39962449641 completed successfully, including publication through the existing maintainer approval gate and the final published-asset digest check. Repository release immutability was enabled as required by the release policy. Release ID 421884823 is published and immutable; its title, notes and exactly two assets match the verified draft.

Verification completed before installation:

• Signed annotated tag signature verified; tagged commit is on main.
• Each downloaded asset's attestation verified for repository Judgment-Pack/judgment-pack-devkit, signer workflow .github/workflows/release.yml, source ref refs/tags/v0.7.0, and the exact tagged commit.
• The attested checksum file verified the downloaded tarball.
• A reproduction from the tagged source matches the tarball byte-for-byte.
• Published asset identities and digests match those verified before approval.

Published SHA-256 digests:

7563c4ba7d2e02fa0c247fac755d98b1a9075c68c2a515aaa542e52d7b208976  judgment-pack-devkit-0.7.0.tgz
f0b04904c85c289487b8772dd658d8d88bb6699368d43dc8d86cc47376853680  checksums.txt

The verified package was installed in a separate versioned directory under <home>/.local/share/judgment-pack/. The existing <home>/.local/bin/jpdev launcher was atomically changed to that installation after checking its prior target. command -v jpdev resolves to that launcher and jpdev --version prints jpdev 0.7.0. The previous installation remains intact. The installed no-root cleanup probe reports zero candidates, removals or refusals in dry-run mode.

Operational cleanup stopped at the dry run for this session's scratch: unmarked root; no ownership/disposal evidence. It reported zero candidates and zero removals. The root predates enrollment, and historical adoption is forbidden. No override, historical enrollment or existing-session-data deletion was performed. Other repository lanes and their scratch were left untouched.

Checks (the completed local checklist; no repeated broad run):

== check summary (dev.json) ==
PASS     diff-check               0s
PASS     local-paths              0s
PASS     agent-docs               0s
    sync-agent-docs: CLAUDE.md matches AGENTS.md
    sync-agent-docs: CLAUDE.md matches AGENTS.md
PASS     bash-n                   0s
    bash -n: every script parses
PASS     json                     0s, python <home>/.pyenv/versions/3.8.20/bin/python3 (Python 3.8.20)
    parsed 6 JSON documents
PASS     shellcheck               4s
    shellcheck: clean
PASS     tests                    58s
    420 passed, 0 failed
== 7 passed, 0 failed, 0 skipped, 0 not run ==

Prior focused evidence remains applicable: 67 cleanup tests; 43 cleanup and 4 shell mutations caught; 18 fix/threshold mutations and the independent final-directory mutation caught. CI passed for implementation, release preparation and the tagged release. Review records retain the individual findings and dispositions.

Item	Disposition
Independent review R1, R2, R3	Fixed and verified before merge; no open release findings.
Release provenance, publication and installation	Verified and complete.
Operational cleanup	Refused; scratch retained, zero existing-data removals. No bypass.