fix(ci): migrations idempotentes et deploy prod sans toucher Postgres

Les migrations échouaient sur une base vide (contraintes/index déjà créés par init).
Le workflow deploy ne recrée plus Postgres ni ne force les entrées _prisma_migrations.

Co-authored-by: Cursor <cursoragent@cursor.com>

.gitea/workflows/ci.yaml

@@ -51,7 +51,12 @@ jobs:
 
       - name: Setup test database
         run: |
-          apt-get update && apt-get install -y postgresql-client
+          sudo apt-get update -qq && sudo apt-get install -y -qq postgresql-client
+          for i in $(seq 1 30); do
+            PGPASSWORD=memento_test pg_isready -h postgres -U memento_test -d memento_test && break
+            [ "$i" -eq 30 ] && exit 1
+            sleep 2
+          done
           PGPASSWORD=memento_test psql -h postgres -U memento_test -d memento_test -c "CREATE EXTENSION IF NOT EXISTS vector;"
           npx prisma migrate deploy
 

.gitea/workflows/deploy.yaml

@@ -121,9 +121,8 @@ jobs:
             git fetch origin main
             git reset --hard origin/main
 
-            echo "=== Pull & recreate postgres with pgvector ==="
-            docker compose pull postgres
-            docker compose up -d --force-recreate postgres
+            echo "=== Ensure postgres is running (no recreate — prod data) ==="
+            docker compose up -d postgres
 
             echo "=== Waiting for postgres healthy ==="
             for i in $(seq 1 30); do
@@ -153,9 +152,6 @@ jobs:
             fi
             echo "Backup saved: $DUMP_FILE ($(( DUMP_SIZE / 1024 ))KB)"
 
-            echo "=== Resolve failed prisma migrations ==="
-            docker compose exec -T postgres psql -U "${POSTGRES_USER:-memento}" -d "${POSTGRES_DB:-memento}" -c "UPDATE \"_prisma_migrations\" SET \"finished_at\"=NOW(), \"rolled_back_at\"=NULL WHERE \"finished_at\" IS NULL AND \"rolled_back_at\" IS NULL;" || true
-
             echo "=== Building app images ==="
             docker compose build memento-note
             docker compose build mcp-server