test: expose Jazzer fuzzing and require code owners

[kriptoburak]

Summary

• assign every path to two maintainers with write permission
• require code-owner review on the protected branch
• expose the existing Jazzer campaign through a real Java test bridge
• compile test code for Java 26
• preserve Java 8 bytecode for every published artifact

Rationale

Scorecard currently detects Jazzer imports only in Java test files. The fuzz target remains real. The Java bridge consumes the campaign's input.

Validation

• compiled the targeted Java and Kotlin tests
• ran the 30-second Jazzer campaign
• completed 3,655,609 runs with seed 1719876642
• reached BUILD SUCCESSFUL in the full Gradle test run
• ./scripts/lint
• ./scripts/audit
• uvx --from reuse reuse lint
• git diff --check

The full test wrapper reached its 60-second cap after Gradle succeeded. The reproducibility check also exceeded the local cap. Required hosted jobs must pass before merge.

Note

Require code owner review and compile test sources with JVM 26

• Adds a CODEOWNERS file assigning repository-wide ownership to @kriptoburak and @furkanerday, requiring their review on all PRs.
• Configures compileTestJava to use --release 26 and compileTestKotlin to target JVM_26 in the Gradle convention plugins.
• Extracts RetryAfterFuzzInput.consume() as a static helper to avoid duplicating data.consumeRemainingAsString() in the fuzz test.

^{Macroscope summarized aae608f.}

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[furkanerday]

Reviewed the complete diff, description, commit history, checks, discussion, repository policy, relevant contracts, tests, dependency and release integrity, licensing, and public-safety implications. Required checks are green and no actionable review threads remain.

[furkanerday]

Human-authored commits 6bd7023, b1f38ef, fddf8f6 lack author-matching Signed-off-by trailers. Each author must amend their own affected commit and re-push it; a later maintainer commit cannot cure an earlier contributor commit. Re-request review after the rewritten commit history and required checks complete.

[kriptoburak]

Rewrote the PR commits without changing the patch to add exact author-matching DCO trailers, and rebased onto the current base branch. Fresh hosted checks can now validate the rewritten history.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Warning

Review limit reached

@kriptoburak, 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f1a1e71-5cdc-4a8e-92e3-3dde5b8a7f1f

📥 Commits

Reviewing files that changed from the base of the PR and between fa76285 and aae608f.

📒 Files selected for processing (5)

• .github/CODEOWNERS
• buildSrc/src/main/kotlin/x-twitter-scraper.java.gradle.kts
• buildSrc/src/main/kotlin/x-twitter-scraper.kotlin.gradle.kts
• x-twitter-scraper-java-core/src/test/java/com/x_twitter_scraper/api/core/http/RetryAfterFuzzInput.java
• x-twitter-scraper-java-core/src/test/kotlin/com/x_twitter_scraper/api/core/http/RetryAfterFuzzTest.kt

---

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

Dismissed after verifying every affected commit on the current head has an exact author-matching Signed-off-by trailer. Independent re-review remains requested.

[furkanerday]

Reviewed the complete current diff, description, commit history, checks, discussion, repository policy, relevant contracts and tests, dependency and release integrity, licensing, DCO, and public-safety implications. Required checks are green and no actionable review threads remain.

[furkanerday]

Reviewed the complete current diff, description, commit history, checks, discussion, repository policy, relevant contracts and tests, dependency and release integrity, licensing, DCO, and public-safety implications. Required checks are green and no actionable review threads remain.