[keelerm84]

• feat: Make data kinds public and add SerializedItemDescriptor
  A persistent data store integration in its own gem can only use public SDK types. Today the data kinds live in LaunchDarkly::Impl::DataStore, and the Redis, DynamoDB and Consul cores call LaunchDarkly::Impl::Model.serialize and .deserialize directly.

  DataKind, FEATURES, SEGMENTS and ALL_KINDS move to LaunchDarkly::Interfaces::DataStore. DataKind gains serialize and deserialize, which match the DataKind serialization methods in the Go, Java and .NET SDKs. SerializedItemDescriptor (version, deleted, serialized_item) matches the type that the persistent data store interface takes in those SDKs and in js-core.

  The Impl names stay as aliases, so no SDK code changes. A later change adds the persistent data store interface that uses these types.

• feat!: Remove the Impl::DataStore data kind aliases
  The data kinds are now public in LaunchDarkly::Interfaces::DataStore. The LaunchDarkly::Impl::DataStore names for DataKind, FEATURES, SEGMENTS and ALL_KINDS were internal and had no compatibility guarantee, but the FDv2 store interface docs told store authors to use them. Code that used those names must use the LaunchDarkly::Interfaces::DataStore names instead.

  All SDK code now uses the public names. ldclient-rb/impl/data_store.rb is gone, and ldclient-rb/impl/data_store/data_kind.rb, which now holds only the status provider and update sink, is renamed to status.rb.

---

Note

Overview
Breaking change: DataKind, FEATURES, SEGMENTS, and ALL_KINDS now live on LaunchDarkly::Interfaces::DataStore instead of LaunchDarkly::Impl::DataStore. The internal impl/data_store.rb barrel file is removed; impl code that still needs status plumbing loads impl/data_store/status only.

The public DataKind adds serialize / deserialize (wrapping the model layer) so persistent-store gems can stay on public types, plus SerializedItemDescriptor (version, deleted, serialized_item) aligned with other SDKs. Hash-style [] access and equality/hash behavior are preserved for ordering and dependency tracking.

Every data path in the SDK (streaming/polling updates, FDv1/FDv2 store, file/test data sources, dependency tracker, client reads) now references the Interfaces constants. Specs for DataKind move from spec/impl/data_store_spec.rb to spec/interfaces/data_store_spec.rb, including round-trip serialization and a load-isolated require check.

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

[kinyoklion]

1. DataKind defines eql?/hash but not ==/=== — a reconstructed or Marshal'd kind is value-equal yet identity-unequal, so Model.deserialize's case/when silently returns a raw Hash instead of a FeatureFlag (also breaks ALL_KINDS.include?). In-SDK trigger CANNOT-PROVE (SDK uses only frozen constants); the hazard is for the new public audience the PR creates. Fix: alias_method :==, :eql?.
2. interfaces/data_store.rb has no requires — under the public-types-only require the PR tells store-gem authors to use, serialize/deserialize raise NameError (and even with serialization manually required, NoMethodError on Hash#to_json — json never required). Only full require "ldclient-rb" works — defeats the PR's stated purpose in the gem-dev harness. Fix: two require lines (no circularity, verified).