docs(evidence): re-verify favicon rel=icon finding 017eb201fc against current main and live (2026-08-15)

[nish3451]

Summary

Re-verification of review-queue item 017eb201fc — "[unreviewed-by-opus] 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: closed. The failure mode no longer occurs, on source and on the live site. The code-side fix is already merged in origin/main (PRs #85 and #113), and the CI guard in scripts/check-site.mjs (lines 1375-1420) enforces exactly one <link rel="icon" href="/favicon.svg"> in the head of all seven served pages.

Verification (2026-08-15, current head 23e24d6)

1. Source: npm run check passes ("TinyStudio.io checks passed."); npm test passes (exit 0, 121 subtests, 0 failures).
2. Drift: git diff 5770bf3..HEAD over public/, scripts/check-site.mjs, src/worker.js contains zero favicon/rel=icon changes since the 2026-08-14 receipt (PR docs(evidence): re-verify favicon rel=icon finding 017eb201fc against current main and live #182).
3. Live (Playwright 1.62.1, headless Chromium): all seven pages (/, /audit, /agents, /pricing, /specimen, /brief-requested, /agent-desk) return 200 with exactly one rel=icon link in head pointing at /favicon.svg; zero /favicon.ico requests on any page load; zero page/console errors.
4. Assets: /favicon.svg → 200 image/svg+xml, byte-identical to committed file (SHA-256 998e43ad83f78adcd8a75fb37a87657ba2289b760470f42583c7fab166d9184c); /favicon.ico → 404, now never referenced.

Files

• docs/evidence/favicon-rel-icon-rereverify-2026-08-15.md — evidence receipt
• .lane/reports/docs-favicon-rel-icon-rereverify-2026-08-15.md — lane report

Summary by CodeRabbit

• Documentation
  • Added verification records confirming the favicon fix across seven live pages.
  • Documented successful source checks, test results, asset probes, browser verification, and reproducibility steps.
  • Confirmed a single favicon reference, no legacy favicon requests, and matching favicon asset content.

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

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 847cf843-8fba-45a5-8fb6-eeca7d41cca0

📥 Commits

Reviewing files that changed from the base of the PR and between 23e24d6 and cd04815.

📒 Files selected for processing (2)

• .lane/reports/docs-favicon-rel-icon-rereverify-2026-08-15.md
• docs/evidence/favicon-rel-icon-rereverify-2026-08-15.md

---

📝 Walkthrough

Walkthrough

The change adds two evidence receipts for the favicon fix. The receipts record source checks, test results, browser verification across seven pages, asset probes, matching asset bytes, and zero /favicon.ico requests.

Changes

Favicon verification

Layer / File(s)	Summary
Favicon verification receipts .lane/reports/docs-favicon-rel-icon-rereverify-2026-08-15.md, docs/evidence/favicon-rel-icon-rereverify-2026-08-15.md	The receipts document source and drift checks, passing npm run check and npm test, live Chromium measurements across seven pages, successful asset probes, matching asset bytes, and issue closure.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to cd048

This PR adds verification records for an already-resolved favicon issue and does not change application behavior or production assets. No actionable merge-blocking risk remains beyond normal checks.

---

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