docs(evidence): re-verify structured-data finding 975fdb784275 against current main and live - #124
Conversation
…t 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: 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 |
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.
![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: 161f86e22e
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 | ||
| ship-verification above (81fc379, PR #93). Nine of those commits touched |
There was a problem hiding this comment.
This commit is based on ad9cee3, not 18128e8; six intervening commits are present, including 8606b0c and ed62202, which modify public/audit.html, scripts/check-site.mjs, and related tests. As a result, the later claims that source checks and live byte comparisons cover “this head” only document the older snapshot and do not substantiate the stated closeout against the commit being reviewed. Please rerun and record the verification against the actual parent/current tree, or describe this as a snapshot-only receipt rather than a current-head re-verification.
Useful? React with 👍 / 👎.
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.
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.
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.
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.
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.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7061208bbe
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence since the prior comment is that this version has been rebased again: its parent is now 6864576, which is 13 commits past the recorded 18128e8, and public/audit.html, scripts/check-site.mjs, and scripts/test-agent-ui.mjs differ between those revisions. Consequently, the later assertions that source checks and live byte comparisons cover “this head” still only document the older snapshot and do not verify the commit being reviewed; rerun the checks and live comparison against 16d44a9, or label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 14c1cb630b
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence since the earlier comments is that this revision's parent is now 66aa81e, 14 commits after the recorded 18128e8; those commits modify public/audit.html, scripts/check-site.mjs, and the relevant tests, and the parent now runs 59 worker tests rather than the documented 55. Consequently, the source checks and live byte comparisons described as covering “this head” still verify an older snapshot, so rerun and record them against 66aa81e/4367deb or explicitly label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cb3f1677ba
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence since the earlier comments is that this revision is now based on 941ab68, which is 15 commits past the recorded 18128e8; that interval changes public/audit.html, scripts/check-site.mjs, and the relevant tests, and the current worker suite reports 59 tests rather than the documented 55. Consequently, the source checks and live byte comparisons described as covering “this head” still verify an older snapshot, so rerun and record them against 941ab68/1bd3462 or explicitly label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ac89ffe707
ℹ️ 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".
| `npm test` suite passes (headings 6/6, sitemap 7/7, worker 55, ui 16, | ||
| contract 8). The worker suite grew from 53 to 55 since the last |
There was a problem hiding this comment.
Fresh evidence since the earlier comments is that this revision's parent is now 4e2b94c, 16 commits after the recorded 18128e8; that interval changes public/audit.html, scripts/check-site.mjs, and the relevant tests. Running npm test on the reviewed tree reports 59 worker tests rather than the documented 55, so the source checks and live byte comparisons described as covering “this head” still document the older snapshot and do not substantiate closeout against 27af01a; rerun and record the verification on this revision or explicitly label it as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5f0cc666c2
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence beyond the earlier comments is that this revision is now based on cbefed9, 17 commits after the recorded 18128e8; that interval changes public/audit.html, scripts/check-site.mjs, and the relevant tests, and npm test on the reviewed tree reports 59 worker tests rather than the documented 55. Consequently, the checks and live byte comparisons described as covering “this head” still verify an older snapshot, so rerun and record them against cbefed9/f697473 or explicitly label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3280ddd3f7
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence since the prior comments is that this revision's parent is now 3c56ce3, 19 commits after the recorded 18128e8; that interval modifies public/audit.html, scripts/check-site.mjs, and relevant tests, and npm test on the reviewed tree reports 59 worker tests rather than the documented 55. Consequently, the source checks and live byte comparisons described as covering “this head” still verify an older snapshot, so rerun and record them against 3c56ce3/bcb6848 or explicitly label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e71c405332
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence since the prior comments is that this revision's parent is now aeb34a9, 20 commits past the recorded 18128e8; that interval modifies public/audit.html, scripts/check-site.mjs, and relevant tests, and npm test on the reviewed tree now reports 62 worker tests rather than the documented 55. Consequently, the source checks and live byte comparisons described as covering “this head” still verify an older snapshot, so rerun and record them against aeb34a9/c968f34 or explicitly label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5a060343c4
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence since the earlier comments is that this revision is now based on 586c0f6, 22 commits after the recorded 18128e8; that interval modifies public/audit.html, scripts/check-site.mjs, and relevant tests, and npm test on the reviewed tree reports 62 worker tests rather than the documented 55. Consequently, the source checks and live byte comparisons described as covering “this head” still verify an older snapshot, so rerun and record them against 586c0f6/dea0509 or explicitly label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 180b272f25
ℹ️ 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".
| Re-verified against the current origin/main head (18128e8, "fix(public): | ||
| serve rel=icon on /brief-requested and guard favicon links in | ||
| check-site.mjs (#113)") after 18 commits landed since the 2026-08-11 |
There was a problem hiding this comment.
Fresh evidence since the prior comments is that this revision is now based on 1a992be, 23 commits after the recorded 18128e8; that interval modifies public/audit.html, scripts/check-site.mjs, and the relevant tests, and npm test on the reviewed tree reports 62 worker tests rather than the documented 55. Consequently, the checks and live byte comparisons described as covering “this head” still verify an older snapshot, so rerun and record them against 1a992be/42fed0a or explicitly label this as an 18128e8 snapshot receipt.
Useful? React with 👍 / 👎.
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
What
Re-verifies dogfood finding 975fdb784275 ("Structured data opportunity on home", audit 20260808T074205Z-msk2fl3n) against the current origin/main head (18128e8) and the live deployment, following the repo's established re-verification pattern (prior lanes: PRs #78, #93).
The finding has been closed since PR #32 (code fix) with CI guard and evidence receipts; this lane confirms nothing regressed in the 18 commits since the last closeout (81fc379 / PR #93).
Verification recorded (added to docs/evidence/structured-data-2026-08-09.md)
npm run checkpasses (the "Structured data (dogfood 975fdb784275)" guard: exactly one valid schema.org@graphblock in each page's head, bound to the page's own metadata); fullnpm testpasses (headings 6/6, sitemap 7/7, worker 55, ui 16, contract 8).git show <sha> -- public/over all 18 commits since 81fc379 shows zerold+json/@graph/@id/@typechanges.application/ld+jsonblock in head and in document, graph carries exactly one Organization/WebSite/WebPage with unique@ids, WebPage bound to the page's own metadata (og:title entity-decoded per the guard), no console or page errors.Finding remains closed; nothing further on the finding's page to change.