CLOUD-2092 Add PR Tests gate

[tvaughanRR]

Summary

This repo (the public Python SDK) had no pull-request-triggered CI. Adds .github/workflows/pr-tests.yml:

• run_python_tests job: checks out via the RR wrapper, sets up Python (3.13 and 3.12 matrix) via the RR wrapper, pip install -e . pytest, then runs the unit tests with pytest.
• pr-tests aggregator job (name "PR Tests") gating on the test job via rocketreach/github-actions/testing/pr-tests.

The repo uses setup.py (not poetry), so the reference template's poetry steps were adapted to pip. There is no lint/type config in the repo (no ruff/mypy/flake8/black), so the gate runs tests only.

test_integration.py targets a localhost:8000 dev server (the Development gateway environment) that is not available on CI runners, so the pytest step runs the unit suites (test_resource.py, test_search.py) only.

Test plan

• YAML validated locally (parses; pr-tests job needs run_python_tests).
• Unit tests pass locally: 9 passed, 7 subtests passed.

Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

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

Run ID: ae06daba-6c74-4419-ad49-24da472e950d

📥 Commits

Reviewing files that changed from the base of the PR and between a9fe4ce and f873f11.

📒 Files selected for processing (1)

• .github/workflows/pr-tests.yml

---

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

[tvaughanRR]

Backing out: rocketreach_python is a public repo and cannot resolve the internal rocketreach/github-actions wrapper actions. Per decision, it will be added to the org standard-ruleset exclude list (exemption) instead of carrying a PR Tests gate.