jpdev v0.5.0

jpdev v0.5.0

Surgical rounds (#18, pull request #19): a fix round or a carry no longer costs what a fresh build costs.

What it holds

• Worktrees with shared caches. jpdev codex run --worktree <base> makes a git worktree off a base clone and points the sandbox's Go, npm and XDG caches at <base>/.jpdev-shared/; node_modules is linked from the base when the lock files match, otherwise the run is told to install. jpdev worktree add|list|remove manage them; remove refuses a worktree with uncommitted or unpushed work unless --force.
• A small-fix mode. jpdev codex run --small tells the builder to run only the check-list steps its change touches and leaves the whole list to CI; after the run the wrapper refuses to commit when the diff touched a path under dev.json's handover.shared_paths or boundary_paths, or changed more than JPDEV_SMALL_MAX_LINES lines (default 80).
• Carries without an agent. templates/update-branches.yml, vendored by adopting repositories, updates every open pull request branch from the default branch on each push and labels carry needed on a conflict; jpdev carry --pr N merges the default branch into the branch, commits and pushes when nothing conflicts, and otherwise starts a Codex run from a generated carry brief (templates/carry-brief.md).
• Resuming a builder's thread. jpdev codex run --resume <thread> continues a previous Codex thread for the fix round that follows a review; every run records the thread id the CLI reports in .jpdev/output/thread. A builder stopped by a safeguard is still never resumed.
• The handover job in CI. templates/ci-check.yml gains a handover job: the boundary-path diff against the base must be additions only unless the pull request body says Boundary change: yes, and the manifest's handover.schema_probe command runs when set. The logic lives in lib/handover_check.sh.

What it does not hold

Running Codex itself in GitHub Actions; jpdev codex review (#13); the handover files swept by --add of a containing directory (#16); the identifier exemption in the word list (#12); the usage text on the recorded thread id (a wording row). The adopting repositories re-vendor the workflow, check.sh and the CI template after this release.