Skip to content

jpdev v0.3.0

Choose a tag to compare

@github-actions github-actions released this 21 Oct 00:40
· 24 commits to main since this release
4ba11cf

jpdev v0.3.0

The third release of the development kit: Codex CLI sessions run from the same briefs as Claude sessions, and the push form is one command.

What it holds

  • jpdev codex run (#9): runs a Codex CLI build from a brief with the model and effort always explicit, in a workspace-write sandbox with network access, stdin closed, the transcript logged; after Codex returns, the wrapper stages the tracked changes (and only the paths named with --add), commits with the DCO sign-off from Codex's msg.txt (adding the Co-Authored-By: Codex trailer where missing), pushes with the credential-helper form, and opens the pull request from pr.md; --no-commit, --no-push, --no-pr stop earlier; a clone on main is refused. Found on the first real run: Codex's sandbox keeps .git read-only, so the git part is the wrapper's.
  • jpdev codex check-brief (#9): refuses a brief that carries a word from the kit's list (extendable through JPDEV_CODEX_WORDS) and suggests a neutral phrasing; a term split across lines or hyphenated is matched too (from the review). jpdev codex brief-template prints the brief shape Codex expects.
  • jpdev push [branch] (#6): the credential-helper push form in one command, refusing every force form; templates/AGENTS.md and CLAUDE.md state the form and name the command (adopted repositories re-sync their agent docs).
  • -mod=readonly (#7): a Go step can no longer rewrite go.mod; a kit test holds go.mod byte-identical across a step.
  • The policy (docs/policy.md): the cross-vendor rule: Codex builds non-boundary issues from accepted designs and briefs and Claude reviews them; Claude builds boundary decisions and Codex reviews them when its quota allows.

Adopting repositories

Re-vendor scripts/dev/check.sh from templates/check.sh at this tag and re-sync AGENTS.md/CLAUDE.md from templates/AGENTS.md so the push form is stated.

Installing and verifying

Download the tarball and checksums.txt from this release, check the digest, and verify both attestations as docs/releasing.md describes before linking bin/jpdev into your PATH.