feat(deploy): validate separate Paradev projects in previews

Merged
KI
5d ago
+59-2

What & why

Validate the separate api-paradev and web-paradev Vercel projects before production setup. The paradev-project-preview label switches only API/web preview destinations, requires domain-preview and explicit public project variables, and retains preview credentials and the isolated Neon database.

#9687 is merged; this PR now targets main. No production workflow, secrets, live domains, marketing links, or cutover redirects change.

Validation

  • YAML parsing, actionlint and all 16 label/variable configurations passed. Independent workflow review found no blockers.
  • CI Lint, Test, Typecheck, CLI build and page-storage integration checks passed.
  • All preview deployments passed, including API/web in their new projects. Corrected new project defaults to Node 24 and pdx1; public API protection now matches the existing API. The first builds used iad1 before that setting correction.
  • Seven live metadata/CORS checks passed: canonical preview issuer/resource preserved, browser endpoints and connector callback use the owned preview API host, app origin allowed and unrelated origin denied.
  • Thirteen additional HTTP checks passed: database health, both desktop OAuth starts and state-cookie attributes, invalid desktop inputs, external callback rejection, four unauthenticated integration guards and legacy-host read-only reachability.
  • Notion and Teams return 503 because preview credentials are absent; these vendor flows remain unverified.
  • Browser Use completed real Google sign-in on the new projects with the existing preview account. Account navigation and hard reload retained authentication.
  • Completed desktop Google OAuth through API -> Google -> web success -> localhost receiver. The received desktop session authenticated as the expected user; JWT signature, canonical preview issuer/audience and subject validated. Signed out only the test desktop session; browser authentication remained valid.
  • Cua Driver controlled real Chrome home/integrations/account/billing navigation and reloads. PostHog confirmed these new visits still resolve to the original marketing person.

Vercel classified the first new-project build as a production target/default alias; the workflow still used preview credentials and a preview database. No production data deployment or cutover was performed.

Summary by CodeRabbit

  • New Features
    • Preview deployments can now use separate Paradev projects when a pull request has the required labels. Preview URLs continue to use the existing API alias and preview environment.
    • Preview setup is blocked when the required labels are not paired or project configuration is missing.
  • Documentation
    • Added guidance on preview URLs, configuration requirements, OAuth callbacks, and cleanup. Production deployments and credentials are unchanged.