fix: Dispatcher release summary now carries the uloop prefix

[hatayama]

Summary

• The collapsible release sections now name the dispatcher consistently with the project runner.

User Impact

• Before: release PR collapsible rows read unity-package: ..., dispatcher: ..., uloop-project-runner: ... — the dispatcher was the only native binary without the uloop prefix (visible in chore: release v3-beta #1693).
• After: the dispatcher row reads uloop-dispatcher: <version>, matching the project runner naming.

Changes

• The release PR body clarifier renames the dispatcher summary to uloop-dispatcher: <version> (display only; the release-please component id and the dispatcher-v* tag format stay untouched).
• scripts/sync-published-release-pr-labels.sh resolves release tags from these summaries, so it now also accepts the uloop-dispatcher slug and maps it to the dispatcher-v tag.
• Heading clarification keeps working on a renamed summary, and a second clarification pass leaves the block unchanged (covered by a new stability test).

Verification

• go test ./internal/automation/ in cli/release-automation (new assertions fail without the fix)
• sh scripts/test-sync-published-release-pr-labels.sh (new uloop-dispatcher tag-resolution case fails without the fix)
• scripts/check-go-cli.sh passes

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 26 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2c9bc11b-0bea-4ef2-9bc6-931fba481734

📥 Commits

Reviewing files that changed from the base of the PR and between e7b2624 and 3f5508c.

📒 Files selected for processing (4)

• cli/release-automation/internal/automation/release_pr_body.go
• cli/release-automation/internal/automation/release_pr_checks_test.go
• scripts/sync-published-release-pr-labels.sh
• scripts/test-sync-published-release-pr-labels.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/uloop-dispatcher-summary-label

---

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.}