board: record the PR #258 arc — neutralize-by-cfg beats remove - #259
Conversation
Two appends, no code: - EPIPHANIES.md: the #258 finding. The "dalek must be removed" conclusion was reached twice from a correct intrinsic count (57 sites) and a wrong inference — the whole vector backend sits behind one cfg at backend/mod.rs:42, so reachability, not porting, was the question. Records the verified counts, the one-line fix, the serial-costs-nothing argument, and the X25519 contributory-check tripwire. - vertical-simd-consumer-contract.md: the escalation ladder this mints for third-party deps — (1) grep for the backend gate and neutralize by cfg, (2) port onto ndarray::simd only for paths we execute, (3) remove only with a failed gate-grep cited. "Contains raw intrinsics" and "raw intrinsics are reachable" are different claims; the matryoshka invariant binds the second.
|
Warning Review limit reached
Next review available in: 41 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_3ea76dc6-ed17-48d4-913a-c88c725152bc) |
2 participants
Board hygiene for the just-merged #258. Two appends, no code:
.claude/board/EPIPHANIES.md— the finding: the "dalek must be removed" conclusion was reached twice from a correct intrinsic count (57_mm*sites) and a wrong inference. The whole vector backend sits behind one cfg (backend/mod.rs:42), so reachability — not porting — was the question. Records the verified counts, the one-line.cargo/config.tomlfix, whyserialcosts nothing on our paths, and the X25519 contributory-check tripwire test..claude/knowledge/vertical-simd-consumer-contract.md— the escalation ladder this mints for third-party dependencies: (1) grep for the backend gate and neutralize by cfg, verify with a clean rebuild; (2) port ontondarray::simdonly for paths we actually execute (thevendor/chacha20precedent); (3) remove only with a failed gate-grep cited. "Contains raw intrinsics" and "raw intrinsics are reachable" are different claims; the matryoshka invariant binds the second.Follows the board rule that a merged arc's correction lives on the board, not only in a PR body where future sessions won't look first.
Generated by Claude Code