Queue outstanding-issues request: mobile CLS regression on /

[BigSimmo]

Summary

• Queues a single immutable /issues inbox request (docs/outstanding-issues-inbox/d92786de-de31-4118-84cc-0a9098e7f2e0.json) documenting a real, reproducible mobile CLS regression on / discovered while working PR Simplify Differentials compare-queue hero card #2050.

Context

PR #2050 (an unrelated Differentials compare-queue UI simplification) hit a Lighthouse budget CI failure: mobile-root CLS measured 0.236 against the committed 0.013 baseline, identical across two independent CI re-runs on two different head SHAs, with the correctly pinned/matching browser (the check graded rather than refusing for evidence-incomplete/browser-drift). PR #2050's diff is a Server Component change on a completely different route with zero client-bundle delta, so it cannot be the cause.

This matches docs/outstanding-issues.md item #147 ("Mobile CLS breaches four routes"), marked RESOLVED 2026-08-12 via PR #1616, which verified home-page mobile CLS at exactly 0.013 — the same number now used as the CI baseline. Since main's own push-triggered CI skips the Lighthouse budget job entirely (it only runs on pull_request events with UI_CHANGED=true), a regression here could land on main undetected by any merge that doesn't itself touch UI-changed paths.

This PR only queues the tracking request — no source changes, no attempt to fix the regression itself (out of scope here; needs a proper bisect/investigation).

Verification

• npm run issues:add — the script's own request validation passed and reported the request as merge-safe.
• Verification not run beyond that: this is a single generated, schema-validated JSON file under docs/outstanding-issues-inbox/, added via the repo's own scripts/ledger-inbox.mjs add tooling. No source/build/test surface is touched.

Risk and rollout

Not applicable — append-only tracking document, no code/behavior change. Reconciliation into the canonical docs/outstanding-issues.md ledger happens via a separate, deliberately serialized npm run issues:reconcile run per repo convention.

Notes

• Full investigation detail, CI run IDs, and cross-references are in the queued request file itself.

---

Generated by Claude Code

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

[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]

Caution

Review failed

The head commit changed during the review from 42c5c61 to 40ac5e0.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/cls-regression-issue-log

---

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