Consolidated UzzOPS PostgreSQL/Supabase schema from repo migrations (public tables, columns, types, notes, indexes, grouped by domain). Use when implementing or debugging the UzzOPS data layer (API routes, hooks, Zod, SQL, RLS-related work) or when the user names UzzOPS tables/domains (tenants, company_members, profiles, projects, features, sprint_features, sprints, risks, marketing_*, gantt_*, product_*, md_imports, reuniao_*, etc.). Prefer this over guessing column types; full detail is in references/supabase-schema-from-migrations.md (snapshot from checkpoints/2026-04-07_uzzops/08_SUPABASE_SCHEMA_FROM_MIGRATIONS.md). Aligns with checkpoints/PROMPT_CHECKPOINT_UZZOPS.md Phase 5. If migrations changed after the snapshot, treat database/migrations/ as source of truth and refresh the reference file.
Provide accurate table and column context for UzzOPS without re-reading every SQL migration. The bundled Markdown is a single consolidated schema (see its header for the migration range).
features, sprints, marketing_campaigns).## DOMINIO: heading in the reference) or search for a line like ### `public.features` (swap the table name).database/migrations/ is authoritative if it disagrees with the reference; refresh references/supabase-schema-from-migrations.md when the schema changes.CREATE POLICY statements when policies matter.tenant_id and membership via company_members on most app tables.Replace references/supabase-schema-from-migrations.md with an updated checkpoints/.../08_SUPABASE_SCHEMA_FROM_MIGRATIONS.md or a freshly generated equivalent from database/migrations/.