v1.2.1

• Fix: eval-summary telemetry counters now report reason as the numeric wire code (1=STATIC 2=TARGETING_MATCH 3=SPLIT), matching the backend SDKs. Previously the counter carried the OpenFeature-style string form (e.g. "TARGETING_MATCH"), which the telemetry ingestion API's stricter validation could reject — evaluation-summary batches containing a rule-matched evaluation could be dropped as a result. The ingestion service now also accepts and normalizes the string form, so existing 0.0.16–1.2.0 clients work without upgrading; this release aligns the SDK with the canonical wire contract. Counters without a reason are unchanged (field omitted). No API changes.