fix(ci): add statuses:write permission to promote caller

[castrojo]

Problem

The reusable-promote-squash.yml@v1 was updated today (2026-06-23) to post a validate=success commit status on the squash branch HEAD, so the merge queue can accept the PR in the same run without re-triggering. This requires statuses: write in the promote job.

Caller-level permissions set the maximum grants available to called workflow jobs. promote-testing-to-main.yml did not grant statuses: write, so GitHub rejects the workflow at startup before any job runs (startup_failure on every dispatch).

Root cause of PR #1055 being closed UNSTABLE: The workflows: write permission added in #1054 caused actionlint to fail (it's not in actionlint's known-scope list). The promote workflow detected the UNSTABLE lint check and eventually closed the stale PR once testing == main.

Root cause of current startup_failures: Missing statuses: write in the caller — all 3 retrigger attempts after 23:00 UTC fail at startup.

Fix

Add statuses: write to promote-testing-to-main.yml's top-level permissions block.

Verification

After merge, retrigger the promote workflow to confirm it runs (even if no-op since testing == main).

Closes #1055 (indirectly — fixes the promote pipeline)

[coderabbitai]

Warning

Review limit reached

@castrojo, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 12 minutes. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e260db8b-8825-467d-bda6-f49079119384

📥 Commits

Reviewing files that changed from the base of the PR and between 9e6c0ce and c7b6f89.

📒 Files selected for processing (1)

• .github/workflows/promote-testing-to-main.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/promote-statuses-permission

---

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

[github-actions]

Thanks for the PR! A maintainer will review it.

While you wait, make sure these pass locally:

just validate        # element graph check
just build default   # build the image
just boot-test       # confirm the desktop boots (exits 0 = pass)
just lint            # bootc container lint

If this PR fixes a bug, add verify steps to the linked issue so users can confirm the fix on their hardware after the next nightly ships:

```verify
ujust <something>   # what users should run to confirm the fix
```