docs(ledger): record PR #1222 prlanded squash merge

[BigSimmo]

Summary

• One append-only row in docs/branch-review-ledger.md closing the loop on PR fix(chrome): hide and return the universal header on scroll at every breakpoint #1222 (cross-breakpoint header hide/reveal), which squash-merged as 0b82a826. Same post-merge convention as docs: prlanded ledger for reconciliation tooling PR #1203 #1216, docs(ledger): record #1214 prlanded merge and #1190 close #1221, and docs: record PR #1213 prlanded merge superseding #1188 #1225.
• Records the merged head, the squash SHA, empty two-dot content diff against main, remote branch deletion, the green required contexts, why skip-branch-sync was applied, and the post-merge worker-image Docker Hub flake so nobody re-investigates it as a regression.

Verification

• npm run check:branch-review-ledger — 923 records, union merge active, no conflict markers or exact duplicates.
• npx prettier --check docs/branch-review-ledger.md.

Nothing else applies: the diff is a single documentation line, with no source, schema, or configuration change.

Risk and rollout

• Risk: none. Documentation only, appended to an append-only ledger protected by the union merge driver.
• Rollback: revert the commit.
• Provider or production effects: None.

  

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

[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: 36 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: 732fa2d8-b36d-43aa-be4c-20e9bfe2a6f9

📥 Commits

Reviewing files that changed from the base of the PR and between e7e60c6 and 0eaa3a6.

📒 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/ledger-pr1222-landed-4fd7

---

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