Link Supabase CLI to live project

AGENTS.md

@@ -92,7 +92,9 @@ Rules:
 ## Database Change Rules
 
 - Treat the live Supabase project as the source of truth for schema and RLS.
-- Prefer MCP Supabase migrations and inspection tools for schema work.
+- The Supabase MCP connection and the local Supabase CLI are linked to the same live project (`smjictierxsqgdmwobrj`).
+- Use MCP for inspection and verification against the live project.
+- Use the Supabase CLI for linked remote operations and migration workflows when you need a shell-driven path.
 - Document any schema or permission change in the relevant docs.
 - Keep app code and docs aligned with the live schema names (`profiles`, `members`, `marks`), not legacy names.
 

docs/09-database-and-migrations.md

@@ -19,7 +19,9 @@ Latest migration visible in the live project at the time of verification:
 ## Workflow
 
 - Treat the live Supabase schema as authoritative.
-- Inspect schema and policies with Supabase MCP tools before making assumptions.
+- The Supabase MCP connection and the local Supabase CLI point at the same live project (`smjictierxsqgdmwobrj`).
+- Use MCP first for inspection and verification against the live schema and policies.
+- Use the Supabase CLI for linked remote operations and migration workflows when a shell-driven path is more practical.
 - Apply schema changes through Supabase migrations or MCP-driven database changes, not ad-hoc dashboard edits.
 - Update app code and docs in the same change when table names, functions, or permissions change.
 - The current app no longer exposes invite-code provisioning, recovery, or audit-log flows.

supabase/.gitignore

@@ -0,0 +1,8 @@
+# Supabase
+.branches
+.temp
+
+# dotenvx
+.env.keys
+.env.local
+.env.*.local