Phase 4 Stage 2: onboarding redesign (client_app + mitra_app)

Verif Choice Sheet on display_name_screen drives the user into either
the verified or anonymous onboarding sub-flow. ESP screen (12 chips,
multi-select, info-only) + USP screen are shared between both branches;
selections persist through to chat_sessions.topics on session start.

OTP-blocked popup (HaloPopup) listens for the four real OTP-rate-limit
error codes (OTP_RATE_LIMIT_PHONE, OTP_RATE_LIMIT_IP, OTP_COOLDOWN,
OTP_ATTEMPTS_EXCEEDED) and drops the user onto the anonymous path with
ESP/USP state preserved.

Auth-providers gating replaces the --dart-define=ENABLE_SOCIAL_AUTH
build flag with server-driven discovery. authProvidersProvider preloads
GET /api/shared/auth-providers at cold start; welcome/register/
force-register screens render Google/Apple buttons only when the
backend reports enabled:true. Falls back to phone-OTP-only when both
providers are off. social_auth_enabled.dart deleted; client_app/CLAUDE.md
updated to reflect the new gating contract.

Mitra app: chat screen renders an ESP chip strip above the first message
bubble when chat_sessions.topics is non-empty.

Backend session.service.js getSessionById SELECTs cs.topics so the mitra
side can read the customer's selected topics.

Maestro flows 02_onboarding_verified.yaml + 03_onboarding_anon.yaml.

Deviation from plan: plan referenced OTP error code 'otp_retry_exhausted';
real codes are OTP_RATE_LIMIT_*/OTP_COOLDOWN/OTP_ATTEMPTS_EXCEEDED -
popup listens for all four. Plan said 'has_paid_first_session'; live
endpoint returns 'has_consulted_before' - used the live field.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

client_app/lib/features/onboarding/esp_topic.dart

@@ -0,0 +1,34 @@
+/// Twelve emotional-state-pick (ESP) topic chips shown on the onboarding ESP
+/// screen. Multi-select, info-only — the picks are persisted on the chat
+/// session at session start and surfaced to the mitra as a chip row above
+/// the first message bubble. They do NOT affect matching, pricing, or routing.
+///
+/// `value` is the wire-format string sent to the backend
+/// (`chat_sessions.topics TEXT[]`). Lowercase snake_case to keep it stable
+/// across UI label tweaks.
+enum EspTopic {
+  relationship('relationship', 'Hubungan'),
+  family('family', 'Keluarga'),
+  work('work', 'Pekerjaan'),
+  study('study', 'Sekolah / Kuliah'),
+  finance('finance', 'Keuangan'),
+  health('health', 'Kesehatan'),
+  friendship('friendship', 'Pertemanan'),
+  selfWorth('self_worth', 'Self-worth'),
+  anxiety('anxiety', 'Kecemasan'),
+  loneliness('loneliness', 'Kesepian'),
+  grief('grief', 'Kehilangan'),
+  identity('identity', 'Identitas');
+
+  final String value;
+  final String label;
+  const EspTopic(this.value, this.label);
+
+  static EspTopic? fromValue(String? v) {
+    if (v == null) return null;
+    for (final t in values) {
+      if (t.value == v) return t;
+    }
+    return null;
+  }
+}