docs(evidence): re-verify render-blocking finding b8f6046e942a on current main and live (2026-08-14)

[nish3451]

What

Re-verification lane for dogfood finding b8f6046e942a ("Render-blocking
resources on home", audit run 20260808T074205Z-msk2fl3n). The finding was
fixed by PRs #20/#23 and last re-verified on 2026-08-13; this lane re-checks
on the current origin/main head (0ff0694) and against the live deployment.

Verdict

The finding stays closed — no code change needed.

• npm run check:render-blocking (real Chromium, production CSP, css2
  delayed 2500ms): all six pages PASS — css2 non-blocking, FCP never waits
  (home 240ms), only same-origin stylesheets block, promoted sheet applied.
• npm test: 117 tests, 0 failures.
• Live (real Chromium, unthrottled): css2 non-blocking on all six pages,
  FCP never waits for it, fonts load (Karla/Fraunces), promoted sheet
  applies, only same-origin stylesheets render-blocking.
• Live HTML is byte-identical to public/ on this head (no drift).

Files

• docs/evidence/render-blocking-fonts-2026-08-08.md — appended the
  2026-08-14 closeout re-verification receipt.
• .lane/reports/reverify-render-blocking-b8f6046e942a-2026-08-14.md —
  lane report (evidence only, no code change).

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 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: defaults

Review profile: CHILL

Plan: Free

Run ID: 5744687c-5b30-4fc9-8b58-3097259469fa

📥 Commits

Reviewing files that changed from the base of the PR and between 0ff0694 and 24d8f58.

📒 Files selected for processing (2)

• .lane/reports/reverify-render-blocking-b8f6046e942a-2026-08-14.md
• docs/evidence/render-blocking-fonts-2026-08-08.md

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

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