docs(evidence): re-verify canonical-URL finding 6631c0ab0454 against current main and live (#169) - #170
Conversation
…current main and live (#169) Re-verified the home-page canonical the finding flagged (PR #29 fix) against origin/main head dc1542a 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 in real Chromium, 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: 30 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 (1)
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-verifies dogfood finding 6631c0ab0454 ("Missing canonical URL on home") against current origin/main head
dc1542aand the deployed site, following the same evidence pattern as #121/#75/#38.Checks
npm testpasses on this head — check (canonical guard requires exactly one non-commented<link rel="canonical">inside<head>per page, non-empty href, no URL duplicated across pages), headings 6/6, sitemap 7/7, worker 72/72, ui 16/16, contract 8/8.https://tinystudio.io/.index/audit/agents/pricing/specimen.html(following 307s to clean twins) diff byte-identical against source on this head.The only commit since the last re-verify (dc1542a, apple-touch-icon guard for all seven pages) touches no canonical link or guard, so the home-page canonical is byte-identical to every prior receipt.
Finding remains closed: code (PR #29), CI guard, and live deployment all confirmed.