docs: archive verified latency improvements

[BigSimmo]

Summary

• archive PR: Production readiness improvements and E2E fixes #105 after completing its remaining driven-browser LoadingPanel proof
• retain the prior preconnect evidence and record exact desktop/phone chunk-delay results

Browser evidence

• verified project identity clinical-kb:71dfe8ea64e1 at http://localhost:3662
• delayed the exact document-search-results chunk by 1.6 seconds
• observed role=status / aria-label=Loading document results at 1440x900 (315 ms) and 390x844 (123 ms), then observed it clear after chunk execution
• phone pass used keyboard activation, reduced motion, and forced colors; focus ended on Mode Documents and horizontal overflow was 0
• stopped the verified local server after QA

Validation

• npm run check:installed-lock-parity (pass)
• npm run check:outstanding-issues (pass: 59 open, 87 archived)
• npx prettier --check docs/outstanding-issues.md (pass)
• npm run check:branch-review-ledger (pass)
• git diff --check (pass)

Risk and rollback

Documentation-only issue disposition. Revert the commits to restore the open row; no runtime, provider, or API behavior changes.

RAG impact: no retrieval behaviour change — documentation-only issue disposition.

[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:9 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: 441ca938-b89d-4362-a2f9-1d507e8e3ab6

📥 Commits

Reviewing files that changed from the base of the PR and between 445b4ae and 05008bb.

📒 Files selected for processing (2)

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

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:2f18cd7ebf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".