docs(lane): soft-404 root cause is the stale deployment (release-lane deploy gap) - #149
Conversation
The repo already carries the real 404 fix (PR #34) and its static guards; the live site serves the 2026-06-20 bundle because the release lane fails closed on the missing CLOUDFLARE_API_TOKEN Pages secret. Document the evidence and the one-time provisioning action that resolves the item. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
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: 1 minute 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 |
1 participant
What this is
Investigation report for the open item: every unknown URL on tinystudio.in returns HTTP 200 with the full homepage.
Root cause: the soft-404 is a stale-deployment problem, not a repo bug. The code fix already exists on main (PR #34 added the real
public/404.html), and the repo's static guards all pass. The live site has served the 2026-06-20 bundle (a0d1de5, pre-#34) since the Cloudflare GitHub integration broke, and the release lane cannot re-deploy because theCLOUDFLARE_API_TOKENrepo secret was never provisioned (the lane fails closed by design).Evidence (2026-08-14)
GET /__ts-lane1-abc123.htmlGET /404.htmlscripts/test-public-soft-404.mjsscripts/check-public-live-soft-404.mjsWhat this PR changes
.lane/reports/fix/lane1-soft-404-deploy-gap.mddocumenting the diagnosis, live evidence, and the exact one-time action to resolve the item (provision a Pages-scoped token,gh secret set CLOUDFLARE_API_TOKEN, re-run the deploy lane; the lane is self-verifying against the live 404 proof with auto-rollback).How to resolve the item
f670a698e17bf160c8e4679823e68916).gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-innode scripts/check-public-live-soft-404.mjsmust pass 0 failures.