docs(evidence): re-verify social share image fix on current main and live - #175
Conversation
…live
Dogfood finding d87d715be3d0 ("Social share image incomplete on home")
was fixed by PR #31 and closed on 2026-08-11/12/13. This lane re-verifies
the fix on the current origin/main head (afb5d49) and the live deployment:
the twelve-tag share set is intact in public/index.html, the CI guard
passes, and the live site serves the complete set with a reachable
1200x630 og-image.png byte-identical to the committed file. No code
change required.
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: 59 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.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
1 participant
Closes dogfood finding d87d715be3d0 ("Social share image incomplete on home", audit 20260808T074205Z-msk2fl3n) as already fixed.
What this PR does
Adds a lane-1 re-verification receipt: the fix from PR #31 (commit
eae1d87) is present on the current origin/main head (afb5d49) and the live deployment still serves the complete twelve-tag Open Graph + Twitter Card set with a reachable 1200x630og-image.png.Verified
public/index.htmlhead carries all twelve share tags exactly once,og:image/twitter:imagebound tohttps://tinystudio.io/og-image.pngwith declared 1200x630.npm run checkgreen on current head (CI guard "Social share tags (dogfood d87d715be3d0)" holds the set in source).GET https://tinystudio.io/→ 200 with full share set in served HTML.GET https://tinystudio.io/og-image.png→ 200image/png, bytes SHA-25693109e72af34c2476f2ddd5a7104352e30c13536677e8c6aa7f80be96b3b08df— identical to committedpublic/og-image.png.Prior closeouts