docs(evidence): re-verify favicon rel=icon finding 017eb201fc against current main and live - #182
Conversation
…main and live (2026-08-14)
Re-verifies review-queue item 017eb201fc ("No rel=icon link is served, so
every page load fires a 404 /favicon.ico request") against origin/main head
5770bf3 and the live deployment: npm run check and npm test pass, and a real
Chromium probe of all seven served pages shows exactly one /favicon.svg
rel=icon link each with zero /favicon.ico requests.
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 22 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (2)
Note 🎁 Summarized by CodeRabbit FreeYour 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 |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
1 participant
Re-verification lane for review-queue item 017eb201fc ("No rel=icon link is served, so every page load fires a 404 /favicon.ico request while favicon.svg exists and is allow-listed").
Outcome: already fixed and deployed; re-verified and closed out
The code-side fix is merged in
origin/main: PR #85 (9302611) added<link rel="icon" href="/favicon.svg" type="image/svg+xml" />to the five human-facing pages, and PR #113 (18128e8) extended it to/brief-requestedand added a CI guard inscripts/check-site.mjscovering all seven served pages.Verification performed
npm run checkpasses (exit 0): the "Favicon (dogfood)" guard enforces exactly one/favicon.svgrel=icon link in the head of all seven pages, with a valid git-tracked SVG and worker allow-list entry (src/worker.jsline 61).npm testpasses (exit 0): heading-hierarchy, sitemap, agent-worker, agent-UI, product-contract, viewport, narrow-viewport suites — zero failures (only a pre-existing out-of-scope note that/overflows at 240/260px, which does not gate the exit code)./,/audit,/agents,/pricing,/specimen,/brief-requested,/agent-desk) serve 200 with exactly one rel=icon link in head pointing at/favicon.svg, zero console/page errors, and zero requests to/favicon.ico.https://tinystudio.io/favicon.svg→ 200image/svg+xml, byte-identical to the committed file (SHA-256998e43ad...);/favicon.ico→ 404, now never referenced.Evidence:
docs/evidence/favicon-rel-icon-reverify-2026-08-14.md.