chore(release): dev-loop 1.5.0 — per-role model selection - #65
Merged
Conversation
Bumps both version files. `.claude-plugin/plugin.json` is the one release.yml checks against the pushed tag; `.claude-plugin/marketplace.json` carries the same number for marketplace listings and is not enforced anywhere, so it drifts silently if bumped separately — they move together. Ships #63: worker model via --model / DEV_LOOP_WORKER_MODEL, the auditor pinned off `inherit`, and wiki-plan moved to the coordinator so the planning tier is independent of the implementing tier. Minor, not patch: new configuration surface, backward compatible (unset changes nothing). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump only — no behavior change. Ships #63.
What's in 1.5.0
Per-role model selection, so the three jobs that previously shared one model can each sit where they belong:
--model/DEV_LOOP_WORKER_MODELonorca-worker-start.sh,orca-spawn.sh,launch-session.sh. Unset omits the flag, so an upgrade changes nothing for existing users.inherit, so the self-grading guard never follows a cheaper worker down and inherits its blind spots.wiki-planmoved to the coordinator (Phase 3 step 2a); the worker adopts the plan via loop-implement's existing "a plan already exists" mode. The phase sequence,plan_ready,watch-status, the ready-set scheduler, and the loop-gate allowlist are all untouched.Why minor, not patch
New configuration surface, backward compatible: with nothing set, behavior is byte-identical to 1.4.2 (pinned by a boundary test per launch script).
Both version files move together
.claude-plugin/plugin.jsonis the onerelease.ymlchecks against the pushedv*tag — a mismatch fails the release..claude-plugin/marketplace.jsoncarries the same number for the marketplace listing and is not enforced anywhere, so bumping them separately lets it drift silently. Bumped in one commit for that reason.🤖 Generated with Claude Code