docs: consolidate remaining reviewed session follow-ups

[BigSimmo]

Summary

• consolidates the unique follow-ups that were not present in the concurrently merged issues: capture the unreadable-CI token, at-risk worktree work, and the unpushed hook fix #1490/issues: re-land the three session findings PR #1490 lost when it was closed #1508 heads
• archives completed rendered-style contract issue chore(deps-dev): bump @types/node from 24.13.2 to 26.0.1 #94 (including closed docs: consolidate remaining reviewed session follow-ups #1509)
• preserves corrected chore(deps-dev): bump prettier from 3.9.0 to 3.9.1 #98 canary evidence, perf: SSR-safe lazy loading, loading skeletons, and SourceImage memo #147 CLS attribution, and unique Harden Playwright cache restore behavior #154-Parse nested JSONB job-status RPC result before completion gate checks #156 follow-ups
• repairs the two mockup-only undefined hover tokens and documents the design-sync triage rule
• supersedes closed fix(ui): repair three dropped CSS custom-property references, and record the defect family #1451, issues: record the withdrawn live-region finding as #151 so it is not re-filed #1502, docs(rag): record refuted lexical probe collapse (#098) #1503, docs(issues): attribute the mobile CLS breach, land its measurement harness, and escalate #150 #1505, and issues: capture three unowned follow-ups (id allocation, --med-accent-soft, mockup hover tokens) #1506

Verification

• npm run check:installed-lock-parity — pass (Node 24/npm 11 lock set)
• node ./node_modules/typescript/bin/tsc --noEmit — pass
• single-file ESLint for the mockup component — pass
• outstanding-issues, branch-review-ledger, docs inventory/links/scripts, Prettier, and diff guards — pass
• focused design-token Vitest — not run locally because another worktree held the repository Playwright lease; exact-head hosted CI required

RAG impact: no retrieval behaviour change — documentation evidence only; protected retrieval source is unchanged.

Risk

Documentation and design-scratch mockup only. No production route, provider, API, schema, migration, or deployment change.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[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: 42 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: ebb09109-aff7-40b1-96ef-67cde7b9952f

📥 Commits

Reviewing files that changed from the base of the PR and between c101137 and 9eb45c8.

📒 Files selected for processing (2)

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

---

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

[BigSimmo]

Temporarily closing during the owner-authorized one-at-a-time merge sweep so #1507 can finish against a stable base. This branch and all commits are preserved; its unique issue-ledger closure will be reviewed and consolidated in order.

[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 ↗︎.