fix: unwrap TraitConfig values in local evaluation before segment matching

TraitConfig objects ({ value, transient }) were passed directly to the
evaluation engine without extracting the actual value. This caused
segment condition comparisons to fail (e.g. 'cedars' == { value: 'cedars',
transient: true } → false), so segment overrides were never applied.

The remote evaluation path already handled this correctly via
isTraitConfig() in generateIdentitiesData. This fix applies the same
unwrapping in getIdentityFlagsFromDocument and getIdentitySegments.

Fixes #238

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: talissoncosta

sdk/index.ts

@@ -8,7 +8,13 @@ import { FlagsmithAPIError, FlagsmithClientError } from './errors.js';
 
 import { DefaultFlag, Flags } from './models.js';
 import { EnvironmentDataPollingManager } from './polling_manager.js';
-import { Deferred, generateIdentitiesData, getUserAgent, retryFetch } from './utils.js';
+import {
+    Deferred,
+    generateIdentitiesData,
+    getUserAgent,
+    isTraitConfig,
+    retryFetch
+} from './utils.js';
 import {
     SegmentModel,
     EnvironmentModel,
@@ -275,7 +281,7 @@ export class Flagsmith {
             identifier,
             Object.keys(traits || {}).map(key => ({
                 key,
-                value: traits?.[key]
+                value: isTraitConfig(traits?.[key]) ? traits![key].value : traits?.[key]
             }))
         );
 
@@ -474,7 +480,7 @@ export class Flagsmith {
             identifier,
             Object.keys(traits).map(key => ({
                 key,
-                value: traits[key]
+                value: isTraitConfig(traits[key]) ? traits[key].value : traits[key]
             }))
         );