docs(evidence): close out social share image finding d87d715be3d0 against current main and live - #76
Conversation
…inst current main and live
![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: 7 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: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0cac9dd03a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| current main, and the live deployment now serves the complete Open Graph + | ||
| Twitter Card set — each tag exactly once, in `<head>`, bound to the page's own | ||
| metadata, pointing at a reachable 1200x630 current-offer `og-image.png` that | ||
| is byte-identical to the committed file — on the home page and on all four | ||
| sibling public pages. |
There was a problem hiding this comment.
Under the deployment state this receipt records, the live /audit page does not satisfy this all-five-pages conclusion: the note at lines 210–216 says its og:url is still https://tinystudio.io/audit.html, while the browser lands on /audit and the current guard expects that clean URL. The closeout should either report that live mismatch in the results and limit the successful conclusion to the homepage, or wait until the pending deployment before claiming every sibling page has a share set bound to its own address.
Useful? React with 👍 / 👎.
| pages are the static files verbatim through the Worker's ASSETS binding | ||
| (`src/worker.js`), so the source guard and the served bytes cannot drift | ||
| unless the Worker's asset serving itself changes. The measurement does not |
There was a problem hiding this comment.
The source guard only validates the checked-out files; the ASSETS binding can serve an older or otherwise different deployed artifact without src/worker.js changing. This receipt demonstrates that exact case in lines 210–216, where live /audit differs from current main because deployment is lagging, so saying source and served bytes cannot drift incorrectly turns a CI source check into a deployment guarantee. Keep stale/failed deployments and CDN versions as explicit reasons that the live browser check remains necessary.
Useful? React with 👍 / 👎.
…current main and live (#168) Judges the lane-1 item for dogfood finding d87d715be3d0 ("Social share image incomplete on home", audit 20260808T074205Z-msk2fl3n). The finding was fixed by PR #31 (eae1d87), verified live by PR #76, and engine-rerun-confirmed by PR #122; this receipt re-verifies on the current head (5209ec7) and the live deployment that the twelve-tag share set, the CI guard, and the reachable 1200x630 og-image.png all still hold. Nothing further to change; item closes with a reason. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
1 participant
What
The dogfood audit run 20260808T074205Z-msk2fl3n found "Social share image
incomplete on home" (finding d87d715be3d0): the home page served zero
og:/twitter: tags. The fix (PR #31, merged) added the complete share set to
all five public pages, regenerated og-image.png for the current offer, and
added the check-site.mjs social-tag guard — but unlike every sibling finding
from the same audit run, this one never received its closeout evidence doc.
This PR writes that closeout: a live-deployment measurement of the deployed
site (headless Chromium, all five pages), plus source checks on the current
head.
Evidence (2026-08-11)
in
<head>and once in the full document,og:description== metadescription, zero console/page errors.
https://tinystudio.io/og-image.png: 200, image/png, valid 1200x630 PNG,byte-identical to the committed file (SHA-256
93109e72af34c2476f2ddd5a7104352e30c13536677e8c6aa7f80be96b3b08df); pixel
sample matches the current cream/ink/brass palette (current-offer card, not
the retired Agent Desk artwork).
npm run checkand fullnpm testpass on current main (ce02df9):headings 6/6, sitemap 7/7, worker 53/53, UI 16/16, contract 8/8.
f9f0b0f + 1cc7a4e; the live audit page still serves the
.htmlog:url formthat main already corrected — neither commit touches the home page, which
is the finding's scope and is already correct on both main and live.
Files
docs/evidence/social-share-image-2026-08-11.md(new, 221 lines)