[kinyoklion]

Summary

This connects the override-affected marking of an evaluation to analytics events, as the OVERRIDE specification requires. An evaluation that read a definition from the override store, directly or through a prerequisite or a segment, produces no individual feature event and no debug event, whatever the flag's configuration requests. It is still counted in summary events, in a separate counter that carries overrideAffected: true, so LaunchDarkly can tell override-affected counts from ordinary counts of the same flag, variation, and version. A prerequisite record carries the prerequisite's own marking: an unaffected prerequisite evaluated inside a marked evaluation still produces its individual event.

• EventProcessor gains an overload of recordEvaluationEvent with the marking. It is a default method that ignores the marking and delegates to the existing method, so a custom implementation keeps compiling and behaving as before. The SDK's implementations override it.
• The evaluator's event recorder passes the evaluation result's marking for top-level, prerequisite, and requested-type-mismatch records. An evaluation that throws records its error event with the evaluated flag's own marking, because that definition was read before the failure. Event generation keys on that value alone and does not read the evaluation reason.
• The server SDK now depends on launchdarkly-java-sdk-internal 1.13.0, whose event processor suppresses individual events for marked evaluations and splits the summary counters by the marker. CI for this change cannot pass until that version is released.
• The OVERRIDE specification's vector runner now also asserts the per-evaluation summary marking.

Flag overrides are currently experimental and subject to change.

This PR depends on the override layer change (rlamb/overrides-java-override-layer) and is based on that branch; retarget it to feat/overrides once that branch merges.

The existing file data source keeps its current behavior; this change does not touch its code paths.

SDK-3246

---

Note

Overview
Wires override-affected evaluations into the server SDK analytics path per the OVERRIDE spec: evaluations that read override-store data (flag, prerequisite, or segment) pass an overrideAffected flag into EventProcessor.recordEvaluationEvent, which launchdarkly-java-sdk-internal 1.13.0 uses to suppress individual feature/debug events and emit summary counters tagged with overrideAffected: true.

EventProcessor adds a default overload with the new parameter (existing custom processors keep compiling by ignoring it). The evaluator’s EvaluationRecorder forwards EvalResult.isOverrideAffected() for success, prerequisite, type-mismatch, and error paths; prerequisite records use the prerequisite’s own marking. Tests cover client-level marking, flushed payload shape, spec vectors summaryOverrideAffected, and marked error events.

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

_{Opened from termag}

[kinyoklion]

bugbot review

[cursor]

Stale Bugbot comment from a previous run.

[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 0a91418. Configure here.}