docs: close rejected Playwright cache proposal (archive #136)

[BigSimmo]

Motivation

• Archive outstanding issue Harden RAG telemetry and production guardrails #136 after an end-to-end benchmark showed the proposed reusable Next build cache for isolated Playwright runs is a net CI loss and would consume shared cache budget.

Description

• Update docs/outstanding-issues.md to move Harden RAG telemetry and production guardrails #136 into the resolved/archive section and document the measured outcome and rationale for rejecting the cache (warm build saved ~34s for an ~804MB cache; persisting it per-commit would risk evicting Playwright browser caches).

Testing

• Ran npm run check:outstanding-issues, npm run format, npm run format:check, and git diff --check, all of which passed locally and the outstanding-issues self-check passed.

---

Codex Task

[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:32 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: 0858105e-1be2-49d9-b848-5bf32b57fc8a

📥 Commits

Reviewing files that changed from the base of the PR and between 4b5af90 and 4b3200f.

📒 Files selected for processing (2)

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

---

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