docs(lane1): re-verify homepage managed-service section absence is the honored snooze

[nish3451]

Item

[unreviewed-by-opus] Live site is missing the entire <section id="managed-service"> block on the homepage while the merged homepage on main carries it

Disposition: intended, snooze honored — not a regression

The managed-service buyer path (PRs #10/#11) is snoozed-by-Nish (2026-08-08: do not build, publish, or deploy it without his explicit yes). The release lane strips the entire section via scripts/prepare-public-deploy-bundle.mjs (fail-closed in both directions), and both scripts/test-public-deploy-bundle.mjs and scripts/check-public-live-deploy.mjs assert its absence.

Fresh re-verification (2026-08-21)

• Source: public/index.html still carries the section (id="managed-service", line 284) on origin/main HEAD ccfbd4b.
• Live: fresh fetch of https://tinystudio.in/ — 200, portfolio title, zero id="managed-service" / "Website Correction" / "website-correction" / "managed service" / data-measure-source.
• Provenance: live deploy-manifest.json shows filter_version: 1, source_commit: ccfbd4b (current main), prepared_at: 2026-08-21T03:59:56Z — the live bundle is current, so the absence is the filter's deliberate output, not a stale deploy. (The deploy path was repaired in fix(release): CF_API_BASE typo — deploy lane 403'd since creation #208/fix(release): deploy lane Node 20 → 22 (wrangler hard requirement) #209/fix(release): acceptance checker was dead code (missing import + undefined helpers) #211; the earlier 2026-08-11 disposition noted a stale 06-20 bundle, which is no longer the case.)
• Checks: scripts/test-public-deploy-bundle.mjs 101 checks 0 failures; scripts/check-public-live-deploy.mjs 240 checks 0 failures.

Change

Single docs annotation in docs/measurement/public-conversion-signal.md recording the re-verification. No product change — the section returns only when Nish lifts the snooze.

Summary by CodeRabbit

• Documentation
  • Added a re-verification confirming the homepage’s managed-service section is intentionally hidden while its snooze remains active.
  • Documented that the current deployment matches the approved source and filtering behavior.
  • Confirmed the behavior is intentional and not a regression.

[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: 4 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: 5028f482-9684-400f-9c77-1aa28d6c24d9

📥 Commits

Reviewing files that changed from the base of the PR and between 86a7ef9 and a801dec.

📒 Files selected for processing (1)

• .lane/reports/docs-lane1-homepage-managed-service-snooze-reverify-20260821.md

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 3ba085e1-2318-4385-9046-c713ce40eea9

📥 Commits

Reviewing files that changed from the base of the PR and between ccfbd4b and 86a7ef9.

📒 Files selected for processing (1)

• docs/measurement/public-conversion-signal.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The documentation adds a 2026-08-21 re-verification of the managed-service section. It records that the section remains absent from production because the active snooze triggers fail-closed filtering.

Changes

Conversion Signal Documentation

Layer / File(s)	Summary
Managed-service production verification docs/measurement/public-conversion-signal.md	Adds source, live-site, and deployment-manifest evidence. Records that the section will return after the snooze is lifted.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 86a7e

This PR records the verified homepage deployment behavior without changing product code or runtime behavior. No actionable merge-blocking risk remains beyond normal checks and review.

---

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.}