docs(lane1): report contact heading-hierarchy item — already fixed in PR #18, live blocked on missing Cloudflare token - #170
Conversation
… PR #18, live blocked on missing Cloudflare token 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. |
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: 27 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: 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.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
…iew ladder, not stuck CI (#175) Lane 1 verification report: the tinystudio-in merge gate is not frozen and not defective. auto-ship merged 5 tinystudio-in PRs today (all docs/tests-only safe changes: #172, #170, #174, #168, #173), and the 12 CLEAN PRs are all code PRs that by design ride the flagship review ladder before any merge. That ladder is currently queued behind a live flagship repair (fleet-repair-3b6421dc29), so code PRs are SKIPPED/WAITING each cycle. Of 30 open PRs only 12 are CLEAN; 10 are BLOCKED (CI queued) and 8 DIRTY. No code change in this repo can unblock it. No product files changed. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Lane 1 report: heading hierarchy cleanup on /contact
Dogfood item 52753880dfc7 — no source change possible or needed.
Verification
71a20a4"fix(public): repair heading hierarchy on audited pages (fix(public): repair heading hierarchy on audited pages #18)" is an ancestor oforigin/mainand changedpublic/contact/index.html(card headingsh3->h2). Current outline isH1 -> H2s -> H2 footer -> H3s, no skipped levels.scripts/test-public-heading-hierarchy.mjsasserts the card H2s and no jumps — 93 checks, 0 failures locally.https://tinystudio.in/contact/still servesh1 -> h3 h3 h3(old outline), and livestyles.csslacks the.info-card :is(h2, h3)rule. Production is byte-identical to the 2026-06-20 build.CLOUDFLARE_API_TOKENsecret missing —gh secret listshows onlyCLOUDFLARE_ACCOUNT_ID. All recent deploy runs fail at "Required Pages secrets not provisioned - fail loudly".Unblock
gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-in(Cloudflare Pages:Edit token)No repository product files changed; this PR adds only the lane report.