docs: h268-probe-wave-1 verdicts — §10(g) decorrelation half killed, §10 RESULT lines, §5 results sub-table

[AdaWorldAPI]

Summary

Doc-only companion to the lance-graph probe-wave PR (probes live there; Opus-adjudicated per h268-probe-wave-v1.md). Records the three measured verdicts in the matrix doc:

• §10(g) corrected — the "decorrelated by construction" half is KILLED by PROBE-WALK-SPECTRUM: the parity of a full-period-17 permutation is an exact periodic waveform whose autocorrelation is governed by C(τ mod 17) at every lag; measured lattice |R| max 0.875 vs PRNG 0.0205 (42.7×). Coprimality ≠ decorrelation. The "known period-17 structure" half is CONFIRMED (R(17m)=1−8m/N, measured 0.998/0.996/0.994). D-QUANTGATE and the walk's bijectivity-quantization role are explicitly unaffected.
• §10 forward-synthesis RESULT lines: PROBE-WH-MAG → NEUTRAL, bare-tile leg NOT-TRANSFERRING (B/A 0.929/1.411/1.869; the row-level WH win needs Passthrough + centroid residual; shipped row codec untouched; PROBE-WH-MAG-2 deferred). PROBE-SIG-CHECKSUM → PASS with the depth-2 parallel-chord blind-spot bound (digest null space exceeds tree-like equivalence; mitigate via depth 3 or paired digest).
• §5 gains a results sub-table for the wave (verdict / numbers / consequence per probe); the open-queue table is untouched.
• Blackboard entry appended.

Verification

• Knowledge-doc test suite: 117/117 green.
• All numbers copied from the adjudicated live runs (lance-graph probe modules; reviewer re-ran and hand-verified the closed forms).

🤖 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: 47 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: 06b18051-7466-4004-8ef0-052830ee4245

📥 Commits

Reviewing files that changed from the base of the PR and between 95dc8af and 95aec8e.

📒 Files selected for processing (2)

• .claude/blackboard.md
• .claude/knowledge/pr-x12-h268-morton-wgpu-synergies.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_61757ea4-c86d-454f-9609-df2af95169ef)