ci(OMN-13914): add synchronize+reopened to pr-title-check trigger

[jonahgabriel]

Summary

Fan-out of the OMN-13909 canary fix (onex_change_control PR #3542, merged) to close the pr-title / check-title required-check merge-wedge in this repo. types: [opened, edited] never re-reports the required context on a push without a subsequent title edit, wedging mergeStateStatus: BLOCKED even when every other required check is green. Full root-cause analysis on OMN-13909; this repo is one of 9 fan-out targets tracked under the child ticket OMN-13914 (omnidash excluded — parked by operator directive).

Fix

.github/workflows/pr-title-check.yml: types: [opened, edited] → types: [opened, edited, synchronize, reopened]. Identical one-line diff as the canary fix — no scope creep. No change to pr-title-check-reusable.yml needed (it already reads the live event payload title, which GitHub populates correctly on synchronize).

Test plan

• YAML parse check
• pre-commit run --files .github/workflows/pr-title-check.yml — all applicable hooks passed
• Targeted verification per the ci(OMN-13875): CI Summary directly gates Contract Compliance Check #2188/feat(OMN-1932): Wire snapshot publisher into registration handlers #254 precedent for workflow-YAML-only diffs — full multi-hour local suite not required for a single-line CI trigger-type change with zero Python/runtime impact

Evidence-Ticket: OMN-13914

OMN-13914 (see OMN-13909 for full context)

Evidence-Source: OCC#3553

[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: 44 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 208de32c-d186-4a0b-afbb-5889bec55df6

📥 Commits

Reviewing files that changed from the base of the PR and between 7ffdbca and a3ab717.

📒 Files selected for processing (1)

• .github/workflows/pr-title-check.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-13914-pr-title-synchronize-trigger

---

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