spike(v4): block transport selection pending native evidence

[YashasVM]

Outcome

No transport is selected. The V4-01 acceptance matrix cannot be run honestly because pinned Windows libsrt/libsrtp2 development packages, the native two-candidate probe, an identical real-AU corpus with orientation/config metadata, and a target Wi-Fi impairment topology are absent.

Included

• reproducible prerequisite audit under spikes/transport`n- checked-in host fingerprint and exhaustive 192-cell NOT_RUN matrix
• bounded proposed queue declarations with capacity, deadline, byte/fragment limits, and overflow policy
• blocking ADR with exact unblocking gates and rollback
• behavioral tests for exhaustive matrix coverage and preservation-field requirements

Verification

• python -m pytest tests/test_v4_transport_audit.py tests/test_v4_phase0_tools.py -q (9 passed)
• python spikes/transport/audit.py --output docs/evidence/v4-01-transport-audit (expected exit 2 while blocked; 192 cells emitted)
• git diff --check`n

Scope

No product transport, Android, OBS, engine, or legacy production path changes. Simulated Phase 0 impairment is explicitly not used as selection evidence.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 4 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ba46fe01-982c-4605-9698-73217a31f3a9

📥 Commits

Reviewing files that changed from the base of the PR and between 6c65476 and 80ad731.

📒 Files selected for processing (6)

• docs/decisions/0001-v4-transport-blocked.md
• docs/evidence/v4-01-transport-audit/environment.json
• docs/evidence/v4-01-transport-audit/matrix.jsonl
• spikes/transport/README.md
• spikes/transport/audit.py
• tests/test_v4_transport_audit.py

---

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.}