docs(lane1): reverify soft-404 item — source fixed on main (PR #34), live blocked on missing Cloudflare token - #189
Conversation
…live blocked on missing Cloudflare token
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 6 minutes Limit details: You’ve used all 1 included review currently available under your plan. 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.
Your trial has ended. Reactivate Greptile to resume code reviews.
…-08-20) (#210) 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 Co-authored-by: minimax-vps <minimax-vps@MiniMax.local>
1 participant
Lane 1 reverify: soft-404 item
Item: [unreviewed-by-opus] Every unknown URL on tinystudio.in returns HTTP 200 with the full homepage - soft-404.
Verdict
No source change is possible or needed — the soft-404 fix is already merged on main (PR #34, commit
4499dd4) with a full local/CI/deploy-proof chain; live delivery is still blocked by the missingCLOUDFLARE_API_TOKENrepo secret (NEEDS-NISH). Re-deploying origin/main once a Pages-scoped token is provisioned closes the item; no code change will be required.Evidence (2026-08-17, from this checkout of fresh origin/main)
test-public-soft-404.mjs→ 19 checks, 0 failures (wired intonpm test/npm ci). Deploy-bundle gate (NEUTRAL_PROOFS, top-level real-404 proof from PR fix(public): enforce the top-level real-404 deploy proof in the release lane #104) passes. Release-lane post-deploy acceptance asserts live 404s with auto-rollback./404.html→ HTTP 200 + homepage body.check-public-live-soft-404.mjs→ 5 failures;check-public-live-deploy.mjs→ 7 failures (whole production deployment is the stale 2026-06-20 bundle, which has no404.html, so Pages' SPA fallback serves index.html for everything).gh secret listhas onlyCLOUDFLARE_ACCOUNT_ID; deploy workflow fails fail-closed on every main push (latest 2026-08-17T00:24:49Z); nightly Live Site Check alarms daily (by design). VPS fleet token verified 403 (no Pages permission).One-time fix (no code change needed)
f670a698e17bf160c8e4679823e68916gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-incheck-public-live-soft-404.mjsmust report 0 failures.Docs-only change:
.lane/reports/docs-lane1-soft-404-reverify-20260817.md