CustomerProfileNotifier

AutoDispose AsyncNotifier for the edit/view screens. loadClientInfo on build, refreshClientInfo for pull-to-refresh, updatePersonInfo for edits — all gated by ref.mounted checks to avoid setting state after disposal.

1. build() returns getClientInfo() — set loading → data | error.
2. updatePersonInfo: read userServiceProvider BEFORE setting loading (prevents disposed-ref crash), then POST, then state.data on success.
3. Errors rethrow so the calling form can show a SnackBar with the message.

• ref.mounted guard prevents the classic 'setState after dispose' crash when the user navigates away mid-update.
• AutoDispose means stale state goes away when ManageProfileScreen pops — re-entry refetches.
• Calling refreshClientInfo immediately after a successful update is redundant — the update response already contains the fresh data.

• lib/src/features/shared/manage-profile/customer_profile_provider.dart:7 // CustomerProfileNotifier
• lib/src/features/shared/manage-profile/customer_profile_provider.dart:37 // updatePersonInfo (ref.mounted guard)
• lib/src/features/shared/manage-profile/customer_profile_provider.dart:70 // customerProfileServiceProvider (autoDispose)

userServiceProvider is declared twice (here and in personal_info_provider.dart) — both yield the same UserService instance, no problem in practice.