Peer Mentor Repository

A low-complexity shared repository that is a critical dependency for at least three features: contact list, contact detail, and peer mentor detail. Its early delivery unblocks parallel development across all three feature teams simultaneously. Shared ownership means any interface change has wide regression impact — coordinate with all consuming feature leads before modifying method signatures. Test coverage must include getMentorById, getMentorsByOrganization with and without status filters, both update methods, and the real-time watch stream.

Supabase schema stability is the primary external dependency risk; confirm table structure is finalized before beginning implementation to avoid costly rework.

Wraps the Supabase client (via supabase-client-provider) with typed Dart models using JSON deserialization from Supabase's PostgREST responses. getMentorById and watchMentorById share the same query path, with watch implemented via Supabase's realtime subscription API returning a Stream. getMentorsByOrganization applies an optional .eq('status', statusFilter.name) clause when statusFilter is non-null. Update methods use Supabase's .update() with .eq('id', mentorId) and return void, relying on Supabase's error throwing on failure.

PeerMentorProfile is an immutable Dart class with a fromJson factory. As a shared component, avoid adding feature-specific query logic here — keep it generic and let callers filter in-memory or via the aggregation service layer.