chore(release): cut v0.2.2

[div0rce]

Release v0.2.2

Finalizes the v0.2.2 changelog and flips the release anchors. CMakeLists is already at 0.2.2.

v0.2.2 bundles, on top of v0.2.1:

• Hardening + perf wave (perf: clean high-density flamegraph (fp build, profile workload, no [unknown]) + engine event-buffer reuse #135–perf(flamegraph): regenerate artifact after round-2 fixes and index load-factor win #146): decoder enum-domain rejection, network/CLI hardening, a real UBSan abort gate, OCaml diff_report robustness, and two measured order-book perf wins (try_emplace, index load-factor cap).
• Documentation overhaul (docs: v0.2.2 overhaul — refresh every stale doc and provenance artifact #147, docs: rebuild the README from scratch (perf-first, reimagined, no emdashes) #149): every doc/artifact refreshed; README rebuilt to lead with the numbers and flamegraph.
• Performance-evidence report (docs: PERFORMANCE.md — before/after perf evidence for the v0.2.2 engine wins #148, fix: extinguish ignored review bugs, purge em dashes, add mermaid, v0.1.0 perf baseline #150): PERFORMANCE.md comparing v0.1.0 → v0.2.2 (allocations/order −35%, cycles/order −6.8%, branch-miss 2.01%→1.68%, latency unchanged; cache-miss honestly unavailable, M29 follow-up: full cache-counter PMU evidence (bare-metal Apple PMU now partial; cache events unsupported) #90), with zero-[unknown] flamegraphs.
• Bug/style sweep (fix: extinguish ignored review bugs, purge em dashes, add mermaid, v0.1.0 perf baseline #150): previously-unaddressed CodeRabbit findings fixed, every em/en dash removed repo-wide, mermaid diagrams added across the docs.

make check/make asan 272/272; determinism preserved.

After merge: tag v0.2.2 and publish a GitHub-only release.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Updated release notes and project status to reflect that version 0.2.2 is now released.
  • Expanded release documentation with more detail on performance evidence, security/robustness improvements, and the documentation refresh.

• Chores

  • Refreshed release-readiness guidance to match the latest tagged release and clarify the bundled deliverables.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@div0rce, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 50 minutes and 20 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c8bd01d1-a365-4c57-95e5-6f3a51cf01a9

📥 Commits

Reviewing files that changed from the base of the PR and between ceda15e and eb81e83.

📒 Files selected for processing (5)

• AGENTS.md
• CLAUDE.md
• HANDOFF.md
• PROGRESS.md
• docs/release_readiness.md

📝 Walkthrough

Walkthrough

The release notes, progress tracker, and release-readiness document were updated for v0.2.2. The changelog adds documentation/evidence details, and the status docs now describe v0.2.2 as released and tagged.

Changes

Release documentation updates

Layer / File(s)	Summary
Release notes and evidence CHANGELOG.md	The 0.2.2 changelog entry updates the release date, expands the release note text, and adds a documentation-and-evidence subsection.
Release state and outcome PROGRESS.md, docs/release_readiness.md	The progress tracker and release-readiness note are updated to mark v0.2.2 as the released latest tag and revise the outcome wording.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Poem

🐰 I hopped through notes in morning light,
v0.2.2 now gleams just right.
Docs and tags all line up neat,
My tiny paws tap a release beat.
Ears up! The changelog has a cheer,
and bunny whiskers sniff: release is here.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers the release content, but it does not follow the required template sections for Milestone, DoD, Tests, or Notes.	Add the missing template sections: Milestone, a 2-5 sentence Summary, the DoD checklist, a Tests code block with commands, and Notes/decisions.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately captures the main change: releasing v0.2.2.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-v0.2.2

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/release_readiness.md`:
- Around line 96-102: The release-readiness summary is inconsistent with the
updated verification totals, so reconcile the evidence before merging. Update
the release record in release_readiness.md to match the current counts used in
CHANGELOG.md and PROGRESS.md, and ensure the v0.2.2 release narrative,
verification rows, and status text all agree. Check the release summary block
around the v0.2.2 entry and keep the references to the existing release markers
and evidence items aligned with the corrected total.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8e9e1bf2-96ce-49b8-95c3-78c49c329cd1

📥 Commits

Reviewing files that changed from the base of the PR and between afe3f20 and ceda15e.

📒 Files selected for processing (3)

• CHANGELOG.md
• PROGRESS.md
• docs/release_readiness.md

[codescene-delta-analysis]

No application code in the PR — skipped Code Health checks.

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.