Skip to content

docs(lane1): report contact heading-hierarchy item — already fixed in PR #18, live blocked on missing Cloudflare token - #170

Merged
nish3451 merged 3 commits into
mainfrom
docs/lane1-contact-heading-hierarchy
Aug 15, 2026
Merged

docs(lane1): report contact heading-hierarchy item — already fixed in PR #18, live blocked on missing Cloudflare token#170
nish3451 merged 3 commits into
mainfrom
docs/lane1-contact-heading-hierarchy

Conversation

@nish3451

Copy link
Copy Markdown
Collaborator

Lane 1 report: heading hierarchy cleanup on /contact

Dogfood item 52753880dfc7 — no source change possible or needed.

Verification

  1. Source already fixed: commit 71a20a4 "fix(public): repair heading hierarchy on audited pages (fix(public): repair heading hierarchy on audited pages #18)" is an ancestor of origin/main and changed public/contact/index.html (card headings h3 -> h2). Current outline is H1 -> H2s -> H2 footer -> H3s, no skipped levels.
  2. Test-pinned: scripts/test-public-heading-hierarchy.mjs asserts the card H2s and no jumps — 93 checks, 0 failures locally.
  3. Live still stale: https://tinystudio.in/contact/ still serves h1 -> h3 h3 h3 (old outline), and live styles.css lacks the .info-card :is(h2, h3) rule. Production is byte-identical to the 2026-06-20 build.
  4. Deploy blocker (NEEDS-NISH): CLOUDFLARE_API_TOKEN secret missing — gh secret list shows only CLOUDFLARE_ACCOUNT_ID. All recent deploy runs fail at "Required Pages secrets not provisioned - fail loudly".

Unblock

No repository product files changed; this PR adds only the lane report.

… PR #18, live blocked on missing Cloudflare token

Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 43889267-6449-4857-b2f1-52ef666de7cf

📥 Commits

Reviewing files that changed from the base of the PR and between bb28441 and 940328f.

📒 Files selected for processing (1)
  • .lane/reports/docs-lane1-contact-heading-hierarchy-20260815.md

Note

🎁 Summarized by CodeRabbit Free

Your 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 @coderabbitai help to get the list of available commands.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@nish3451
nish3451 merged commit 230baa8 into main Aug 15, 2026
2 checks passed
nish3451 added a commit that referenced this pull request Aug 15, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant