docs(lane1): report Promptly privacy meta-tightening item — source merged, live blocked on missing Cloudflare token

[nish3451]

Summary

Dogfood finding 63256313bbbb flags the /promptly/privacy meta description as needing tightening. This report documents that the source fix is already merged and that live delivery is blocked by infrastructure outside this lane's scope.

Verification

• Source merged: commit 6674aec "fix(public): tighten the Promptly privacy page meta description (fix(public): tighten the Promptly privacy page meta description #120)" is an ancestor of origin/main (HEAD a294496). It shortens the description from 144 to 121 chars, dropping the redundant "App-specific" lead-in and "what it handles" filler, synced across meta description, og:description, twitter:description, and JSON-LD.
• Test-pinned: scripts/test-public-structured-data.mjs gates the pattern (JSON-LD description matches meta description); ran 127 checks, 0 failures.
• Live still stale: https://tinystudio.in/promptly/privacy/ serves the old thin description ("App-specific privacy policy for Promptly by Tiny Studio.") because production is a stale build.

Blocker (NEEDS-NISH)

.github/workflows/deploy-public-site.yml is fail-closed on CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID. Only CLOUDFLARE_ACCOUNT_ID exists; CLOUDFLARE_API_TOKEN is missing, so every deploy run fails at the "Required Pages secrets not provisioned - fail loudly" step. Provisioning requires a Cloudflare dashboard token — a Nish action owned by the canonical deploy-pipeline item.

Unblock

1. gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-in
2. Next main push (or workflow_dispatch) deploys the fix along with the other ~17 merged public fixes.

[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: 40 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: cf26f1c2-d365-470e-bedd-37e88a1d9db1

📥 Commits

Reviewing files that changed from the base of the PR and between a294496 and 24da2f8.

📒 Files selected for processing (1)

• .lane/reports/docs-lane1-promptly-privacy-meta-live-gate-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.}