Contact List Riverpod Provider

Contact List Riverpod Provider is a medium-complexity state management layer that depends on contact-repository being complete and stable. Its reactive nature — auto-refreshing when auth context or organization changes — requires careful coordination with the authentication feature team to ensure the session and organization context providers are available and correctly structured before integration. The AsyncValue pattern (loading, error, data states) introduces UI states that all consuming widgets must handle, meaning UI developers need clear contracts for all three states before building screens against this provider. Plan for integration testing that simulates auth context switches and org changes.

Because it is not marked as shared, its scope is bounded to the contact list feature, limiting blast radius of changes.

ContactListRiverpodProvider exposes a set of Riverpod providers that bridge the service layer to the Flutter widget tree. `contactListProvider` and `peerMentorListProvider` are `AsyncNotifierProvider` or `FutureProvider` instances returning `AsyncValue>` and `AsyncValue>` respectively, delegating to `ContactListService`. `contactSearchQueryProvider` is a `StateProvider` whose changes trigger `filteredContactListProvider` and `filteredPeerMentorListProvider` to recompute via `.watch()`. Auth and organization context changes should invalidate the base list providers using `ref.invalidate()` or by watching an auth state provider.

`selectedContactViewProvider` is a `StateProvider` for detail view selection. Providers should use `ref.onDispose()` to cancel any pending async operations. Ensure all providers are registered in the appropriate `ProviderScope` and that family variants are used if multi-org support requires concurrent provider instances.