test: execute Ruby README quickstart

[kriptoburak]

Closes #18.

Summary

• run the README quickstart against a local WebMock fixture
• assert the encoded query contract
• assert the decoded paginated response
• keep credentials and remote services out of the test

Validation

• ./scripts/test
• ./scripts/lint
• bundle exec bundle-audit check --update
• bundle exec ruby scripts/coverage.rb
• bundle exec ruby scripts/check_reproducible.rb

---

Summary by cubic

Add test/x_twitter_scraper/readme_quickstart_test.rb to execute the Ruby README quickstart against a local WebMock fixture. It verifies the encoded search query and decoded paginated response while avoiding credentials and network calls, closing #18.

^{Written for commit 56bedd0. Summary will update on new commits.}

Note

Add contract test for Ruby README quickstart against GET /x/tweets/search

Adds readme_quickstart_test.rb, a Minitest suite that verifies the Ruby client's tweets.search method issues the correct HTTP request and maps the response to PaginatedTweets fields. Uses WebMock to stub the endpoint and assert request parameters (q, limit) and response fields (has_next_page, next_cursor, tweets).

^{Macroscope summarized 56bedd0.}

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 17 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: 8158711b-95bc-447c-a94d-021f2f821bdd

📥 Commits

Reviewing files that changed from the base of the PR and between b7bce9f and 56bedd0.

📒 Files selected for processing (1)

• test/x_twitter_scraper/readme_quickstart_test.rb

---

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