docs: record PR batch #883–#888/#891 merge babysit

[BigSimmo]

Summary

• Append a docs/branch-review-ledger.md row for the screenshot-queue merge babysit covering PRs Fix(differentials): route "Compare selected" directly to resolved presentation workflow #883–fix(worker): preserve distinct image placements in cheap image de-duplication #888 and superseding fix(ci): checkout PR policy from github.workflow_sha #891.
• Records merged/closed outcomes, review findings addressed, and verification evidence.

Verification

• Ledger row inserted under Review Records with date, refs, outcome, and checks
• Verification not run: documentation-only change; no runtime behavior changed.

Risk and rollout

• Risk: low; documentation ledger only.
• Rollback: revert this commit.
• Provider or production effects: None.

  

[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 ↗︎.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 1 minute

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: 9def58c3-36b0-46c2-a3c9-ebcc405dc82e

📥 Commits

Reviewing files that changed from the base of the PR and between 8b0a600 and 68993b5.

📒 Files selected for processing (1)

• docs/branch-review-ledger.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/branch-review-ledger-9b6d

---

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