docs(lane1): reverify trust-page heading-hierarchy item — fixed in PR #74 and now verified live

[nish3451]

Summary

Reverify report for tinystudio-in lane 1 item: "Live /privacy/, /terms/, and /drishti/privacy/ still expose H1->H3x3 document outlines while origin/main has the merged PR #74 H1->H2x3 outline".

Outcome

Already fixed and now verified live — no source change needed.

• The H1->H2x3 repair is merged on main (PR fix(public): repair heading hierarchy on terms, privacy, and Drishti privacy pages #74).
• CLOUDFLARE_API_TOKEN was provisioned 2026-08-20; the Deploy public site lane now runs green on main pushes.
• Deploy run 32419947981 (push ccfbd4b, 2026-08-20) post-deploy acceptance: 240 checks, 0 failures, including section J "trust pages render the fixed H1 -> H2x3 card outline (PR fix(public): repair heading hierarchy on terms, privacy, and Drishti privacy pages #74)" for /privacy/, /terms/, /drishti/privacy/ (plus /promptly/privacy/, /privacy-choices/).
• Live guard test-public-live-heading-hierarchy.mjs: 17 checks, 0 failures.
• Direct live fetches 2026-08-21: all three pages serve H1 -> H2x3 cards -> H2 footer -> H3x3, no jump >1.

Why the homepage managed-service section is still absent on live

By design: the deploy bundle filters it out (its acceptance asserts "homepage has no id=managed-service"), per the separately decided-snoozed buyer-path item 643f147275 ("you pushed it to later") and the deploy-path item 63a61bb1b7 ("do NOT deploy the managed-service buyer-path content (#10/#11) — remains snoozed-by-nish until he says yes"). That residual is not this item's to fix.

Files

• .lane/reports/fix-lane1-trust-pages-heading-hierarchy-reverify-20260821.md — this lane's report (only file changed).

[chatgpt-codex-connector]

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 30 minutes

Limit details: You’ve used the included review currently available.

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?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 8ca4771e-e2ae-4bd2-8f67-31ab2c7aab77

📥 Commits

Reviewing files that changed from the base of the PR and between b7a09a3 and 38253f2.

📒 Files selected for processing (1)

• .lane/reports/fix-lane1-trust-pages-heading-hierarchy-reverify-20260821.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/settings/billing.

_{Comment @coderabbitai help to get the list of available commands.}