[kinyoklion]

Summary

This is the fourth step of the flag overrides port described by the OVERRIDE specification. It is based on the override store branch because the phases are stacked; retarget to feat/overrides once that branch merges.

EventInputEvaluation gains override_affected, set by the client for the top-level evaluation and by the evaluator for each prerequisite record from that record's own marking. The event processor keys on this scalar alone and never reads the evaluation reason: an override-affected evaluation produces no individual feature event and no debug event, even when the flag requests them, while its index event and its summary counting are unchanged. An unaffected prerequisite record inside a marked evaluation is still recorded as usual.

The summary counter key becomes (variation, version, override_affected), so override-affected and ordinary evaluations of the same flag, variation, and version accumulate into separate counters instead of collapsing together. A counter that aggregates marked evaluations carries overrideAffected: true in the summary event; the property is present only when true, like the unknown marker. Both the sync and async event processors share this dispatch and output code.

In the all-flags state, an override-affected flag keeps its value, version, and marked reason but is presented with trackEvents and trackReason off and no debugEventsUntilDate, so a consumer bootstrapped from the state sends no individual events for it. When a migration evaluation of an overridden flag replaces the reason with a wrong-type error, the new reason keeps the marking. The async client mirrors these changes.

The OVERRIDE specification vector runner now also asserts the summaryOverrideAffected field of each vector against the marking the client hands to the event processor.

Tests cover the summarizer key split, the marker in the summary output, suppression of feature and debug events through both real event processors (including a marked prerequisite record and a mixed set of evaluations of one flag), the client-side marking of top-level and prerequisite records through a prerequisite tree, the all-flags tracking fields, the wrong-type reason, and an end-to-end payload check that an override-affected flag appears only in the summary.

SDK-3250

An evaluation that fails with an unexpected exception keeps the marking when the flag came from the override layer, so it produces no individual event and the all-flags state presents it with tracking off.

---

Note

Overview
Adds an override_affected marker on evaluation events so flag-override evaluations are handled differently in analytics.

Event pipeline: Override-affected evaluations still update summary counters (with overrideAffected: true when marked) and index events, but no individual feature or debug events are emitted even when tracking is on. Summary counter keys are now (variation, version, override_affected) so marked and unmarked evaluations don't share the same bucket.

Clients (sync + async): Evaluation paths pass override_affected into EventFactory; WRONG_TYPE and exception paths preserve the override marking when applicable. all_flags_state clears trackEvents, trackReason, and debugEventsUntilDate for override-affected flags so bootstrapped consumers don't fire individual events. Prerequisite evaluation records carry their own override marking.

Async FDv2: Late override reloads after client close no longer error when the event loop is closed—notifications are dropped with a debug log.

Specification vector runners and new tests cover summarizer/output behavior, event suppression, prerequisite propagation, and end-to-end payloads.

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

[kinyoklion]

bugbot review

[cursor]

Stale Bugbot comment from a previous run.

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