What problem does it solve? Specialist registration in the EOS app requires uploading verification documents (DNI photo and professional title photo) from a React Native mobile app to an Express backend, which involves tricky multipart/form-data handling, correct FormData construction, multer configuration, and private Supabase Storage uploads. ## Core Features & Use Cases - Frontend Upload Flow: Builds a FormData payload with specialty, licenseNumber, dniPhoto, and titlePhoto using expo-image-picker, letting fetch set the Content-Type boundary automatically. - Backend File Handling: Receives files with multer memoryStorage using named fields, validates required inputs, and restricts specialties to dermatologo and cosmetologo. - Private Storage & Persistence: Uploads documents to the private Supabase Storage bucket specialist-docs under per-user paths and inserts a specialist_profiles row with license_status set to pending. - Use Case: When implementing Módulo 3 (Registro de Especialista), follow this workflow to wire the mobile image pickers to the Express endpoint and store verification documents securely without exposing public URLs. ## Quick Start Implement the specialist registration endpoint that accepts DNI and title photos from the React Native app and stores them in the private Supabase specialist-docs bucket.
