| name | photo-approval |
| description | Catch photo and delivery proof workflows. Use when building photo upload, approval, or image display. |
| allowed-tools | Read, Write, Grep |
Photo System
Two types:
- Catch photos: supplier → admin approval → buyers see "Fish Caught" with real photo
- Delivery proofs: driver → auto-saved → communal/proxy flagged for admin
Storage: Supabase Storage (migration 005)
Four buckets created:
- catch-photos (public, 1MB max): {flight_window_id}/{species_id}/{timestamp}.jpg
- delivery-proofs (private, 5MB max): {delivery_run_id}/{stop_id}/{timestamp}.jpg
- village-media (public, 50MB max): general village photos, impact stories
- qr-labels (public, 512KB max): QR codes for catch batch traceability
DB: catch_batches table (migration 007) links batches to flight_windows and fish_species.
DB: village_media table (migration 008) tracks approval workflow for village photos.
CRITICAL RULES
- NEVER store photos as base64 in database. Upload to Storage, store URL.
- Compress to max 1MB client-side before upload (cousin on 3G).
- NEVER show unapproved catch photos to buyers.
- NEVER delete photos. Set status=rejected, keep file.
- Delivery proof MANDATORY — driver cannot mark "delivered" without photo upload.
Compression (client-side):
Use OffscreenCanvas: resize to max 1200px wide, JPEG quality 0.8.
Catch approval flow:
Supplier uploads → catch_photos.status=pending → admin /admin/photos queue
→ admin approves → photo becomes buyer-facing → "Fish Caught" notification sent
Keep EXIF on delivery proofs (contains GPS for verification).
