docs(evidence): re-verify canonical-URL finding 6631c0ab0454 against current main and live (2026-08-17, lane 1) - #241
Conversation
…current main and live (2026-08-17, lane 1)
|
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: 8 minutes Limit details: You’ve used all 1 included review currently available under your plan. 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 |
1 participant
Item
[dogfood 6631c0ab0454] Missing canonical URL on home(audit run20260808T074205Z-msk2fl3n).Verdict: already fixed and live — this PR is the 2026-08-17 receipt
The finding was closed by PR #29 ("seo: add canonical URLs to the five public
pages") and re-verified on 2026-08-09, 08-11 (twice), 08-12, 08-13 and 08-14.
Re-confirmed today against origin/main head
3dc5856and the deployed site.No production file changed.
1. Source + CI
The full
npm testchain passes on3dc5856. This host hasnodev22.23.1but no
npmbinary, so each script in the chain was run directly:node scripts/check-site.mjs→ "TinyStudio.io checks passed", headings 6/6,sitemap 7/7, worker 80/80, ui 16/16, contract 8/8, first-viewport 4/4,
narrow-pages 34/34 rows PASS, narrow 11/11 rows PASS. The
"Canonical URLs (dogfood)" guard still enforces exactly one non-commented
<link rel="canonical">inside<head>per page, a non-empty href pointing atthe page's canonical
https://tinystudio.ioaddress (home:https://tinystudio.io/), and no URL duplicated across pages.2. Live (headless Chromium, Playwright 1.62.1)
/(home)https://tinystudio.io//audithttps://tinystudio.io/audit/agentshttps://tinystudio.io/agents.html/pricinghttps://tinystudio.io/pricing.html/specimenhttps://tinystudio.io/specimen.html/agent-desk(retired, noindex)https://tinystudio.io/agent-deskSix served pages, six distinct canonical hrefs. Home serves
<link rel="canonical" href="https://tinystudio.io/">, unchanged from everyprior receipt. The
.htmlforms still 307 to their clean twins andwww.still 301s to the apex the home canonical names.
3. Deployment parity
Live matches origin/main byte-for-byte on all five public pages plus
/agent-desk—curl -sLthrough the.html307s diffed againstpublic/*.htmlshows zero differences.One thing genuinely changed since the 2026-08-14 receipt
At 08-14 the home canonical was correct but not exclusive: the retired
public/agent-desk.htmldeclaredcanonicalandog:urlpointing athttps://tinystudio.io/, the home page's own address, and the dogfood guardnever caught it because its page list is the five public pages. PR #229
(
798cd71a) repointed both at the cleanhttps://tinystudio.io/agent-deskandextended the retired-desk guard to require exactly one canonical and one
og:urlnaming that address. Verified here:git show 20b7cc6:public/agent-desk.htmlcarries the apex-root canonical, the file on3dc5856carries/agent-desk, and the live page serves/agent-deskwithrobots: noindex, nofollow. The home page's canonical is now the only claim onhttps://tinystudio.io/anywhere in the served site.Range reviewed
33 commits since the last re-verify head
20b7cc6; six touchedpublic/orscripts/check-site.mjs(#176, #212, #211, #213, #229, #238).git log -p 20b7cc6..3dc5856 -- public/index.htmlcontains exactly one hunk —the
autocomplete="email"attribute on the lead form's email input — so thehome-page canonical line is byte-identical to the one every prior receipt
measured, and the canonical guard itself is untouched in range.
Files
docs/evidence/canonical-urls-2026-08-09.md— appended the 2026-08-17re-verification section to the standing receipt.
.lane/reports/docs-canonical-rereverify-2026-08-17.md— lane report(lane-unique path, no shared report file touched).