chore: remove syncVercelEnvVars from Trigger configs

[claudfuen]

Summary

• Remove syncVercelEnvVars() from both app and API Trigger.dev configs
• All required env vars are already set independently in Trigger's dashboard (staging + production)
• Decouples Trigger env from Vercel env for proper isolation

Why

Trigger should manage its own env vars explicitly, not inherit from Vercel. This is a prerequisite for staging email isolation (separate Resend keys per environment).

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
app	Ready	Preview, Comment	Apr 10, 2026 6:34pm
comp-framework-editor	Ready	Preview, Comment	Apr 10, 2026 6:34pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal	Skipped		Apr 10, 2026 6:34pm

[cursor]

PR Summary

Low Risk
Removes an environment-variable sync mechanism, so misconfigured Trigger dashboard env vars could cause runtime failures, but the code change itself is small and localized to build config.

Overview
Removes syncVercelEnvVars() from both apps/api/trigger.config.ts and apps/app/trigger.config.ts, so Trigger jobs no longer inherit environment variables from Vercel at build time.

This decouples Trigger’s runtime configuration from Vercel and relies on env vars being managed directly in Trigger.

^{Reviewed by Cursor Bugbot for commit 1c040c0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[claudfuen]

🎉 This PR is included in version 3.20.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀