[kinyoklion]

Summary

The OpenFeature Java provider shipped 2.0.0 on Nov 5 (#66, start-wait change). The docs install snippets still pin 1.2.1, and the validator resolves the latest 1.x.

• launchdarkly-openfeature-serverprovider: 1.2.1 → 2.0.0 in openfeature/install-the-provider-xml and -gradle
• dev.openfeature:sdk range in openfeature/install-dependencies-gradle: [1.7.0,2.0.0) → [1.16.0,2.0.0), which matches the provider's own build.gradle floor (raised in openfeature-java-server#41)
• sdks.env: LD_JAVA_OPENFEATURE_PROVIDER_VERSION family @1 → @2, so the JVM validator builds against 2.x

The snippet bodies didn't need to change. The Provider(String sdkKey) constructor used by initialize-the-provider is still in 2.0.0. 2.0.0 is published on Maven Central (the GCS mirror still lists 1.2.1 as latest).

Validation: I couldn't run snippets validate --sdk=java-server-sdk locally because no LD keys are available on this machine, so the snippets-validate CI matrix is the check. After release, the ld-docs snippet sync will update the rendered blocks on sdk/openfeature/java.mdx. A companion ld-docs-private PR fixes the prose compatibility statements.

Link to Devin session: https://app.devin.ai/sessions/32cb4af04cfe43929b0e6586ea213773
Open in Devin Desktop: https://app.devin.ai/desktop/session/32cb4af04cfe43929b0e6586ea213773?variant=devin

[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