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

[nish3451]

Closes dogfood item [dogfood b8f6046e942a] Render-blocking resources on home.

The code-side fix (PRs #20 and #23) and its CI enforcement remain intact on current origin/main (885a7a9). This lane re-confirmed all three legs of the guarantee against the current head and the deployed site:

1. Code: the Google Fonts css2 stylesheet is still fetched via rel=preload as=style (non-blocking) with same-origin fonts.js promotion and a <noscript> fallback on all six public pages; shared.css carries no @import chain; the worker still serves /fonts.js from its asset allow-list.
2. CI: npm run check:render-blocking (real Chromium, production CSP, css2 delayed 2500ms) — all six pages PASS: css2 non-blocking, first-contentful-paint never waits for it (homepage 296ms, audit 132ms, desk 104ms, pricing 200ms, specimen 396ms, brief-requested 252ms vs css2 at 2500ms), no render-blocking resources other than same-origin stylesheets, promoted sheet applied.
3. Live (unthrottled Chromium, production CSP verified via curl -sI https://tinystudio.io/): css2 renderBlockingStatus non-blocking on all six deployed pages, only same-origin stylesheets render-block, fonts load (Karla/Fraunces) and apply under the CSP.

Full suite green on this head: npm test — static guards passed, 105 tests, 0 failures.

No code changes were needed; this PR appends the 2026-08-13 closeout re-verification receipt to docs/evidence/render-blocking-fonts-2026-08-08.md.

[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: 33 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: c391383a-310e-4f8e-8abe-4cffacf4c0b2

📥 Commits

Reviewing files that changed from the base of the PR and between 885a7a9 and 06d8510.

📒 Files selected for processing (1)

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