docs(lane1): reverify soft-404 item — RESOLVED on the live site (2026-08-20) - #210
Conversation
…-08-20) The soft-404 defect (unknown URL returns HTTP 200 with the homepage body) is now fixed on https://tinystudio.in: a random nonce URL returns HTTP 404 with the real 'Page not found' page (title 'Page not found • Tiny Studio', H1 'This page could not be found.', noindex meta, shared header/footer chrome, no canonical to '/'). The dedicated live soft-404 checker passes 18/18 and the static unit test passes 21/21. Previous 2026-08-17 reverify (PR #189) concluded the soft-404 was real and live, blocked on the missing CLOUDFLARE_API_TOKEN. The deploy lane has since been repaired end-to-end: - PR #198: workflow reads secrets.CLOUDFLARE_API_TOKEN || secrets.CLOUDFLARE - PR #199: PAGES_PROJECT = 'tiny-studio' (was the broken 'tiny-studio-3f5' subdomain), wrangler --project-name fixed - PR #208: CF_API_BASE /api/v4 -> /client/v4 (captureProductionIdentity was 403'ing on every call since the lane was created) With the lane able to capture a real canonical_deployment, the daily schedule + the next main push published the filtered public/ bundle, and the live 404 page now appears. Live evidence (curl, live checker, deploy acceptance section C, deploy-bundle gate) all agree; item is closed on the live proof, not a code task. Report only; no source file changed. Files: + .lane/reports/docs-lane1-soft-404-reverify-20260820.md
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 38 minutes Limit details: You’ve used the included review currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day 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/settings/billing. Comment |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - C. deployed 404 page is real, not homepage (3/3) | ||
| - D. real page still serves (1/1) | ||
| - E. deployed stylesheet keeps WCAG 2.2 24px footer tap-target rule (PR #22) (7/7) | ||
| - F. deployed llms.txt lists every public page (1/1) |
There was a problem hiding this comment.
Section F performs two checks—one for the HTTP status and one for page coverage—but the report labels it 1/1. This makes the section breakdown sum to 17 rather than the stated total of 18 and makes the closure evidence harder to audit.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .lane/reports/docs-lane1-soft-404-reverify-20260820.md
Line: 29
Comment:
**Section F count is understated**
Section F performs two checks—one for the HTTP status and one for page coverage—but the report labels it `1/1`. This makes the section breakdown sum to 17 rather than the stated total of 18 and makes the closure evidence harder to audit.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
Verdict
Item RESOLVED on the live site. A random nonce URL on https://tinystudio.in now returns HTTP 404 with the real "Page not found" page (not the homepage). No source change is needed.
What this report contains
A reverification of the lane-1 soft-404 item (
[unreviewed-by-opus] Every unknown URL on tinystudio.in returns HTTP 200 with the full homepage - soft-404, and no). The 2026-08-17 reverify (PR #189) was blocked on the missing Cloudflare token; the deploy lane has since been repaired end-to-end:aaeab8b) — acceptCLOUDFLAREas the token secret name alongsideCLOUDFLARE_API_TOKEN3c13d47) — correct Pages project name totiny-studio(was the broken subdomain)b64f242) — fixCF_API_BASEtypo/api/v4→/client/v4(captureProductionIdentity was 403'ing on every call)With the lane able to capture a real
canonical_deployment, the filteredpublic/bundle was published, and the live 404 page now appears.Evidence (verified 2026-08-20, fresh
origin/main=b64f242)curl -sI https://tinystudio.in/__soft-404-test-$(openssl rand -hex 6).html→ HTTP 404, real not-found bodynode scripts/check-public-live-soft-404.mjs→ 18 checks, 0 failures (dedicated soft-404 live checker)node scripts/test-public-soft-404.mjs→ 21 checks, 0 failures (static unit test)node scripts/check-public-live-deploy.mjssection C → 2/2 ok (soft-404 proof in deploy-lane acceptance)"alternateName": "tinystudio.in", "not affiliated" copy, noWebsite Correction, nomanaged-serviceThe single failure in
check-public-live-deploy.mjs(214/1) is an unrelated script-internalPUBLIC_PAGE_URLS is not definedReferenceError in section I (the llms.txt coverage check inside that script) — the llms.txt file itself is correct and the dedicated soft-404 checker section F is green.Why no source code change
The soft-404 fix is already on main (PR #34 added
public/404.html, PR #104 enforced the deploy proof). What was missing was a working deploy lane, which the three PRs above provided. Item is closed on the live proof; no further code change required.Files
+ .lane/reports/docs-lane1-soft-404-reverify-20260820.md— this report (unique to this lane, not a shared report file)The fix and its guards already live on main via PR #34 (
4499dd4) and PR #104 (d54c91f). Prior reports: PR #149 (deploy-gap root cause), PR #189 (2026-08-17 still-blocked reverify).Greptile Summary
The PR adds a lane report documenting that the live soft-404 issue is resolved and attributes the resolution to repaired deployment infrastructure.
Confidence Score: 5/5
The PR appears safe to merge.
No blocking failure remains.
Important Files Changed
Reviews (2): Last reviewed commit: "Merge branch 'main' into docs-lane1-soft..." | Re-trigger Greptile