feat(#613): enable canary-rollout schedule in .github (cutover)

[don-petry]

What

PR-C2 of the epic #613 cutover. Re-enables the 4-hourly schedule: on the relocated canary-rollout workflow (shipped disabled in #624), making .github the live host for autocut → promote-all → sync-issues.

 on:
-  # schedule:  # DISABLED until epic #613 step-4 cutover …
-  #   - cron: "0 */4 * * *"
+  schedule:
+    - cron: "0 */4 * * *"   # every 4 hours
   workflow_dispatch:

⚠️ Merge order (hard requirement)

Must land AFTER petry-projects/.github-private#1128, which deletes the engine + workflow there and stops that repo's schedule. Both CANARY_AUTO_CUT and CANARY_AUTO_PROMOTE are true, so the two schedules must never overlap (they'd race on tag mutations). Sequenced strictly after the .github-private removal.

Already live-validated

workflow_dispatch evaluate run 28990172900 in .github minted the release-manager App token, resolved cross-repo dev-lead channel tags on .github-private, and computed the #548 gate — the engine runs correctly from its new home.

Refs #613

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

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

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

Run ID: 2648d96f-3cca-4468-9e61-aa86ea408296

📥 Commits

Reviewing files that changed from the base of the PR and between 9b27602 and febd624.

📒 Files selected for processing (1)

• .github/workflows/canary-rollout.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch epic-613-cutover-enable-schedule

---

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

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[Copilot]

Pull request overview

Re-enables the scheduled trigger for the relocated canary-rollout workflow in petry-projects/.github, completing the cutover step so this repo becomes the live host for the 4-hourly automation loop (autocut → promote-all/evaluate-all → sync-issues/drift).

Changes:

• Re-enabled the schedule: trigger to run every 4 hours.
• Restored automated canary-rollout orchestration cadence from .github (instead of dispatch-only).