[abelonogov-ld]

Changes the default LDConfig.eventMaxAge from 7 days to 24 hours. Persisted events that have not been delivered within 24 hours are discarded and counted as dropped, and so is what the SDK stored for a mobile key the application stopped using. Applications can still set eventMaxAge to keep events longer. It has no effect where eventPersistence is .disabled.

Stacked on #538 (tier 3).

• LDConfig.Defaults.eventMaxAge is now 24 * 60 * 60, and the docs on LDConfig.eventMaxAge and ObjcLDConfig.eventMaxAge say so.
• LDConfigSpec asserts the new default.
• Three EventStoreSpec tests that age a batch by 6 days or 1 day and expect it to be kept now age it by 12 hours. The tests that age by 8 or 30 days still exceed the maximum age and are unchanged.

Android counterpart: launchdarkly/android-client-sdk#424.

Tested: LaunchDarklyTests on Mac Catalyst, 1233 tests, 0 failures.

---

Note

Overview
Lowers the default LDConfig.eventMaxAge from 7 days to 24 hours for persisted, undelivered events (and for stale on-disk data tied to abandoned mobile keys). Apps can still raise eventMaxAge; behavior is unchanged when eventPersistence is .disabled.

LDConfig.Defaults, public docs on LDConfig / ObjcLDConfig, the default-config test in LDConfigSpec, and EventStoreSpec expiry fixtures are updated so “recent” batches are aged by 12 hours instead of 1–6 days while “expired” cases still use 8+ days.

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