docs(evidence): re-verify social share image fix on current main and live - #221
Conversation
…live (#221) Lane-1 re-verification of dogfood finding d87d715be3d0 (social share image incomplete on home). The fix (PR #31, eae1d87) is present on the current origin/main head 9944fec, the source guard passes, and the live deployment serves the complete twelve-tag share set with a reachable 1200x630 og-image.png byte-identical to the committed file. 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: 28 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 |
1 participant
Lane-1 re-verification of dogfood finding d87d715be3d0 ("Social share image incomplete on home").
The fix (PR #31, commit
eae1d87) was verified and closed on 2026-08-11 (PR #76), 2026-08-12 (PR #122), 2026-08-13 (PR #168) and 2026-08-14 (PR #175). This PR re-verifies on the current origin/main head9944fecand the live deployment so the item can close with a reason and cannot re-open by drift.What was verified (2026-08-15)
eae1d87is an ancestor of the current head.public/index.htmlshare tags byte-identical to the fix commit (zeroog:/twitter:lines changed by later commits).npm run checkpasses on current head, including the "Social share tags (dogfood d87d715be3d0)" guard.public/og-image.png: valid non-interlaced 1200x630 PNG, SHA-25693109e72af34c2476f2ddd5a7104352e30c13536677e8c6aa7f80be96b3b08df.GET https://tinystudio.io/→ 200, complete twelve-tag share set in<head>,og:urlhttps://tinystudio.io/.GET https://tinystudio.io/og-image.png→ 200image/png, 345,042 bytes, SHA-256 identical to the committed file.No code change required — the finding remains fixed and closed.