docs: x265 probe-wave-2 verdicts — sprite-replay Results + §5 wave-2 table + §10 WH-leg RESULT-2

[AdaWorldAPI]

Summary

Doc-only companion to the lance-graph wave-2 probe PR (probes live there; Opus-adjudicated LAND-AS-IS). Records both verdicts in the matrix doc + sprite plan:

• sprite-replay plan Results section: PASS-AT-SIGNED360 (scoped to helix-manifold motion; arbitrary-motion [H]); ResidueEdge-24bit INSUFFICIENT (hemisphere-blind + 8-bit-rim rank-adjacency hazard) → Signed360-only; KILL did not fire.
• §5 wave-2 results sub-table for both probes; the base PROBE-SPRITE-REPLAY queue row marked with its verdict.
• §10 WH-magnitude leg RESULT-2: upgraded from bare NOT-TRANSFERRING to TRANSFERS-with-escape+centroid on structured tiles, with the compound-column caveat (the win is a codec-pairing property; WH's isolated margin unmeasured; bareB/A stays NEUTRAL).

Verification

• Knowledge-doc test suite: 117/117 green.
• All numbers from the adjudicated live runs; caveats carried verbatim so no strength is over-read.

🤖 Generated with Claude Code

https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@AdaWorldAPI, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7022f45b-8198-42e5-a92d-c267d949291c

📥 Commits

Reviewing files that changed from the base of the PR and between 95176af and 5189437.

📒 Files selected for processing (2)

• .claude/knowledge/pr-x12-h268-morton-wgpu-synergies.md
• .claude/plans/x265-sprite-replay-probe-v1.md

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot 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_66e83147-d3c0-4d00-bf01-6773cddaa416)