[kinyoklion]

Summary

Extends the analytics event processing in LaunchDarkly.InternalSdk for override-affected evaluations, as defined by the OVERRIDE specification.

EventTypes.EvaluationEvent gains an OverrideAffected field. When it is set, the event processor produces no individual feature event and no debug event for the evaluation, whatever the flag's TrackEvents and DebugEventsUntilDate request. The evaluation is still counted in summary events, and the marker becomes part of the summary counter key, so override-affected and other evaluations of the same flag key, variation, and version accumulate into separate counters instead of being collapsed together. The summary event output writes "overrideAffected": true on a marked counter and omits the property otherwise, following the existing unknown marker. The summarizer interface carries the marker through both the aggregated and the per-context summarizers.

Nothing sets the field yet; the server SDK does so in the next change. Every existing event path is unchanged when the field is false, which the existing event processor and output tests confirm. New tests cover the suppression of feature and debug events, the suppression of a marked prerequisite record, the separate counters, and the counter serialization.

This PR is based on the branch of the override layer change so that the whole flag overrides series applies as one linear sequence; it uses nothing from that branch.

SDK-3248

---

Note

Overview
Adds an experimental flag/segment override layer to the FDv2 data system so operators can force known flag state per key without affecting initialization or data-source status.

Configuration and plumbing: DataSystemBuilder.Overrides() wires an optional IOverrideSource into DataSystemConfiguration. FDv2 builds an OverrideLayer, OverrideSink, and OverrideOverlay on the store read path; FDv1 exposes empty/no-op override APIs. Offline mode skips starting the source (warn only). Start/dispose failures are logged and the client continues without overrides when appropriate.

Evaluation and client behavior: Overridden entries win on read; flags can be evaluated (and AllFlagsState can return override-only payloads) before LaunchDarkly data is available when the layer holds them. Evaluation reasons carry overrideAffected through errors and migration paths; AllFlagsState disables per-flag tracking fields for override-affected results.

Change notifications: LaunchDarkly updates fan out through combined dependency tracking (IExternalDependencies on the override layer), and override snapshots notify listeners via the same flag-change path with merged-view diffing in OverrideChanges.

Analytics: EvaluationEvent.OverrideAffected suppresses individual feature and debug events while still counting summaries; counters are keyed separately and serialize "overrideAffected": true when set.

Extensive unit/integration tests cover the layer, overlay, sink, builder, client scenarios, OVERRIDE spec vectors, and event summarizer/processor output.

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

[kinyoklion]

bugbot review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

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