docs(ledger): prlanded #1656 Docker delivery hardening

[BigSimmo]

Summary

• Append prlanded rows for PR Harden Docker delivery pipeline and worker graceful shutdown #1656 (Docker delivery hardening), PR fix(settings): unfreeze the desktop settings panel and keep its rail reachable #1641 (settings panel unfreeze), and PR refactor(viewer): Phase 1 DocumentViewer shell extraction #1665 (viewer Phase 1 shell extract) after each squash-merge landed and the remote feature branch was deleted.

Verification

• prlanded content / remote-branch checks for Harden Docker delivery pipeline and worker graceful shutdown #1656, fix(settings): unfreeze the desktop settings panel and keep its rail reachable #1641, refactor(viewer): Phase 1 DocumentViewer shell extraction #1665
• Verification not run: docs/ledger-only append; verify:pr-local optional for this scope
• UI verification not run: no UI changes
• No provider-backed checks run

Risk and rollout

• Risk: none (append-only review ledger)
• Rollback: revert the ledger row commits
• Provider or production effects: None

Notes

• Created during Run PR / babysit sweep so merges are recorded without ledger-only tips on product PRs.

[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:54 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: b005638f-651d-41dd-946e-561e834a4ef1

📥 Commits

Reviewing files that changed from the base of the PR and between 097dfd2 and 7520f46.

📒 Files selected for processing (1)

• docs/branch-review-ledger.md

---

_{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]

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, add credits to your account and enable them for code reviews in your settings.