docs(evidence): re-verify canonical-URL finding 6631c0ab0454 against current main and live (2026-08-14) - #209
Conversation
…current main and live (2026-08-14) Re-verified the home-page canonical the finding flagged (PR #29 fix) against origin/main head 20b7cc6 and the deployed site: npm test passes with the check-site.mjs canonical guard, all five public pages serve exactly one canonical link in head, and live matches source byte-for-byte. 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: 31 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 |
1 participant
Re-verification of dogfood finding 6631c0ab0454 ("Missing canonical URL on home") against current origin/main (20b7cc6) and the deployed site.
Verdict
Finding already closed by PR #29 and confirmed live; nothing to fix. This lane re-confirms the three halves:
npm testpasses on 20b7cc6. The "Canonical URLs (dogfood)" guard inscripts/check-site.mjsenforces exactly one non-commented canonical link inside<head>per page, a non-empty href at the page's canonicalhttps://tinystudio.ioaddress (home:https://tinystudio.io/), and no URL duplicated across pages.<link rel="canonical" href="https://tinystudio.io/">, unchanged from every prior receipt.Commits since the last re-verify (dc1542a..20b7cc6): 51d5849 (#151) and 20b7cc6 (#208). No canonical-line change in
public/index.html; the onlyscripts/check-site.mjsedit is a comment rewrite.Change
docs/evidence/canonical-urls-2026-08-09.md: appended the 2026-08-14 re-verification section.