The mobile app's settingsService.getNotificationPreferences/ updateNotificationPreferences call GET/PUT /api/v1/settings/notifications, but the backend never registered any /settings/* routes — only /api/v1/notifications/preferences existed. Every load silently 404'd (swallowed by a catch that just logs) and every Save showed a "Failed to save settings" alert; no notification preference was ever read back or persisted for any user. Mount the existing, already-working notificationPreferencesRoutes router at /api/v1/settings/notifications as well, so the mobile client actually reaches the real controller/Prisma logic instead of hitting a dead path. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>