docs: retire constrained GitHub guard tasks

[BigSimmo]

Summary

• archive Remove legacy clinical-chat compat tokens (teal, ready, amber, document) #129 after validating the repository's constrained branch-sync procedure: merge-tree diagnosis first, authenticated updates only, and a local merge fallback for custom-driver false conflicts
• archive Harden Playwright cache restore behavior #132 under its explicit-limitation outcome: retain the tested local auto-merge sentinel, document missing-hook/missing-gh blind spots, and rely on ordinary unprivileged PR CI for server-side formatting enforcement
• avoid privileged pull_request_target execution of PR-head formatting code

Verification

• npm run guard:push:self-test
• npm run test -- tests/guard-push.test.ts tests/sync-open-pr-branches.test.ts — 2 files, 24 tests passed
• npm run check:github-actions
• npm run check:outstanding-issues -- --base-ref origin/main
• npm run check:branch-review-ledger
• git diff --check

Risk and rollback

Documentation-only disposition of already implemented constraints. Revert this PR to restore the two open rows.

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

[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

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:10 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: 02a2b91a-1af9-413f-ab86-e3836bc71a1c

📥 Commits

Reviewing files that changed from the base of the PR and between 58e99b3 and 08eb145.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

---

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