feat: Populate OpenFeature flag metadata from the evaluation reason

[kinyoklion]

Populates OpenFeature flag metadata with the LaunchDarkly specific parts of the evaluation result, so hooks (including the OpenTelemetry hook) can read them.

• Keys mirror the evaluation reason fields: variationIndex, inExperiment, ruleIndex, ruleId, prerequisiteKey, bigSegmentsStatus.
• Each key is omitted rather than default-valued when it does not apply, so a consumer can distinguish "not in an experiment" from "no information".
• Matches openfeature-java-server#56, openfeature-dotnet-server#61 and openfeature-python-server#53; the naming is being defined in an sdk-specs spec.

No screenshots or staging preview apply - this is a server-side library change with no UI.

Implementation details

Requirements

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

Describe the solution you've provided

ResolutionDetailsConverter#to_resolution_details now passes flag_metadata:

flag_metadata: flag_metadata(reason, is_default ? nil : variation_index)

Each entry is gated on the corresponding reason field being present rather than on the reason kind, so no key is written from a sentinel value. big_segments_status is a symbol in the Ruby SDK, so it is stringified to keep the metadata value types consistent with the other providers.

The README gains a "Flag Metadata" section documenting the keys.

Describe alternatives you've considered

Exposing the reason object itself as one metadata entry would be closer to the LaunchDarkly shape, but OpenFeature flag metadata values are scalars, so the flat keys are the only available shape.

Additional context

docker run --rm -v "$PWD":/app -w /app ruby:3.4 bash -c "bundle install && bundle exec rake"

61 examples, 0 failures; RuboCop clean. 7 new examples cover each key and the omissions.

@cursor review

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

---

Note

Overview
OpenFeature evaluations now include LaunchDarkly-only details on flag_metadata, so hooks (including OpenTelemetry) can read them.

ResolutionDetailsConverter maps variationIndex, inExperiment, ruleIndex, ruleId, prerequisiteKey, and bigSegmentsStatus from the evaluation reason. Keys are omitted when they do not apply (including inExperiment when false, and variationIndex for default values). bigSegmentsStatus is stringified.

The README documents the keys and a usage example. Specs cover each field and the omission cases.

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

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring