feat(chapter-03): add Supabase migrations as database history
Chapter: 03 - Database evolution. Plain-English map: Introduce Supabase CLI configuration and timestamped migrations so database changes can be reviewed, applied, and repeated over time. Why it matters: A single schema file shows what the database looks like today, but not how it got there. Migrations tell future maintainers when and why the shape changed. Principle: Schema changes should be versioned like application code. Existing deployments need an incremental path instead of a one-shot reset. Precedent borrowed: The fork report's Docker/local-development cluster, Supabase practice, and upstream PR #113's database-integrity work. Upstream base: willchen96/mike@d39f580. Original local commit: bc72e34.
| Repository | amal66/mike |
|---|---|
| Author | Amal <mamalanand3@gmail.com> |
| Authored | |
| Parents | 5ad6715c |
| Stats | 3 files changed , +442 |
| Part of | Supabase migrations and database integrity |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-c72b8c74.md
from inside the repo you want the change in.