docs: prevent in-flight branch sync churn

[BigSimmo]

Summary

• require branch-sync operators to inspect the current head's required CI before mutating it
• let behind-but-clean runs settle and perform one late sync after review/fix work is assembled
• keep cancel-in-progress enabled and reserve immediate preemption for blocking conflicts or explicit requests
• archive Revert "perf: lazy-load heavy components, memoize SourceImage, optimize lucide-react" (#133) #145

Verification

• npm run check:outstanding-issues -- --base-ref origin/main
• npx prettier --check AGENTS.md
• npm run check:branch-review-ledger
• git diff --check
• verify:pr-local not run: documentation/process guidance only; no source, runtime, test, workflow, dependency, or build behavior changed.
• UI verification not run: no UI behavior changed.

Risk and rollback

• Risk: low; process-only guidance could delay a sync that an operator intended immediately. The rule explicitly permits immediate sync for a blocking conflict or an explicit user request.
• Rollback: revert this PR to restore the prior push-only anti-churn wording.
• Provider or production effects: GitHub branch/PR documentation only; no provider mutation beyond this authorized PR workflow.

RAG impact: no retrieval behaviour change — process documentation only.

[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:7 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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

Run ID: ddc34541-2a92-47a4-8d23-d6f3034dd4e4

📥 Commits

Reviewing files that changed from the base of the PR and between 41f0712 and 4fdc4ba.

📒 Files selected for processing (6)

• .claude/skills/run-pr/SKILL.md
• AGENTS.md
• docs/branch-review-ledger.md
• docs/outstanding-issues.md
• scripts/sync-open-pr-branches.mjs
• tests/sync-open-pr-branches.test.ts

---

_{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 ↗︎.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:2081b03c3b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[BigSimmo]

@cursoragent fix merge conflict

[cursor]

Merge conflict resolved on PR #1492.

• Merged origin/main (fbe58d80) into codex/sync-ci-anti-churn — clean auto-merge (no conflict markers)
• Pushed tip c6e46707
• PR is MERGEABLE again (mergeStateStatus: BLOCKED only until required checks finish)

#1492