docs(evidence): re-verify canonical-URL finding 6631c0ab0454 against current main and live - #75
Conversation
…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.
📝 WalkthroughWalkthroughThe documentation adds a closeout re-verification for canonical URLs. It compares current-main source values with deployed values, records live Chromium checks, and documents deployment lag for ChangesCanonical URL verification
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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.
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: 711820d7b4
ℹ️ 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.
This change is applied on top of 6a914b6, but the receipt calls 1cc7a4e the current origin/main head and later claims that live lags main by exactly the two commits ending there. The reviewed history contains ce02df9 and 6a914b6 after 1cc7a4e, so the stated head, “two newest commits,” and conclusion that the checks were run against current main are already stale when this commit lands. Update the recorded head and deployment delta, and run the claimed source checks on that head so this audit evidence remains reproducible.
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.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/evidence/canonical-urls-2026-08-09.md`:
- Around line 133-138: Update the reproduced live-check measurement in the
canonical-URLs document to use an expected URL map, including home as
https://tinystudio.io/ and the current main page as https://tinystudio.io/audit.
Add assertions for HTTP 200, CSP header presence, and exact per-page canonical
href equality against that map while retaining the existing uniqueness and
console/page-error checks.
- Around line 109-116: Correct the “Closeout re-verification” entry and its date
in the canonical-URLs evidence document so it reflects the actual verification
date and deployment state; do not claim completion for a future date. If
verification has not occurred, remove or defer the closeout section until it is
performed.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 42f9482b-7d2a-46e5-b166-fb35d7c7a657
📒 Files selected for processing (1)
docs/evidence/canonical-urls-2026-08-09.md
| ### Closeout re-verification (added 2026-08-11) | ||
|
|
||
| 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 | ||
| five further commits touched the public surface since the 2026-08-09 closeout — | ||
| 95d2248 (preferred source pages for AI answers), c5e2f2b (de-index the retired | ||
| Agent Desk), ac05bec (mobile tap targets: CSS only), f9f0b0f (footer | ||
| attribution link on home), 1cc7a4e (canonical/JSON-LD URL cleanup on /audit). |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Use a valid measurement date before merging.
This review occurs on August 10, 2026, but the section records a completed re-verification on August 11, 2026. August 11, 2026 is in the future. Record the actual execution date and deployment state, or add this closeout after the measurement occurs.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/evidence/canonical-urls-2026-08-09.md` around lines 109 - 116, Correct
the “Closeout re-verification” entry and its date in the canonical-URLs evidence
document so it reflects the actual verification date and deployment state; do
not claim completion for a future date. If verification has not occurred, remove
or defer the closeout section until it is performed.
| 2. Fresh live measurement of the deployed site (2026-08-11, headless Chromium, | ||
| same method as the receipt above, `domcontentloaded` wait, canonical read | ||
| from `document.head` and from the full document, console/page errors | ||
| captured): every page returns 200 with the CSP header, serves exactly one | ||
| canonical link in its head and one across the whole document, and logs no | ||
| console or page errors. Measured canonical hrefs (unique across pages): |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Make the reproduced live check enforce the documented claims.
The shown method does not assert CSP presence or the exact canonical URL for each page. Five incorrect but unique URLs could pass. Add an expected-URL map and assertions for HTTP 200, CSP presence, and the exact per-page canonical, including https://tinystudio.io/ for home and https://tinystudio.io/audit for current main.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/evidence/canonical-urls-2026-08-09.md` around lines 133 - 138, Update
the reproduced live-check measurement in the canonical-URLs document to use an
expected URL map, including home as https://tinystudio.io/ and the current main
page as https://tinystudio.io/audit. Add assertions for HTTP 200, CSP header
presence, and exact per-page canonical href equality against that map while
retaining the existing uniqueness and console/page-error checks.
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. |
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
What
Re-verification lane for dogfood finding 6631c0ab0454 ("Missing canonical URL on home", audit 20260808T074205Z-msk2fl3n), already fixed in PR #29 and closed out against main and live in PR #38 (2026-08-09).
Since the closeout, five commits touched the public surface (95d2248 preferred source pages, c5e2f2b Agent Desk de-index, ac05bec tap targets, f9f0b0f footer link, 1cc7a4e audit canonical/JSON-LD cleanup). Only 1cc7a4e touched a canonical link — the audit page's moved from the redirecting
/audit.htmlto the clean/audit(guard updated to match); the home-page canonical the finding flagged is byte-identical to the closeout measurement. This lane re-confirmed the guarantee on current main (1cc7a4e):npm run checkpasses — the "Canonical URLs (dogfood)" guard inscripts/check-site.mjsrequires exactly one non-commented canonical link inside<head>per page, non-empty href, correct per-page address, no cross-page duplicates — and the fullnpm testsuite passes (check, headings 6/6, sitemap, worker, ui, contract).<link rel="canonical" href="https://tinystudio.io/">..htmlform that PR fix(public): point appraisal-page canonicals and JSON-LD @ids at the clean /audit URL #56 already corrected on main; neither lagging commit touches the home canonical, and the PR seo: add canonical URLs to the five public pages (finding 6631c0ab0454) #29 fix has been live since before the closeout.Evidence
docs/evidence/canonical-urls-2026-08-09.mdgains a "Closeout re-verification (added 2026-08-11)" section (same pattern as the sitemap, heading-hierarchy and meta-description reverify lanes).Nothing further to change — the finding remains closed on the code side (PR #29), in CI (
npm run checkguard), and against the deployed site.Summary by CodeRabbit
/auditcanonical URL change and the temporary difference between the current source and deployed site.