chore(release): 0.5.3

[arkadianet]

Release cut for 0.5.3. Branch is origin/main (f147a5c) + the version/metadata bump only — no code changes.

Contents

• Bump [workspace.package] version 0.5.2 → 0.5.3 (inherited by all 19 member crates), refresh Cargo.lock.
• Regenerate the version-stamped OpenAPI golden fixtures (openapi_native.yaml / openapi_v1.yaml) — the only spec delta is info.version; both *_matches_snapshot tests pass.
• Write the CHANGELOG.md [0.5.3] section.

What 0.5.3 is

The refactor-and-harden release: the workspace-wide oversized-file split epic (#200, #202, #205–#219, behavior-preserving), a review-findings hardening pass (storage data-integrity #218, snapshot-sync authentication #219, sync download-path DoS bounds #220/#221), and correctness fixes — #210 NiPoPoW deserialize bounds, #222 mempool orphan-cascade eviction, #223 sigma evaluator fidelity, #224 ADProofs Mode-5 scheduling, #225 mining storage-rent vs EIP-27, #226 typer parse-order (Finding E), #199 custom extension fields. See CHANGELOG.md for the full list.

Release-cut gate

Per the release-cut rule, the whole-workspace gate (fmt --all --check, clippy --all-targets --all-features -D warnings, test --all) runs here via CI on the merge result. Locally verified: node builds clean at 0.5.3, OpenAPI snapshot tests green.

After merge: tag v0.5.3 on the merge commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Kw7uCwqmiGna8fpg6TvxGi

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 4 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 68a15b23-d73f-4c55-8773-8b1c1f3956de

📥 Commits

Reviewing files that changed from the base of the PR and between f147a5c and 39cfe91.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• CHANGELOG.md
• Cargo.toml
• ergo-api/tests/fixtures/openapi_native.yaml
• ergo-api/tests/fixtures/openapi_v1.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-0.5.3

---

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