docs(plans): SeaORM ↔ Supabase 마이그레이션 통합 epic 분해안 (#374)#380
Merged
Conversation
#374 epic 의 design spec — 본 PR 은 spec 작성만, 실행 X. 채택된 방향 + sub-issue 4개 후보를 정의하며, 실행은 #373 (PR #378) 의 1주 0-error 검증 후 시작. 분석 결과: - 현재 SeaORM 62개 vs Supabase CLI 6개 (RawSql 미사용 → SeaORM-native DDL) - dev 는 SKIP_DB_MIGRATIONS=1 로 이미 Supabase 단일, prod 만 두 시스템 공존 - → Option B (SeaORM 폐기) 채택 Phase 분해: 1. baseline — prod schema dump → 1개 idempotent Supabase 마이그레이션 2. 검증 — drift CI 1주 0-error + 수동 dump diff 3. cutover — prod SKIP_DB_MIGRATIONS=1 4. cleanup — migration/ 디렉토리 + main.rs Migrator + env 제거 본 PR 의 wiki:lint 는 #375 의 frontmatter 정합 commit (81aeabe) 의존 (e2e-hardening-reprioritization-design.md 의 기존 에러). 본 PR 머지 후 e2e 파일 에러는 #375 머지로 해소됨. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
#374 epic 의 design spec 작성. 실행 PR 아님 — 분해안만 정의.
채택 방향: Option B (SeaORM 폐기 + Supabase CLI 단독화).
왜 Option B 인가
dev 는 이미 `SKIP_DB_MIGRATIONS=1` 로 Supabase 단일이고, prod 만 두 시스템 공존. 통합 = prod 만 dev 모델로 정렬하는 작업.
분해 — 4 Phase
각 Phase = sub-issue 1개 + PR 1개. 자세한 acceptance / risk 는 본 spec 문서 참조.
선결 조건
정량화 결과 (2026-04-30)
CI 의존
본 PR 의 `wiki:lint` 는 PR #375 의 frontmatter 정합 commit (`81aeabe5`) 에 의존 — `docs/superpowers/specs/2026-04-23-e2e-hardening-reprioritization-design.md` 의 기존 에러 때문. 본 PR 자체가 추가하는 lint 에러 0건. PR #375 머지되면 자동 해소.
Test plan
🤖 Generated with Claude Code