docs(lane1): reverify thin label-only meta descriptions on five trust/support pages (#lane1)

[nish3451]

Lane 1 reverify: thin label-only meta descriptions on five trust/support pages

Item: [grok-reviewed 2026-08-09 08:30 IST] — reported as five trust/support pages still carrying thin label-only meta descriptions, with /promptly/privacy specifically called out.

Verdict: No source change possible or needed. Same outcome as the 2026-08-14 report (#149), re-verified today on a fresh origin/main (= 53ea7a9).

Source — already fixed, stable

• git merge-base --is-ancestor 9a73040 origin/main → true
• All five pages (/terms/, /promptly/{support,privacy}/, /drishti/{support,privacy}/) carry substantive descriptions (121–159 chars) synced across meta name="description", og:description, and twitter:description
• The /promptly/privacy description twin (item 63256313bbbb) was tightened in PR fix(public): tighten the Promptly privacy page meta description #120 (6674aecf)
• scripts/test-public-deploy-bundle.mjs → 63 checks, 0 failures on this checkout

Live — still stale (a deployment-blocker artifact, not a source defect)

curl -sL https://tinystudio.in/<page>/ (run 2026-08-17) returns the OLD label-only descriptions (44–58 chars) on all five routes. The live bundle is byte-identical to the 2026-06-20 initial bundle (07acd07); every merged public change since 2026-08-07 has never reached production.

Deploy blocker — same fail-closed gate, still NEEDS-NISH

• GET /repos/nish3451/tinystudio-in/actions/secrets (run today) → total_count: 1 — only CLOUDFLARE_ACCOUNT_ID; CLOUDFLARE_API_TOKEN is still missing.
• Latest Deploy public site on push 53ea7a9 (run 32000121501) failed at step "Required Pages secrets not provisioned - fail loudly" at 06:05:20 UTC. The fail-closed behaviour is working as designed.
• The only Cloudflare token on this VPS has no Pages permission (HTTP 403 on /pages/projects/…), so no shell route can unblock it.

What unblocks live delivery (no code change required)

1. Provision a Cloudflare Pages-scoped token: https://dash.cloudflare.com/profile/api-tokens → "Cloudflare Pages: Edit", scoped to account f670a698e17bf160c8e4679823e68916
2. gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-in
3. Trigger the deploy lane; the five meta descriptions reach production alongside the other ~17 merged public fixes.
4. node scripts/check-public-live-deploy.mjs must show 0 failures on the five meta lines (post-deploy accept holds the live proof).

---

Lane: tinystudio-in lane 1 · Worker: minimax-m3 (high) · Date: 2026-08-17 · Branch: docs/lane1-meta-descriptions-reverify-20260817

Co-authored-by: MiniMax VPS minimax-vps@MiniMax.local

[chatgpt-codex-connector]

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

[greptile-apps]

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 6 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

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: 8a7bafb2-6527-44fe-941d-a64147d13fb1

📥 Commits

Reviewing files that changed from the base of the PR and between 53ea7a9 and 9145d94.

📒 Files selected for processing (1)

• .lane/reports/docs-lane1-meta-descriptions-reverify-20260817.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.}