Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

PR Summary

Medium Risk
All server-side flag evaluation now depends on LaunchDarkly configuration and the new staging/production mapping; misconfiguration could change who sees gated features until defaults apply.

Overview
PostHog server feature flag evaluation is removed (posthog-node and the PostHog provider/client modules). LaunchDarkly is wired in via OpenFeature with a shared provider interface, lazy client init, retry after failed init, and safe fallbacks to flag defaults when the SDK key is missing or evaluation fails.

Flag environment is now staging or production (explicit FEATURE_FLAG_ENVIRONMENT, or Vercel production vs everything else as staging). OpenFeature contexts map dashboard user and optional team for LaunchDarkly targeting. The feature flag service default provider and evaluate API now pass full flag definitions, not only keys.

Env/docs/scripts add LAUNCHDARKLY_SDK_KEY and require FEATURE_FLAG_ENVIRONMENT when the SDK key is set. PostHog remains for analytics only in client env naming/docs. Unit tests cover OpenFeature context mapping, environment resolution, and LaunchDarkly init retry behavior.

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

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

Project	Deployment	Actions	Updated (UTC)
web	Ready	Preview, Comment	Jun 18, 2026 1:19am