docs: align reconciliation findings and review evidence

[BigSimmo]

Summary

• Replace the stale combined diagnosis for issue Bump @types/react from 19.2.16 to 19.2.17 #18 with the current-main, mechanism-specific findings already landed by PR Document rejected RAG canary findings #1093.
• Record the completed exact-head review and merge proof for PR fix(ui): restore edge-to-edge phone search dock (no white strip) #1090.

Why

The correction preamble and #18 row disagreed, and the required review-ledger evidence for PR #1090 needed to be durable.

Verification

• npx prettier --check docs/outstanding-issues.md docs/branch-review-ledger.md — passed.
• git diff --check — passed.

Checks not run

• Source, build and browser suites were not rerun because this PR changes documentation only. PR fix(ui): restore edge-to-edge phone search dock (no white strip) #1090's local Chromium/WebKit and refreshed hosted checks are recorded in the ledger row.

RAG impact: no retrieval behaviour change — documentation only.

Risk and rollback

• Risk: documentation accuracy only.
• Rollback: revert this PR.
• Provider/production effects: none.

---

Note

Low Risk
Markdown-only tracking updates; no application, RAG, or deployment behavior changes.

Overview
Documentation-only alignment after PR #1093 and the merged phone-dock work.

docs/outstanding-issues.md — Issue #18 no longer treats lithium, ADHD, and metabolic misses as a single extractive-composer defect. The row now records mechanism-specific current-main findings (lithium: unrelated-table retrieval fast-path; ADHD: chart-heavy source + extractive budget; metabolic: correct source but schedule-free prose selection), notes the reverted lithium guard pending #51 canary stability, and points at runs and PR #1093 instead of the old run #61 composer diagnosis.

docs/branch-review-ledger.md — Adds a completed ledger entry for PR #1090 (cursor/fix-phone-dock-edge-1b1d): merge outcome, safe-area/edge-to-edge dock behavior, merge-behind-main handling, and verification checks.

^{Reviewed by Cursor Bugbot for commit c7e50fd. Configure here.}

[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: 47 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: e7dc3ce2-ad8e-4f6c-9ce3-bc30175a5f20

📥 Commits

Reviewing files that changed from the base of the PR and between 09028ef and c7e50fd.

📒 Files selected for processing (2)

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/group1-ledger-inventory

---

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