feat(retrieval): ship the provenance champion as the retrieval default - #572
Conversation
pin checkout and setup-python to immutable commit shas (mutable tags in a pull_request_target workflow are a supply-chain surface), and classify a delete-only strategy pr as normal instead of engine - the filename shape matched but there is nothing to fetch at the head sha, so the gate failed messy instead of passing through.
the engine-lane winner (pr #567) moves in-package as vouch.strategies.provenance and becomes what challengers must beat: contrib/strategies/baseline.py now delegates to it instead of returning identity order. new KBs get it as the final reorder stage via the starter config (retrieval.strategy); existing KBs keep byte-identical ordering until they add the key, and strategy: null opts out. the bench is unaffected - its throwaway KBs write their own config, so kits and strategies keep being measured explicitly. rerank-isolation tests opt out of the strategy stage, since the champion is final-say and would re-sort the asserted window.
|
Warning Review limit reached
Next review available in: 14 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. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
✨ 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 |
github-actions
Bot
added
docs
1 participant
follow-up to #569: the competition round-1 hardening and the champion promotion.
vouch.strategies.provenanceand becomes the reigning champion:contrib/strategies/baseline.pydelegates to it, so challengers must now beat real provenance-aware ranking, not identity order.retrieval.strategy); existing KBs keep byte-identical ordering until they add the key;strategy: nullopts out. the bench is unaffected (throwaway KBs write their own config).validation: full suite (1833 passed), mypy, ruff; paired bench verifies the champion at +0.05 composite over identity baseline (band 0.0381) with the ci-exact loop.