feat(events): make event serialization usable from another package

[abelonogov-ld]

What

Widens five declarations in com.launchdarkly.sdk.internal.events from package-private to public. Visibility only — no behavior change.

Declaration	What becomes public
EventOutputFormatter	class, constructor, writeOutputEvents
EventSummarizerInterface	interface
AggregatedEventSummarizer	class, constructor
PerContextEventSummarizer	class, constructor
EventSummarizer	class only — so that EventSummary can be named
EventSummarizer.EventSummary	class only

Everything else stays package-private. EventSummarizer and EventSummary gain no callable surface: EventSummarizer's constructors and methods are untouched, and EventSummary cannot be constructed from outside the package. They are public so the type List<EventSummarizer.EventSummary> can be named by a caller passing it from a summarizer to the formatter.

Why

The Android SDK's event durability work summarizes and serializes each event on the thread that recorded it, ahead of the bounded queue that DefaultEventProcessor keeps between the caller and the summarizer. That means it needs the summarizers and the output formatter directly: DefaultEventProcessor only accepts individual events and summarizes them itself, so there is no public way to hand java-sdk-internal a summary that has already been aggregated.

Today the Android SDK gets at them by declaring AndroidEventBuffer in this package — a split package across two artifacts, with a javadoc workaround to keep it out of the published docs. That works, but it is not something to keep: it is fragile under any build that takes package ownership seriously, and it puts a class the Android team maintains inside a package this repo owns.

With these declarations public, that class moves into com.launchdarkly.sdk.android where it belongs, and the split package and its build workaround go away. The important part is that the Android SDK keeps using this implementation of the wire format rather than growing a second copy that could drift from it.

Notes for review

• The diff is modifiers only, apart from one added line of javadoc on EventSummary, which JavadocType requires because it is a newly public type. No existing comment was edited.
• javadoc reports three new no comment warnings, on the two constructors and writeOutputEvents. That is the same warning roughly eighty existing members in this module already produce, and it does not fail the build.
• Event, EventsConfiguration and Sampler were already public and needed no change.
• compileJava, checkstyleMain, javadoc and the com.launchdarkly.sdk.internal.events.* tests all pass.

🤖 Generated with Cursor