chore(release): stamp 0.0.14 across the workspace; pin the versions together

[ulmentflam]

Prep for the v0.0.14 release.

_version.py said 0.0.14 while all eight pyproject.toml files said 0.0.12. nightly version reported one number and anything built from the workspace was stamped another, which makes a bug report's "which version?" unanswerable.

The drift was quiet by construction: a source install reads _version.py, a wheel reads pyproject.toml, and neither can see the other disagreeing — so nothing caught it for two versions.

This bumps the eight files to match and adds test_version_consistency.py to stop it recurring. The test is parametrized over every pyproject.toml the workspace actually contains, so a new host package is covered the day it lands rather than the day someone remembers to add it, and it asserts the layout it depends on rather than silently passing over an empty glob.

Mutation-verified: reverting one host package to 0.0.12 fails with the offending path named.

1177 tests pass (10 new). nightly verify clean on all five checks.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 046bc9f0-39b7-497c-8b42-9b0f4d29bd15

📥 Commits

Reviewing files that changed from the base of the PR and between f91a41f and f6b81f5.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (9)

• packages/nightly-core/pyproject.toml
• packages/nightly-core/tests/test_version_consistency.py
• packages/nightly-host-antigravity/pyproject.toml
• packages/nightly-host-claude/pyproject.toml
• packages/nightly-host-codex/pyproject.toml
• packages/nightly-host-cursor/pyproject.toml
• packages/nightly-host-gemini/pyproject.toml
• packages/nightly-host-opencode/pyproject.toml
• pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch nightly/release-0.0.14

---

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.}