chore: prepare v0.3.0 release

[copyleftdev]

Cuts 0.3.0. Everything here is version metadata, changelog, and the regeneration the bump forces —
no behavior changes.

Why 0.3.0 and why now

main carries two breaking changes that reach nobody until a release exists, because tool schemas
and terminal causes ship inside the binary:

• MCP surface (#32, feat(mcp)!: pin the store and reject filesystem paths in tool arguments #33) — store and config
  are process arguments, kahea_invoke takes sealed handles rather than filesystem paths, undeclared
  arguments are rejected.
• kahea/k1 terminal cause (#34, fix(websocket): a close verdict outranks a failure to acknowledge it #35) — a
  close code the plan rejects is reported as expectation-failed even when the peer resets while it
  is acknowledged, instead of io-failure.

0.2.0 is what public scanning found, and it is still the newest artifact. One version for both breaks
is cheaper than a second contract change a release later.

What is in the diff

• Version bumped in lockstep across Cargo.toml, Cargo.lock, server.json,
  packaging/mcpb/manifest.json, both plugin manifests, and .claude-plugin/marketplace.json.
  scripts/validate-distribution.sh asserts all five JSON files equal the cargo version, so a
  partial bump fails the gate rather than shipping skewed metadata.
• Unreleased becomes 0.3.0 - 2026-08-13, with the terminal-cause break and the CI-flake work
  (#36, test: stop wall-clock flakes from blocking required checks #37) added.
• Goldens regenerated. RequestPlan.version is sealed material, so bumping the version moves
  every plan fingerprint and handle. fixtures/golden/create-invoice.plan.json and the two
  conformance goldens are regenerated for that reason alone, as is one pinned WebSocket fingerprint
  in kahea-plan. The plan in the golden is otherwise byte-identical: version, id, and
  fingerprint are the only fields that moved.

How it was verified

• scripts/gates.sh green end to end, including the distribution validator that cross-checks all six
  version references and the byte-stability checks that regenerate-and-compare the goldens.
• kahea describe reports 0.3.0.
• Full workspace suite green.

After merge

release.yml triggers on the tag, verifies the tag matches the workspace version, re-runs the gates,
builds Linux/macOS/Windows with SBOMs and provenance attestations, publishes the GitHub release, and
then publishes to the MCP Registry. That last step is public and not something to trigger by
accident, so the tag is deliberately not pushed here — git tag v0.3.0 && git push origin v0.3.0
when you want it to go out.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 113 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: e5614bb9-1340-4101-8dda-b2d63675533c

📥 Commits

Reviewing files that changed from the base of the PR and between 3862d8b and 52d1f26.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (11)

• .claude-plugin/marketplace.json
• CHANGELOG.md
• Cargo.toml
• crates/kahea-plan/src/lib.rs
• fixtures/golden/create-invoice.plan.json
• fixtures/golden/generator-baseline.conformance.json
• fixtures/golden/generator-surface.conformance.json
• packaging/mcpb/manifest.json
• plugins/kahea/.claude-plugin/plugin.json
• plugins/kahea/.codex-plugin/plugin.json
• server.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.}