Adds a feature matrix to the README mirroring the OpenFeature Ruby SDK's
own feature table, so a reader can see at a glance what the provider
does and does not support.

- One row per OpenFeature SDK feature (providers, targeting, hooks,
logging, domains, eventing, shutdown, tracking, transaction context
propagation, extending), plus initialization and flag metadata.
- Every row is currently supported following the tracking, lifecycle,
eventing, wrapper, and flag metadata work; each note says how the
provider implements it, or that the OpenFeature SDK provides it with no
provider involvement.
- The legend keeps room for `⚠️`/`❌` so unsupported rows can state
whether the limitation is in the OpenFeature Ruby SDK or is a provider
gap.

<details>
<summary>Implementation details</summary>

**Requirements**

- [x] I have added test coverage for new or changed functionality
- [x] I have followed the repository's pull request submission
guidelines
- [x] I have validated my changes against all supported platform
versions

**Related issues**

Follow-up to the audit of LaunchDarkly's OpenFeature providers, which
produced #27, #28, #29, #30 and #31 in this repository.

**Describe the solution you've provided**

The matrix reuses the row set and legend of the [OpenFeature Ruby SDK
feature table](https://github.com/open-feature/ruby-sdk#-features) so
the two can be read side by side, and so the same format can be applied
to the other LaunchDarkly providers. Statements about eventing,
initialization, shutdown, tracking, and flag metadata were checked
against the current implementation in `lib/ldclient-openfeature`.

**Describe alternatives you've considered**

Writing a LaunchDarkly-specific row set instead of mirroring
OpenFeature's — rejected, since the point of the matrix is comparability
with the OpenFeature SDK table and with the other providers.

**Testing**

Documentation only; no code changes.

**Additional context**

Screenshots and a staging preview do not apply to a README change in a
server-side library.

</details>


Link to Devin session:
https://app.devin.ai/sessions/0c452d209ec54b068ba120b4c92b8f6c
Requested by: @kinyoklion

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> Adds an OpenFeature **feature matrix** to the README so readers can
see at a glance what this provider supports.
> 
> The table mirrors the OpenFeature Ruby SDK feature list (providers,
targeting, hooks, logging, domains, eventing, initialization, shutdown,
tracking, transaction context, extending, flag metadata). Every row is
marked supported, with notes on how the provider implements it or that
the SDK handles it. The legend leaves room for partial/unsupported rows
later.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
898abf3. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

🤖 I have created a release *beep* *boop*
---


##
[0.3.0](0.2.0...0.3.0)
(2026-08-25)


### Features

* Emit provider events from LaunchDarkly client status
([#29](#29))
([1b53b0c](1b53b0c))
* Populate OpenFeature flag metadata from the evaluation reason
([#31](#31))
([e6ef78a](e6ef78a))
* Report provider name and version to LaunchDarkly
([#30](#30))
([c5dd94d](c5dd94d))
* Support OpenFeature tracking
([#27](#27))
([709f52d](709f52d))
* Support provider initialization and shutdown
([#28](#28))
([27df803](27df803))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> **Release 0.3.0** — this PR only bumps version metadata from **0.2.0**
to **0.3.0** in `.release-please-manifest.json`,
`lib/ldclient-openfeature/version.rb`, and the `SDK_VERSION` example in
`PROVENANCE.md`, and adds the **0.3.0** section to `CHANGELOG.md`.
> 
> No provider or SDK logic changes appear in the diff. The new changelog
entry documents features already landed on main: OpenFeature
**tracking**, provider **initialization/shutdown**, **provider events**
from LaunchDarkly client status, **flag metadata** from evaluation
reason, and reporting **provider name/version** to LaunchDarkly.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
8416ff3. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>