feat: expose schema recovery over the C ABI

[0xgleb]

Adds additive schema reconciliation and schema record exports over the shared engine facade, bumps the ABI minor version, validates compaction policy decoding, and covers the recovery protocol against the real in-memory engine.

Closes #81.

---

This is part 27 of 32 in a stack made with GitButler:

•  32  feat: reconcile Haskell aggregate schemas #52
•  31  docs: reserve TypeScript bindings for 0.5.0 #51
•  30  test: property-check protocol invariants #49
•  29  test: discover Haskell specs with Hspec #48
•  28  refactor: use the Event.Sorcery module namespace #47
•  27  feat: expose schema recovery over the C ABI #46 👈
•  26  refactor: expose schema recovery through engine facade #45
•  25  bench: add Haskell engine benchmarks #43
•  24  test: share cross-binding encoding vectors #42
•  23  feat: renew Haskell job leases #41
•  22  feat: deliver Haskell dispatch verdicts #40
•  21  feat: settle Haskell job executions #39
•  20  feat: route Haskell job executions #38
•  19  feat: seal Haskell dispatch outcomes #37
•  18  feat: load Haskell entities from snapshots #36
•  17  feat: execute typed Haskell commands #35
•  16  feat: restore the typed Haskell domain model #34
•  15  feat: run jobs from the Haskell binding #33
•  14  refactor: package the Haskell binding by feature #32
•  13  feat: expose job operations over the C ABI #31
•  12  feat: expose the existing job runtime #30
•  11  feat: call the shared engine from Haskell #29
•  10  feat: add deterministic Haskell engine codecs #28
•  9  feat: expose stream operations over the C ABI #27
•  8  feat: add the C ABI lifecycle #26
•  7  api: expose the shared engine facade #25
•  6  refactor: route job storage through the engine facade #24
•  5  refactor: extract the serialized engine facade #23
•  4  test: pin atomic event and job persistence #22
•  3  chore: update 0.4.0 ownership metadata #18
•  2  build: unify the Rust and Haskell toolchain #17
•  1  docs: specify the 0.4.0 monorepo engine #14

[coderabbitai]

Warning

Review limit reached

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

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

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1182d369-63db-4836-b7c9-43b4362ae0c9

📥 Commits

Reviewing files that changed from the base of the PR and between d14f5f4 and 880ec8b.

📒 Files selected for processing (1)

• crates/event-sorcery-ffi/src/lib.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/0.4-c-api-schema

---

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