docs(evidence): re-verify meta-description finding 18dd05c10709 against current main and live - #73
Conversation
…st 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: 50 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: 27f71444d0
ℹ️ 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".
|
|
||
| 1. `npm run check` on the current working tree: PASS — the "Meta descriptions | ||
| (dogfood)" guard in `scripts/check-site.mjs` confirms each of the five pages | ||
| carries exactly one non-empty description tag in its head, within a |
There was a problem hiding this comment.
If a description tag is moved below </head> but remains elsewhere in the document, npm run check still passes because scripts/check-site.mjs:1095 searches the complete pageHtml rather than an extracted head. This makes the new assertion that CI confirms every description is “in its head” inaccurate and leaves the stated regression guarantee unenforced; either restrict the guard to each page's <head> or describe it as a whole-document check.
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bff2631304
ℹ️ 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 (1cc7a4e, "fix(public): point | ||
| appraisal-page canonicals and JSON-LD @ids at the clean /audit URL (#56)") after |
There was a problem hiding this comment.
The receipt identifies 1cc7a4e as the current origin/main head, but this commit is based on 6a914b6, which already includes ce02df9 and 6a914b6 after that hash. Consequently, the recorded revision does not identify the working tree on which the stated npm run check result was obtained, making this evidence entry irreproducible as written; record 6a914b6 (or explicitly distinguish the tested tree from the older source baseline).
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b418c5b5af
ℹ️ 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".
| five further commits touched the home page (tap-target sizing, Agent Desk | ||
| de-indexing, AI-answer source declarations, footer link, canonical/JSON-LD | ||
| cleanup) — none of which was allowed to regress the guarantee. Three checks: |
There was a problem hiding this comment.
The history does not show five commits touching the homepage: between the previous verification and 1cc7a4e, only f9f0b0f changes public/index.html (and ac05bec changes its supporting CSS), while the Agent Desk de-indexing, AI-source declaration, and canonical/JSON-LD commits modify other surfaces such as agent-desk.html, llms.txt/offer.md, and audit.html. Because this file is an evidence receipt describing the regression exposure that was rechecked, either describe these as broader site changes or list only the commits that actually affected the homepage.
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: eaf5f91875
ℹ️ 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".
| 2. Served-bytes check: `src/worker.js` serves `public/index.html` verbatim at | ||
| `/` and `/index.html` through the ASSETS binding (no transformation can | ||
| strip the tag), and `public/index.html` carries exactly one |
There was a problem hiding this comment.
/index.html served-bytes claim
The deployed routing does not serve the page bytes directly at both paths: the live routing probe recorded in docs/evidence/internal-links-2026-08-09.md:79-85 shows /index.html returning 307 Location: /, with only / serving the final document. Because env.ASSETS.fetch(request) applies that redirect behavior, this step cannot claim a verbatim response at /index.html; limit the statement to / or explicitly record the redirect.
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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
1 participant
Dogfood finding 18dd05c10709 ("Missing meta description on home", audit 20260808T074205Z-msk2fl3n) was already fixed and closed by PR #21, with a CI guard and live verification recorded in this same evidence file. This lane re-checks the item against the current origin/main head (1cc7a4e) and finds nothing further to change:
public/index.htmlcarries exactly one non-emptymeta name="description"(150 chars) in its head; the guard inscripts/check-site.mjs("Meta descriptions (dogfood)") enforces exactly-once, non-empty, ≤160 chars, unique per page for all five public pages.src/worker.jsservespublic/index.htmlverbatim at/and/index.htmlvia the ASSETS binding — no transformation can strip the tag.npm run checkpasses on this tree (plustest:headings,test:sitemap,test:contractall green).https://tinystudio.io/serves the description today.No code change is needed; this commit appends the 2026-08-11 re-verification record to
docs/evidence/meta-descriptions-2026-08-09.md, following the repo's established closeout convention for this finding.