knowledge: rung POV correction (codex stockfish-rs #8) + ladder-table MD058 spacing#685
Conversation
The rung probe's third oracle defect, found by codex and fixed in stockfish-rs 8e563ab: evaluate() is side-to-move POV, so cross-ply sign comparisons were move-parity noise. Post-fix a real convergence gradient appears (mean first-third 0.48 -> last-third 0.74, 13/25 games) — previously erased — but still below the pre-registered gate; D-SF-RUNG-1 stays INCONCLUSIVE/[H] with the two remaining defects (mate-blindness, unsettled playouts) binding. Standing lesson banked: normalize POV before any cross-ply eval comparison (the L5 corpus never caught this — all five FENs are White-to-move). Also: blank lines around the tenant-ladder table (coderabbit MD058 on #684). Board: EPIPHANIES E-RUNG-POV-CORRECTION-1 prepended (same commit). Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Awg6TXocHcwTtc6eGsHcdD
|
Warning Review limit reached
Next review available in: 31 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_92c03214-3285-4ccf-9fe1-aee49808d923) |
2 participants
What
Two review-comment follow-ups on the merged #684, one commit:
.claude/knowledge/stockfish-nnue-as-perturbation-cascade.md): codex on stockfish-rs feat: add Belichtungsmesser HDR popcount-stacking early-exit cascade #8 found thatevaluate()is side-to-move POV, so the D-SF-RUNG-1 probe's cross-ply sign comparisons were move-parity noise. The doc's rung section now records this as oracle defect (0) — fixed in stockfish-rs8e563abwith fixed-White-POV normalization — with the post-fix numbers (mean first-third agree 0.48 → last-third 0.74, 13/25 games; still below the pre-registered gate, so the verdict remains INCONCLUSIVE and D-SF-RUNG-1 stays [H]).Board:
E-RUNG-POV-CORRECTION-1prepended to.claude/board/EPIPHANIES.md(append-only discipline; the standing lesson: the L5 parity corpus never caught the POV bug because all five anchor FENs are White-to-move — POV bugs need mixed-side falsifiers).🤖 Generated with Claude Code
https://claude.ai/code/session_01Awg6TXocHcwTtc6eGsHcdD
Generated by Claude Code