ci(bump-callers): trigger the pr-size fleet on the Go counter source, not just pr-size.yml (BE-3482)

[mattmillerai]

Fast-follow to #35 (merged): a self-review pass caught this after #35 landed, so
it's a small standalone PR rather than reopening the merged one.

What

bump-pr-size-callers.yml only triggered on changes to pr-size.yml itself.
But the actual counting logic consumers run lives in scripts/check-pr-size/**
— pr-size.yml's own header says the size job builds that Go tool from the
workflows_ref SHA a caller pins, mirroring how cursor-review.yml checks out
.github/cursor-review/* at the same pinned ref. So a behavior-changing edit
to the Go counter wouldn't trigger a caller SHA-bump, and pinned callers would
silently keep running stale tool behavior.

Fix: add scripts/check-pr-size/** to the fleet's trigger paths (mirroring how
bump-agents-md-callers.yml already watches both its workflow file and
.github/agents-md-integrity/**), and update the README fleet table row to
match. Also cleaned up two stale "two entrypoints" comments in the sibling
fleet files left over from before #35 added the third fleet.

Test plan

• shellcheck -x .github/bump-callers/bump-callers.sh .github/bump-callers/tests/test_bump_callers.sh
• bash .github/bump-callers/tests/test_bump_callers.sh (86/86 pass)
• YAML-parsed all three touched workflow files

[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: 38 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 02df55ce-6a1b-48b5-a5f2-7f719dbd7788

📥 Commits

Reviewing files that changed from the base of the PR and between be4fd67 and 3eb1629.

📒 Files selected for processing (4)

• .github/bump-callers/README.md
• .github/workflows/bump-agents-md-callers.yml
• .github/workflows/bump-cursor-review-callers.yml
• .github/workflows/bump-pr-size-callers.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch matt/be-3482-bump-pr-size-fleet-trigger-fix

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch matt/be-3482-bump-pr-size-fleet-trigger-fix

---

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