feat(operations): restack runner-assignment audit on latest main

[seonghobae]

Fresh protected-main successor for the runner-assignment evidence lane.

Exact current source

• base: protected main e64ccc70506916af23c2a1bb97e96dd2cf95d76e;
• head branch: feat/actions-runner-assignment-audit-current-main-v5;
• exact current head: 28a5d57c9bf40c9f45fac1e9cfc532b88904d62c;
• the head was refreshed non-destructively by a two-parent merge commit preserving the proven 10-path product/test/docs delta while taking current protected-main truth;
• GitHub reports the PR mergeable and Ready for review.

The 10-path delta implements bounded GitHub Actions runner-assignment evidence: global 2,000-job and 30-minute grace bounds, defensive run/job source handling, cleanup/error precedence, CLI/operator documentation, and regression coverage. No predecessor check/review/scanner evidence transfers across the refreshed head.

Current gate state

Fresh exact-head application ci run 31681137878, central Security Scan run 31681137868, and reviewer-ci run 31681137850 were triggered against the current protected base and are still queued. Queued evidence is non-passing. Formal reviews and inline review threads are currently empty; live repository policy must be evaluated independently rather than inferred from predecessor prose.

Do not merge until the exact head and protected base remain unchanged, every applicable current-head gate is terminal success, current review/thread evidence remains clean, and live governance is satisfied. After protected integration, retain protected-main operational evidence for the runner-assignment audit before closing the owning operational gap.

Related: #30, #252, #240, #94.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 27 minutes

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: 665d9003-18df-4c95-a7bf-bc1b787b4ecc

📥 Commits

Reviewing files that changed from the base of the PR and between e64ccc7 and 28a5d57.

📒 Files selected for processing (10)

• CHANGELOG.md
• docs/doctoring/actions-runner-assignment-audit.md
• package.json
• scripts/actions-runner-assignment-audit.mjs
• scripts/lib/actions-runner-assignment-audit.mjs
• scripts/lib/actions-runner-assignment-source.mjs
• test/actions-runner-assignment-audit.test.ts
• test/actions-runner-assignment-cli.test.ts
• test/actions-runner-assignment-docs.test.ts
• test/actions-runner-assignment-source.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.}