docs(evidence): re-verify internal-links finding 996dffe45ef7 against current main and live - #80
Conversation
… current main and live The code-side fix (PR #34) and CI enforcement (the 'Internal page links (dogfood 996dffe45ef7)' guard in scripts/check-site.mjs) for dogfood finding 996dffe45ef7 ('Redirecting internal links on home') are already merged in origin/main. This lane re-verified the guarantee still holds after the page edits that landed since the first receipt (canonicals on the appraisal page, the homepage footer daily-reads link, the 44px tap-target pass, the Agent Desk de-index, the AI-answer source pages): - npm run check passes on all five public pages: no anchor targets any .html page name on any of them. - npm test passes (source checks + heading-hierarchy, sitemap, agent-worker, agent-UI and product-contract suites; 90 tests total). - Fresh live measurement of the deployed pages in real Chromium (2026-08-11) confirms the same: every internal link on all five pages returns HTTP 200 with no Location header (probed with maxRedirects 0) — zero redirecting internal links — including the home page the finding flagged (https://tinystudio.io/). The .html forms the pre-fix home linked at still 307-redirect to their clean twins, but no page links to them. Nothing further to change; the receipt now records the closeout on the current head (8b42e0a) so the finding cannot be re-opened by tracker drift.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 15 seconds 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: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
1 participant
Re-verification closeout for dogfood finding 996dffe45ef7 ("Redirecting internal links on home", audit 20260808T074205Z-msk2fl3n).
The code-side fix (PR #34) and CI enforcement (the "Internal page links (dogfood 996dffe45ef7)" guard in scripts/check-site.mjs) were already merged; this PR records that the guarantee still holds on the current head (8b42e0a) and the live deployment, following the repo's closeout pattern.
Verified on current main (8b42e0a)
Verified live (2026-08-11, real Chromium via Playwright)
Nothing further to change; this closes the finding against current main and live.