Add Prime feature flag evaluation client

[d42me]

Adds a Prime CLI feature flag client that evaluates defaults via the platform feature-flags endpoint with CLI version and team context, falling back to defaults when evaluation is unavailable.

---

Note

Low Risk
New optional client module with fail-open defaults on API errors; no changes to existing auth or sandbox flows.

Overview
Adds a Prime CLI feature flag client so callers can resolve flag values from the platform instead of hard-coding defaults.

FeatureFlagsClient POSTs to /feature-flags/evaluate with the requested flag defaults, cli_version, and optional team_id, then merges server flags with per-key fallback when a key is missing. evaluate_feature_flags wraps that and returns a copy of defaults on APIError; is_feature_enabled treats only boolean True as enabled. The new symbols are re-exported from prime_cli.

Unit tests cover request payload/context, API failure fallback, empty input (no network call), and strict boolean handling for is_feature_enabled.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b27f8f3. Configure here.}

[cursor]

Config without client desyncs

Medium Severity

When FeatureFlagsClient or evaluate_feature_flags get a config but no client, a new APIClient uses its own Config for auth and base URL while team_id in the evaluate payload comes from the passed config, so evaluation context can disagree with the request identity.

Additional Locations (1)

• packages/prime/src/prime_cli/feature_flags.py#L43-L53

 

^{Reviewed by Cursor Bugbot for commit b27f8f3. Configure here.}

[willccbb]

@d42me should we fix or OK?