fix(ci): retire bot-authored PR branch sync

[BigSimmo]

Summary

• remove the automatic GITHUB_TOKEN pull-request branch update workflow that produced bot-authored merge heads requiring manual workflow approval
• keep branch synchronization as an operator-only helper that is dry-run by default and fails closed for missing or bot identities before mutation
• fix the helper's structured repository-name parsing and add ordinary-CI guards against direct or indirect workflow-based branch updates
• align repository guidance and resolve durable issue Test RAG retry telemetry logging #82

Verification

• npm run check:github-actions — PASS, including direct and indirect unsafe-workflow self-tests
• npx vitest run tests/sync-open-pr-branches.test.ts — PASS, 7/7
• npm run sync:pr-branches — PASS, read-only inventory of 8 open PRs with zero updates
• npm run docs:check-index, npm run docs:check-scripts, npm run docs:check-links — PASS
• npm run verify:pr-local — PASS on the exact implementation head before merging current main: 393 files, 3,530 passed / 2 skipped, offline RAG fixtures; build correctly skipped for this scope
• post-main-merge npm run verify:cheap — all gates through lint PASS; typecheck did not start because another Database worktree held the shared Chromium heavy-test lease
• post-main-merge focused workflow/helper/docs checks — PASS

Risk and rollback

This intentionally replaces automatic synchronization with a human/operator action. The tradeoff is a manual sync step for behind PRs; the benefit is that required checks run on human-authored heads instead of becoming action_required. Reintroducing the old workflow is not recommended unless the authentication/approval model changes.

No branch was updated by the helper. No Supabase, Railway, OpenAI, or live RAG mutation was performed. RAG impact: no retrieval behaviour change — CI workflow policy and operator tooling only.

[coderabbitai]

Warning

Review limit reached

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

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

Run ID: 97a18497-dddc-47fa-aae6-aad828b27db6

📥 Commits

Reviewing files that changed from the base of the PR and between b6513f1 and 580348e.

📒 Files selected for processing (10)

• .claude/skills/run-pr/SKILL.md
• .github/workflows/pr-branch-sync.yml
• AGENTS.md
• docs/branch-review-ledger.md
• docs/codebase-index.md
• docs/outstanding-issues.md
• docs/process-hardening.md
• scripts/check-github-action-pins.mjs
• scripts/sync-open-pr-branches.mjs
• tests/sync-open-pr-branches.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/retire-bot-branch-sync-20260727

---

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

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.