fix: use prisma db push in entrypoint instead of migrate deploy

The app uses db push (no migration files), so migrate deploy was a no-op.
Also removes the redundant migration step from deploy.yaml since the
entrypoint now handles schema sync on every container start.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

.gitea/workflows/deploy.yaml

@@ -126,9 +126,6 @@ jobs:
             echo "=== Building ==="
             docker compose build memento-note
 
-            echo "=== Database migration ==="
-            docker compose run --rm memento-note npx prisma db push --skip-generate
-
             echo "=== Starting ==="
             docker compose up -d --remove-orphans
             docker compose ps

memento-note/docker-entrypoint.sh

@@ -1,8 +1,8 @@
 #!/bin/sh
 set -e
 
-echo "Running Prisma migrations..."
+echo "Syncing database schema..."
-node ./node_modules/prisma/build/index.js migrate deploy
+node ./node_modules/prisma/build/index.js db push --skip-generate
 
 echo "Starting server..."
 exec node server.js