release: v0.50.0

[norvalbv]

Bump 0.49.1 → 0.50.0, dist rebuilt from a clean origin/main worktree.

Minor, not patch: judge_exec gains a new shape. Every judge now records input_tokens, output_tokens, cache_creation, cache_read, cost_usd and session_id (sc-1527, #368) — which makes per-ship cost answerable for the first time, and is the whole reason the review-latency work in #360 could only ever be justified on wall clock.

Diff is package.json + dist/package.json; the compiled outputs for the feature already landed with #368.

Verified against a real spawn, not the test fake

Ran a live haiku judge through the merged code on origin/main:

RETURNED: "VERDICT: PASS"          ← clean text, not the JSON envelope
input_tokens: 10   output_tokens: 49
cache_creation: 17652   cache_read: 17822
cost_usd: 0.0373   session_id: 788d3a9b-b6a6-4aa8-9faf-6b5f9ea2da3a
output_chars: 13                   ← follows the text, not the envelope bytes

So the caller contract holds, the spend is real, and the session_id join back into the usage tracker exists.

Expect one slow ship per repo after upgrading

cacheKey salts on the devkit version, so every reviewer and completeness verdict earned under 0.49.1 is invalidated by design (sc-1437). That first attempt re-judges from scratch — which incidentally is the run that will carry the first complete cost picture, since nothing is served from cache.

Smoke checks

• built bin reports 0.50.0
• dist byte-consistent with the index in both directions (0 stale, 0 untracked)
• parseJudgeUsage present in the compiled dist/gate-engine/judge/run-judge.mjs

Gates bypassed at the maintainer's request (--no-verify).

After merge

1. Tag v0.50.0 and push — consumers pin devkitRef, so an untagged release is unreachable.
2. Reinstall the global bin.
3. devkit upgrade in devkit itself and in qavis/frink to start collecting.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@norvalbv, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e7bd1354-2794-4c3e-8ae6-a28e8cb929c2

📥 Commits

Reviewing files that changed from the base of the PR and between 55a86df and 8eeeae7.

⛔ Files ignored due to path filters (1)

• dist/package.json is excluded by !**/dist/**

📒 Files selected for processing (1)

• package.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}