chore(co-occurrence): baseline the 60 pre-existing clones — release prerequisite - #311
Conversation
…rerequisite (sc-1414) The repaired clone gate (#305/#308) goes live in consumer hooks at the next release; without a baseline every commit touching a cloned file blocks on debt that predates the gate working. `guard-clone json | guard-dup-allowlist baseline-clones` freezes all 60 as decaying baseline entries (the matcher baseline burn-down pattern). Disposition choice: baseline ALL 60, not just the 43 eval-harness clones — leaving the 16 product clones unbaselined would block unrelated commits touching those files before the dedup work (sc-1414 part 2) lands. Baseline entries decay, so the product clones resurface on schedule; the eval-harness family stays frozen deliberately (deduping it would drift published runner/scorer checkpoint hashes for 2-3 suites — the overrides.mts precedent), as does the deliberate run-review<->bench mirror. Gate verified clean after: scan --gate exit 0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 24 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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
Shortcut sc-1414 part 1 (epic 1399). The repaired clone gate (#305/#308) goes live in consumer hooks at the next release; without a baseline, every commit touching a cloned file blocks on debt that predates the gate working.
guard-clone json | guard-dup-allowlist baseline-clones→ all 60 current clones frozen as decayingbaseline 2026-08-02entries in.co-occurrence-allowlist.json. Verified:scan --gateexits 0 on the clean tree afterward.Disposition choice (deliberate): baseline ALL 60, not just the 43 eval-harness clones. Leaving the 16 product clones unbaselined would block unrelated commits touching those files before the dedup work (sc-1414 part 2) lands; baseline entries decay, so they resurface on schedule. The eval-harness family stays frozen on purpose (deduping it drifts published runner/scorer checkpoint hashes for 2–3 suites — the
overrides.mtsprecedent), as does the deliberaterun-review.mts ↔ bench.mtsmirror.Part 2 (the 16 real product dedups, clusters listed in sc-1414) follows as separate judgment-refactor PRs.
🤖 Generated with Claude Code