docs: archive completed CI tasks

[BigSimmo]

Summary

• archive perf: lazy-load heavy components, memoize SourceImage, optimize lucide-react #133 after validating the removal of merge=union, the outstanding-ledger merge guard, and the Prettier exclusion on current main
• archive Fix API contract semantics and pagination metadata #135 after validating that API-only App Router edits remain outside ui_changed and the focused scope self-test passes
• preserve both IDs and their concise resolution evidence in the append-only archive

Verification

• npm run check:outstanding-issues -- --base-ref origin/main
• npm run check:ci-scope
• npm run check:branch-review-ledger
• git diff --check

Risk and rollback

Documentation-only ledger reconciliation. Revert this PR to move the rows back to the open table.

RAG impact: no retrieval behaviour change — issue-ledger 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:18 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: c80f683c-5688-4fae-a357-3c9c89049c18

📥 Commits

Reviewing files that changed from the base of the PR and between 55c3c55 and 6fc6a75.

📒 Files selected for processing (2)

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

---

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