Hartmut
3e2b242151
CI / Architecture Guardrails (push) Successful in 2m40s
CI / Lint (push) Successful in 3m17s
CI / Typecheck (push) Successful in 3m27s
CI / Unit Tests (push) Successful in 6m41s
CI / Build (push) Successful in 6m5s
CI / E2E Tests (push) Failing after 4m21s
CI / Fresh-Linux Docker Deploy (push) Failing after 5m43s
CI / Release Images (push) Has been skipped
CI / Assistant Split Regression (push) Successful in 5m11s
- e2e: use prisma db push --force-reset so the job starts from a guaranteed clean schema (previous runs hit missing audit_logs even though push reported in-sync; suspected stale service volume). - docker-deploy: run prisma db push before db:migrate:deploy in app-dev-start.sh. The migrations/*.sql files are idempotent supplements (IF NOT EXISTS guards) that assume base tables already exist; a fresh container has no tables, so the first incremental migration's FK on "users" fails. db push creates the baseline, migrate deploy then layers on the incremental additions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>