feat: use cached config if avail on init with openfeature provider

[luxscious]

Implements open-feature/protocol#64 — cache-first initialization for static-context
providers.

feat: cache-first initialization

• SDK initializes immediately from cached config when available, fetches fresh values in the background
• Cache miss path unchanged — blocks on network as before
• Evaluations served from cache surface reason = "CACHED"

feat: OpenFeature provider events

• PROVIDER_READY emitted immediately on cache hit
• PROVIDER_CONFIGURATION_CHANGED emitted when background refresh delivers fresh values
• PROVIDER_ERROR emitted on auth/config errors (400/401/403) during background refresh

feat: cache management

• Persisted cache cleared on auth/config errors so next cold start fetches fresh
• User switch clears in-memory config immediately to prevent serving stale values for the wrong identity

fix: HTTP status code classification

• 403 and other unmapped codes were incorrectly collapsed to 500 and treated as retryable — now classified
  correctly

[Copilot]

Pull request overview

Implements cache-first initialization for static-context providers, adds OpenFeature provider event support, and refines HTTP status classification to better distinguish auth/config errors from retryable server errors.

Changes:

• Add persisted-cache management utilities (per-user cache clearing) and expand HTTP response code handling (403/429 + better default mapping).
• Enable cache-first DevCycleClient initialization with background refresh and config-updated callbacks.
• Add/extend tests around cache-first init behavior, cached evaluation reason mapping, and shared-prefs cache clearing.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
android-client-sdk/src/main/java/com/devcycle/sdk/android/api/DevCycleClient.kt	Cache-first init, background refresh, config-updated callbacks, identity-switch behavior changes
android-client-sdk/src/main/java/com/devcycle/sdk/android/openfeature/DevCycleProvider.kt	Adds OpenFeature provider event observation + cached-eval reason mapping
android-client-sdk/src/main/java/com/devcycle/sdk/android/util/DVCSharedPrefs.kt	Adds clearConfigForUser for persisted cache management
android-client-sdk/src/main/java/com/devcycle/sdk/android/model/HttpResponseCode.kt	Adds 403/429 and adjusts unmapped-code classification
android-client-sdk/src/main/java/com/devcycle/sdk/android/model/EvalReason.kt	Adds source and helper for marking cached evaluations
android-client-sdk/src/main/java/com/devcycle/sdk/android/exception/DVCRequestException.kt	Carries raw status code + adds auth error classification
android-client-sdk/src/main/java/com/devcycle/sdk/android/api/Request.kt	Propagates raw HTTP status into DVCRequestException
android-client-sdk/src/test/java/com/devcycle/sdk/android/api/DevCycleClientTests.kt	Adds tests for cache-first init + user-change/cache-clear scenarios (needs fixes)
android-client-sdk/src/test/java/com/devcycle/sdk/android/openfeature/DevCycleProviderTest.kt	Adds tests for cache-hit init behavior + cached reason mapping
android-client-sdk/src/test/java/com/devcycle/sdk/android/util/DVCSharedPrefsTests.kt	Adds tests for clearing config/expiry per user
android-client-sdk/src/test/java/com/devcycle/sdk/android/model/EvalReasonTests.kt	Adds unit tests for EvalReason.withCachedSource

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 3 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 3 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

PR description says a user switch "clears in-memory config immediately to prevent serving stale values for the wrong identity", but in identifyUser the existing in-memory config (and user used for evaluations/events) is kept until the async fetch completes. That means evaluations right after identifyUser can still be served from the previous user's config. If the intent is to stop serving stale values immediately on user switch, consider clearing/invalidating the in-memory config state (or gating evaluations) at the start of the identify flow.

[jsalaber]

this should be fine, as we await for the config for the new identity to succeed before clearing cache

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In performBackgroundRefresh(), you capture userAtRefreshStart, but refetchConfig() always fetches using latestIdentifiedUser (and will queue using whatever latestIdentifiedUser is at queue-time). If the user changes concurrently (e.g., identifyUser runs while the refresh is being scheduled/queued), the refresh request may be executed for a different user than userAtRefreshStart, yet on error you clear the persisted cache for userAtRefreshStart. This can clear the wrong user's cache and misattribute PROVIDER_ERROR/config errors. Consider refactoring so background refresh fetches for a specific user (e.g., pass userAtRefreshStart into refetchConfig/fetchConfig) and uses that same user for any cache-clearing decisions.

Suggested change

	override fun onSuccess(result: Map<String, BaseConfigVariable>) {
	DevCycleLogger.d("Background refresh succeeded")
	}
	override fun onError(error: Throwable) {
	override fun onSuccess(result: Map<String, BaseConfigVariable>) {
	if (latestIdentifiedUser != userAtRefreshStart) {
	DevCycleLogger.d("Background refresh completed after user changed; ignoring stale result")
	return
	}
	DevCycleLogger.d("Background refresh succeeded")
	}
	override fun onError(error: Throwable) {
	if (latestIdentifiedUser != userAtRefreshStart) {
	DevCycleLogger.w("Background refresh failed after user changed; skipping stale cache/error handling.")
	return
	}

[luxscious]

I believe this is out of the scope of this PR. It's a pre-existing concurrency edge case in refetchConfig that exists independently of our changes