Freeze event-type ABI: internal constructors + consistent copy() (closes #15)

[mibrahimdev]

What

HttpEvent, MqttEvent, BleEvent were public data classes with all-public constructors, but instances are only ever built inside the loggers — consumers only read them. Public constructors (and copy()) freeze the field list: adding a field later is a source/binary break. This narrows the surface so a field can be added later without breaking consumers. Closes #15.

Changes

• Primary constructors → internal on all three event types in both :sharingan and :sharingan-noop. data is kept, so consumers can still destructure (componentN) and when-match.
• Added @ConsistentCopyVisibility so the generated copy() / copy$default follow the now-internal constructor.
• Regenerated BCV dumps (.api + .klib.api) for both modules.

⚠️ Decision for your review: copy() is also frozen

The issue asked for internal constructors. An internal constructor alone leaves copy() public (Kotlin keeps it public for back-compat) — so event.copy() would still be a frozen ABI and adding a field would still break it. That's a half-freeze that doesn't deliver #15's stated goal.

I went the full-freeze route with @ConsistentCopyVisibility, which removes public copy()/copy$default too. Net effect on the public surface:

- public fun <init> (…)              ← removed
- public synthetic fun <init> (…)    ← removed
- public final fun copy (…)          ← removed
- public static synthetic fun copy$default (…)  ← removed
  public final fun component1..N ()  ← kept (destructuring)
  public final fun getX ()           ← kept (reading)
  equals / hashCode / toString       ← kept

If you'd rather keep copy() public (constructor-only freeze), drop the three @ConsistentCopyVisibility annotations and re-run ./gradlew apiDump.

Parity note (relevant to #12)

The change is symmetric across both modules, so the frozen surface stays identical between :sharingan and :sharingan-noop. Separately, I noticed a pre-existing divergence the parity check (#12) must handle: :sharingan event classes carry a Compose $stable field that :sharingan-noop doesn't (Compose is only on the real module). It predates this PR — flagging it so #12's parity check normalizes/ignores $stable rather than failing on it.

Acceptance criteria

• Event-type primary constructors are internal
• Consumer read/when-match/destructure still compiles (sample builds; sample constructs no events)
• BCV .api dumps regenerated to reflect the narrowed surface
• No asymmetric change to the noop surface (parity preserved)

Verification

:sharingan:testDebugUnitTest + :sharingan-noop:testDebugUnitTest green · ./gradlew apiDump regenerated · :sample:composeApp:compileDebugKotlinAndroid green.

Note: the full build+iOS-test gate (#22, PR #25) isn't on main yet, so this PR only runs api-check. Once #25 merges, rebasing this PR would also exercise the iOS build.

🤖 Generated with Claude Code