chore(core): bump engine to a3bf98e — adopt served_by_eq (peer-level policy selection)#48
Conversation
…policy selection) Pulls unhardcoded-engine #24: the `served_by_eq` predicate, which selects by the executed route (a marketplace peer, or the provider for a direct route) — the same notion the host already records as calls.served_by. A policy can now pin or exclude a specific peer (or(served_by_eq …) / not(…), sugar served_by_in / served_by_not_in), not just a whole provider via provider_eq. The host passes policy_ir straight through to the engine, so adoption is the submodule bump plus the SKILL.md guidance: peer targeting IS now expressible — the old "not a policy concern" note is corrected — but prefer gating on properties (reputation_score, success_rate) over pinning peer ids, which rot as peers churn.
|
Warning Review limit reached
Next review available in: 33 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
1 participant
What
Bumps the
coresubmodule (unhardcoded-engine)537e204 → a3bf98e, adopting #24: theserved_by_eqpredicate.served_by_eqselects by the executed route — a marketplace peer (offer.peer_id), or the provider for a direct route — the same notion the host already records ascalls.served_by. A policy can now pin or exclude a specific peer, not just a whole provider:Why this is the whole adoption
The host passes
policy_irstraight through to the engine (validation + interpretation live incore), so there's no host-side predicate registry to update. Adoption = the submodule bump + the policy-authoring docs.SKILL.md
served_by_eq.reputation_score,success_rate) over pinning peer ids, which rot as peers churn —served_by_eqis for a trusted-peer allowlist, not the default.Verification
Full suite (engine embedded via lupa) 404 passed / 3 skipped / 0 failed;
test_skill_mdgreen with the doc edits.