test(coverage): measure replay request core

[seonghobae]

Purpose

Advance #84 from protected main 1c1f7b2eaa7c676bc5ef3797cc362077cf561a33 with the next bounded credential-exchange coverage slice: replay-claim integration and target-request authorization inside claimVerifiedOidcUsage / createRepositoryInstallationToken.

RED

Exact RED head 69e0fe4467ab07052a287d6adcc1d3f80cd432bb adds a deterministic coverage-policy contract requiring the replay/request core to contain no broad V8 ignore markers. Protected main still wraps that region in a broad exclusion, so this head is intentionally RED before production instrumentation changes.

Boundaries

• No coverage threshold is weakened; statements/branches/functions/lines remain 100%.
• No private helper is exported for testing.
• No replay ordering, target authorization, GitHub App permissions, external dependency source, deployment, release, or licensing behavior changes in the RED commit.
• Open PR Route remaining LLM jobs through contextual-orchestrator #403 does not modify src/index.ts or test/production-coverage-policy.test.ts; docs: establish canonical product and trust-boundary documentation #71 owns src/worker.ts/docs but not this src/index.ts region; feat(sandbox): build and verify patch-validator image #67 is a separate validator-image stack.

Keep Draft through RED -> smallest GREEN -> fresh exact-head application CI/reviewer/Security Scan verification. Pending/failing/predecessor/status/model-only evidence is non-passing.

Related: #84.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 20 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: 91ae0f5f-82a7-4479-8ba6-d33786802a7a

📥 Commits

Reviewing files that changed from the base of the PR and between 1c1f7b2 and c83e79d.

📒 Files selected for processing (4)

• src/index.ts
• test/production-coverage-policy.test.ts
• test/replay-request-core-coverage.test.ts
• test/replay-target-authorization-coverage.test.ts

---

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 is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.