[kinyoklion]

Adds the overrideAffected key to the Flag Metadata table in the @launchdarkly/openfeature-node-server README.

• #2105 started returning overrideAffected: true in OpenFeature flag metadata (via translateResult in openfeature-server-common), but the README table still listed only the six keys from before.
• The new row says the key comes from an experimental override source, which matches how the feature ships.
• The Cloudflare provider README is unchanged. The edge SDK options don't expose dataSystem.overrides, so that provider never returns this key.

Details

Requirements

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

Related issues

• Implementation: #2105

Describe the solution you've provided

One new row in the Flag Metadata table. The table is re-padded to prettier's table formatting.

Describe alternatives you've considered

Leaving the key out of the docs until the spec covers it. Decided against: the key already ships, and hook authors can see it.

Additional context

The OpenFeature provider spec (OFP 3.3.1) does not list overrideAffected yet, and OFP 3.3.3 says a provider MUST NOT add keys the spec doesn't define ("New keys are added to this spec first"). Someone needs to decide whether to add the key to OFP or drop it from the provider. This PR only documents what the provider does today.

Link to Devin session: https://app.devin.ai/sessions/1fed835aeab841a3bedc9471e008f80c
Open in Devin Desktop: https://app.devin.ai/desktop/session/1fed835aeab841a3bedc9471e008f80c?variant=devin
Requested by: @kinyoklion

SDK-3356

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring