[kikashy]

Milestone: v0.15.0. This prepares the release of #79, which merged through #80 as c0b75d39201008560c2a4f3ec86a7079791ea6d7.

Change

Release preparation, the same shape as #76:

• JPDEV_VERSION in lib/common.sh is now 0.15.0;

• line 2 of all five versioned script headers now names v0.15.0: templates/check.sh, scripts/dev/check.sh, scripts/dev/handover_check.sh, scripts/dev/changed_checks.py and scripts/dev/release_evidence.py. This is every file in the tree that carries a from judgment-pack-devkit vX.Y.Z line;

• new docs/releases/v0.15.0.md, covering:

  • the release-os compare mode and what it holds;
  • what the mode gives up;
  • that release-runner and pins decisions are unchanged;
  • its operating limits and the review record.

  Earlier release notes do not mention milestone moves, so these notes leave out Reuse a pull request run's evidence when the merged tree under test is identical #77 and Merge queue: make the release evidence gate understand queue commits #78. The repository has no changelog, and the README carries no version.

The three LOW documentation findings from #80's clean-room review (record) are fixed in docs/ci-evidence.md:

• F1. A release-os job of another image name, OS or architecture refuses identity-unexpected, in the identity checks every job passes first. Only another OS-release digest, a tool that is not its pin, or another tool set refuses runtime-identity. This is corrected in the runner identity comparison bullet, the "OS release and platform" bullet and the "A difference is a refusal, not a drift" paragraph.
• F2. The release-os group rule (identity-changed) is now described as a backstop. Through verify, the per-job checks refuse a differing job first, so identity-changed is not the code a release normally reports for this mode.
• F3. The release_runner record is now described in full: image name and version, OS, architecture, and the OS-release digest.

The gate's code and tests are unchanged from #80.

Acceptance mapping

Requirement	Implementation	Verification	Remaining gate
Matching release identity	JPDEV_VERSION and the five versioned script headers	Full check list (the version-line and vendored-copy cases in tests/run.sh); bin/jpdev --version prints jpdev 0.15.0	Exact-head CI
Complete release scope	docs/releases/v0.15.0.md covers the milestone's one change (#79/#80)	git log v0.14.0..c0b75d3 holds only #80	Release-diff review
Review findings closed	F1–F3 in docs/ci-evidence.md	Each changed sentence read against check_identity, check_runtime, identity_group and verify	Release-diff review
Published verified artifact	Existing signed-tag and protected release workflow	Not yet run	Merge, main CI, signed tag, release workflow

Checks

Candidate fdbb6e3468d382309da153ddee477dee061012bc, no uncommitted diff, Python 3.12.11, with a soft 4 GB address-space cap and a resolved TMPDIR. scripts/dev/check.sh was run once over the working tree. The new notes file was still untracked during that run, so I staged it and reran --only diff-check,local-paths, and both passed. The machine-local interpreter path is omitted:

== 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     duplication              0s, python [interpreter path omitted] (Python 3.12.11)
    duplication: no duplicate block (at least 100 tokens over at least 10 lines, 23 files of python, shell)
PASS     json                     0s, python [interpreter path omitted] (Python 3.12.11)
PASS     shellcheck               4s
    shellcheck: clean
PASS     tests                    109s
    449 passed, 0 failed
== 8 passed, 0 failed, 0 skipped, 0 not run ==

CI owns the exact-head run. Not done here: the release-diff review, merge, tag and publication. No consumer is re-vendored.

🤖 Generated with Claude Code

[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