docs(lane1): reverify homepage managed-service heading-hierarchy item - #177
Conversation
|
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: 25 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 |
… (PR #141), postal address blocked on operator fact (#177) (#179) Lane 1 third re-verification report: dkimSelector=resend is set on main (PR #141, fcf5ff3) and the live resend._domainkey.tinystudio.io record resolves; SPF, DMARC, and DKIM all verify. The only remaining sender warning is the empty senderPhysicalAddress, which requires a real published business address (CAN-SPAM) that no code change can supply. No product files changed. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
…hierarchy-reverify-20260815
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
2 participants
Summary
Lane-1 reverify of the item: Homepage managed-service section skips H2->H4 and is missing from the public heading-hierarchy.
Outcome: no product source change needed. The fix is already merged on main as PR #143 (commit
497d690): the#managed-servicefeature heading wentH4 -> H3, giving the section outlineH2 -> H3, andscripts/test-public-heading-hierarchy.mjssection D pins it (93 checks, 0 failures). The live site is still stale — byte-identical to the 2026-06-20 build — because every deploy since then fails closed at the missingCLOUDFLARE_API_TOKENsecret.Evidence (fresh, 2026-08-15)
1 2 3 4 4 3 4 2 3 3 3 2 3 2 3 3 3 3— no jump > 1; managed-service sectionH2 -> H3.node scripts/test-public-heading-hierarchy.mjs-> 93 checks, 0 failures.https://tinystudio.in/still has no#managed-servicesection and matches the old build outline.gh secret list-> onlyCLOUDFLARE_ACCOUNT_ID; deploy run 31862578087 failed at "Required Pages secrets not provisioned - fail loudly".Unblock
Nish:
gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-in(Cloudflare Pages:Edit token), then the next main push deploys all merged public fixes.