c7aac460b79fa6a06e3baa9f0a9f4e0a7c4150e9
tests/concurrency/escalation-idempotency.test.ts fires the same escalation trigger (escalationService.handleBreach) concurrently more than once for the same ticket against real Postgres, asserting exactly one EscalationEvent and one current Assignment result every time — verified across 10 repeated runs (SC-003). The database-level unique-violation is visibly caught and absorbed in the logs, confirming the fix (previous commit) actually engages under a genuine race rather than being untested code. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Development
- docker compose --env-file .env.development -f docker-compose.development.yml up -d --build
Test
- docker compose --env-file .env.test -f docker-compose.test.yml up --build
Production
- docker compose --env-file .env.prod -f docker-compose.prod.yml up --build -d
Stop
- docker compose -f docker-compose.prod.yml down
List Containers
- docker compose --env-file .env.development -f docker-compose.development.yml ps
Logs
- docker compose --env-file .env.development -f docker-compose.development.yml logs -f
Database Migrations
- Local (using .env.development):
- Create/apply new migration:
npx prisma migrate dev --name <name> - Push schema directly (prototype/sync):
npx prisma db push - Deploy pending migrations:
npm run prisma:deploy
- Create/apply new migration:
- Inside Docker Container:
docker exec -it support-api-development npx prisma migrate deploy
Database Seeding
- Local:
npm run prisma:seed(ornpx tsx --env-file=.env.development prisma/seed/index.ts)
- Inside Docker Container:
docker exec -it support-api-development npm run prisma:seed
Languages
TypeScript
93.2%
PowerShell
6.5%
JavaScript
0.2%