chore: add supabase CLI and restore migration new command (#13)

Adds supabase as a dev dependency so agents can use
`npx supabase migration new <name>` for consistent timestamp
prefixes. Reverts the manual YYYYMMDDHHmmss instructions from
the previous PR.

Co-authored-by: Ona <no-reply@ona.com>

Author: zacharias-ona

.agents/conventions.md

@@ -232,13 +232,10 @@ Pattern: wrap in try/catch, return structured JSON with appropriate status codes
 
 ## Database Migrations
 
-Create migration files manually in `supabase/migrations/` with a UTC timestamp prefix:
-
 ```bash
-# Format: YYYYMMDDHHmmss_<descriptive_name>.sql
-# Use the current UTC time when creating the file.
-# Example (created at 2026-04-14 20:00:00 UTC):
-touch supabase/migrations/20260414200000_add_pages_table.sql
+npx supabase migration new <descriptive-name>
+# Creates: supabase/migrations/<YYYYMMDDHHmmss>_<name>.sql
+# The CLI generates the correct UTC timestamp prefix automatically.
 ```
 
 ```sql
@@ -261,7 +258,7 @@ create policy "workspace members can read pages"
 ```
 
 Rules:
-- Timestamp must be current UTC time — never reuse or backdate timestamps.
+- Always use `npx supabase migration new` — never create migration files manually.
 - One migration per logical change (table + its RLS policies together).
 - Auto-applied on merge to main via the deploy-migrations CI workflow.
 

.gitignore

@@ -41,3 +41,4 @@ yarn-error.log*
 # typescript
 *.tsbuildinfo
 next-env.d.ts
+supabase/.temp/

.ona/automations/bug-fixer.yaml

@@ -99,8 +99,7 @@ action:
                 9. Fix the root cause. Do NOT fix symptoms.
                    - Follow every convention in AGENTS.md without exception.
                    - Add a regression test that would have caught this bug.
-                   - For database changes: create a migration file in `supabase/migrations/` with a UTC
-                     timestamp prefix: `YYYYMMDDHHmmss_<name>.sql` (use current UTC time).
+                   - For database changes: `npx supabase migration new <name>`
                 10. Run the full CI check locally: `pnpm lint && pnpm typecheck && pnpm test`
                 11. Fix any errors before proceeding.
 

.ona/automations/feature-builder.yaml

@@ -95,9 +95,7 @@ action:
 
                 Before coding, decide:
                 - **Database**: does this need a new table, new columns, or new RLS policies?
-                  If yes, create the migration file first in `supabase/migrations/` with a UTC
-                  timestamp prefix: `YYYYMMDDHHmmss_<name>.sql` (e.g. `20260414200000_add_pages_table.sql`).
-                  Use the current UTC time — never reuse or backdate timestamps.
+                  If yes, create the migration first: `npx supabase migration new <name>`
                 - **API**: does this need new API routes? Follow the existing pattern in `src/app/api/`.
                 - **Components**: which existing components can be reused? What new ones are needed?
                   Check `src/components/ui/` (shadcn) before building anything custom.

AGENTS.md

@@ -35,7 +35,7 @@ metrics/           → Daily/weekly metrics snapshots
 - Named exports only. No default exports.
 - Conventional commits: `feat|fix|chore|docs|test|refactor(scope): description`
 - PRs with type `feat` or `fix` must reference an issue: `Closes #N`. Chore PRs (metrics, docs, deps) do not require an issue.
-- Database changes require a migration file in `supabase/migrations/` with timestamp prefix: `YYYYMMDDHHmmss_<name>.sql` (use current UTC time, e.g. `20260414200000_add_pages_table.sql`)
+- Database changes require a migration: `npx supabase migration new <name>`
 - Environment variables: `NEXT_PUBLIC_` prefix only for browser-safe values.
 
 ## Testing

docs/automations.md

@@ -401,9 +401,7 @@ Before writing anything, understand the current codebase:
 
 Before coding, decide:
 - **Database**: does this need a new table, new columns, or new RLS policies?
-  If yes, create the migration file first in `supabase/migrations/` with a UTC
-  timestamp prefix: `YYYYMMDDHHmmss_<name>.sql` (e.g. `20260414200000_add_pages_table.sql`).
-  Use the current UTC time — never reuse or backdate timestamps.
+  If yes, create the migration first: `npx supabase migration new <name>`
 - **API**: does this need new API routes? Follow the existing pattern in `src/app/api/`.
 - **Components**: which existing components can be reused? What new ones are needed?
   Check `src/components/ui/` (shadcn) before building anything custom.
@@ -698,8 +696,7 @@ For infra/config bugs:
 9. Fix the root cause. Do NOT fix symptoms.
    - Follow every convention in AGENTS.md without exception.
    - Add a regression test that would have caught this bug.
-   - For database changes: create a migration file in `supabase/migrations/` with a UTC
-     timestamp prefix: `YYYYMMDDHHmmss_<name>.sql` (use current UTC time).
+   - For database changes: `npx supabase migration new <name>`
 10. Run the full CI check locally: `pnpm lint && pnpm typecheck && pnpm test`
 11. Fix any errors before proceeding.
 

package.json

@@ -31,9 +31,16 @@
     "eslint-config-next": "16.2.3",
     "jsdom": "^29.0.2",
     "playwright": "^1.59.1",
+    "supabase": "^2.91.1",
     "tailwindcss": "^4",
     "twitter-api-v2": "^1.29.0",
     "typescript": "^5",
     "vitest": "^4.1.4"
+  },
+  "pnpm": {
+    "onlyBuiltDependencies": [
+      "supabase",
+      "@sentry/cli"
+    ]
   }
 }