Loading Gatehouse…
Loading Gatehouse…
Migration ledger
You have already run the SQL, so do not rerun old migrations. Keep these files in the project so future builds, Git history and Vercel work like a tidy machine room.
Security
Private by default
Services
Platform mapped
Build mode
Fast alpha
Expected files
25
001 through 023
Run status
Done
Per your note
Rule
Keep
Do not delete migration history
Risk
Low
If files stay in repo
001
002
003
004
005
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
025
Capshur signal
If Supabase already has the tables, rerunning create table migrations can throw errors. Only run future migration numbers once.
Capshur signal
The files explain what the app expects: service settings, evidence cases, linked proof, jobs, security, reporting, onboarding and more.
C:\capshur\supabase\migrations\ 001_capshur_alpha.sql 002_... 003_tester_feedback.sql ... 023_onboarding_demo_ui.sql