Observability page, waitlist endpoint, and Early Access nav tag

[pd-builds]

Ships the /cloud/observability launch: the page, the waitlist behind its form, and the nav change that points at it.

1. The page (/cloud/observability)

A structural copy of the Cloud page with its own copy and art, so editing it cannot affect /cloud.

• Hero: "User insights / for AI agents" (hard break on desktop only), email capture, light/dark hero art for desktop and mobile
• Four features with alternating layout: Session replay, Annotations, Timeline, Insights, each with 1440x800 light/dark art served at 720x400
• Closing CTA reusing the same email form

2. The waitlist (POST /api/waitlist)

• Validates origin, content type, body size, and address; per-instance rate limit (5/min, keyed on x-real-ip with x-forwarded-for fallback)
• Forwards server side to a Google Form; the form's linked sheet is the list. Neither Tally's API nor the official Google Forms API can create submissions, so the form's own formResponse endpoint is used, with its caveats documented in lib/waitlist/store.ts
• Config via GOOGLE_FORM_ID and GOOGLE_FORM_EMAIL_ENTRY, already set in Vercel for Production and Preview. Unconfigured or upstream failure returns 503 and the UI shows an error; success is only ever reported after Google confirms the write
• The form UI: arrow icon button becomes a "Get Early Access" text button as you type (animated via a 0fr to 1fr grid track); on mobile the pill splits into a stacked input and full-width button

3. The nav

Observability shipped in #1044 as Coming soon and disabled. The page is live now, so:

• New tag field on nav items: labels without disabling (unlike comingSoon, which does both)
• Observability is a real link with an "Early access" chip, in the desktop dropdown and the mobile tray
• .comingSoon renamed to .itemTag since it now serves both statuses

Verification

• next build passes; both routes in the manifest
• Production build verified in-browser against main's HeroSection: hero, line break, form, all four feature images, nav chip, zero broken images
• Endpoint verified end to end against the real Google Form: a submission through the page UI landed in the sheet, and a wrong entry id fails visibly (400 from Google, 503 to the client) rather than writing a blank row

After merge

• Deploy manually and re-point the preview alias; the Vercel project has no connected Git repository, so merging does not deploy anything by itself
• Delete the three claude-* test rows from the waitlist sheet before launch
• The rate limiter is per-instance, so on serverless it blunts casual abuse rather than preventing it

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openui-docs	Ready	Preview	Aug 23, 2026 5:38pm