Sync main into beta; converge CI on shared reusable workflows

[bharvey88]

Version: 26.7.9.1 (no change — CI/workflow only)

What does this implement/fix?

Syncs main into beta so the beta -> main release PR (#97) merges cleanly. The only real conflicts were the CI workflow files, resolved by converging on the shared ApolloAutomation/Workflows reusable workflows (per Trevor) while keeping the fork-PR support added on beta:

• autoassign.yml — thin caller of the shared autoassign.yml@main, triggered on pull_request_target so fork PRs get auto-assigned (removed the fork-skip if: guard, no longer needed with the write token).
• ci.yml — thin caller of the shared esphome-ci.yml@main (its default stable/beta/dev matrix reproduces beta's old inline 9-build matrix). Label-check removed from here.
• label-check.yml — kept as its own thin caller on pull_request_target (build and label-check need different triggers, so they can't share one file).

Also pulls in main's dependabot.yml update and drops the duplicate root PULL_REQUEST_TEMPLATE.md.

No firmware code or version change — does not publish.

Types of changes

• Bugfix (fixed change that fixes an issue)
• New feature (thanks!)
• Breaking change (repair/feature that breaks existing functionality)
• Dependency Update - Does not publish
• Other - Does not publish
• Website of github readme file update - Does not publish
• Github workflows - Does not publish

Checklist / Checklijst:

• The code change has been tested and works locally
• The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

• Added/updated documentation for the web page

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 22 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: CHILL

Plan: Pro

Run ID: f597ddd5-d127-4437-870c-25589be3556a

📥 Commits

Reviewing files that changed from the base of the PR and between adf9bd8 and c686c79.

📒 Files selected for processing (4)

• .github/dependabot.yml
• .github/workflows/autoassign.yml
• .github/workflows/ci.yml
• PULL_REQUEST_TEMPLATE.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sync-main-into-beta

---

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