# Supabase

Supabase is an optional first-class *discipline*, not a mandatory dependency.

## Read-only evidence in V0.1

`inspectProject()` reports:

- `supabase/config.toml` and `supabase/` presence
- Supabase packages in package manifests
- migration file paths
- an advisory RLS placeholder for later policy inspection
- explicit mutating command names that require care

It does not call the CLI, log in, link a project, start Docker/local services, query a database, generate types, deploy functions, push/reset/pull migrations, or expose credentials.

Official Supabase CLI sources document `supabase init`, `supabase start`, `supabase status`, `supabase link`, `supabase migration new`, `supabase db diff`, `supabase db push`, `supabase db reset`, and `supabase db pull`; these facts and the V0.1 safety boundary are recorded in [`supabase-research.md`](supabase-research.md).

## Future extension seam

A later package may provide a real Supabase adapter behind an opt-in Service/Tool composition. It must query exact installed CLI/API contracts, use migrations for schema changes, test RLS under multiple identities, keep secrets in environment/credential bindings, and classify external writes as SENSITIVE or DANGEROUS.