Implements all 39 tasks from specs/003-ticketing/tasks.md across all
three user stories -- Phase 5 of the roadmap.
Schema (prisma/schema.prisma + migration):
- Ticket (code, status, version for optimistic concurrency,
idempotencyKey, customerId FK), Problem, TicketMessage,
TicketAttachment per docs/06, with Product/Category/
CustomerReference back-relations.
User Story 1 -- ticket/problem creation (P1, MVP):
- Explicit 12-state lifecycle adjacency table
(ticket-state-machine.ts), not "any transition allowed."
- Ticket code generation (<PRODUCT_CODE>-<YEAR>-<SEQUENCE>) scoped
by the actual code prefix, not productId -- see the collision bug
fixed below.
- Idempotency-key enforcement via atomic create-then-catch-conflict
(never a read-then-write race), completing the FR-012 placeholder
from 002-saas-integration.
- Explicit-reference-only recurring-problem linking (no fuzzy
matching -- that's a future AI-support concern).
- POST /v1/support/requests (002-saas-integration) now creates a
real ticket instead of echoing context back.
- PATCH /tickets/:id/status with expectedVersion-based optimistic
concurrency (409 on stale version, 400 on an invalid transition).
User Story 2 -- typed messages (P2):
- Message type -> visibleToCustomer mapping is a fixed constant map,
never caller-supplied; customer-scoped reads filter at the query
layer so an internal note is never fetched, not just hidden.
- POST/GET /tickets/:id/messages (customer-scoped) and
GET /agent/tickets/:id/messages (agent-scoped).
User Story 3 -- attachment pipeline (P3):
- Presigned-PUT upload (new getPresignedUploadUrl on the existing
storageService) -- file bytes never transit this API.
- A MalwareScanner interface with a fail-closed placeholder
(UnimplementedPlaceholderScanner) since no scanner exists in this
stack -- it always reports 'infected', never silently 'clean'.
- The existing attachments-queue job stub now actually calls the
scanner and updates scanStatus; registerAttachmentWorker() is
wired into bootstrapQueue() (previously defined but never called).
- Downloads are gated on scanStatus === 'clean' -- currently always
refused until a real scanner replaces the placeholder.
- MinIO added to docker-compose.{test,development}.yml for local/CI
S3-compatible storage, matching doc 04's explicit guidance.
Two real bugs found and fixed via integration testing against a
live Postgres/Redis/MinIO (not just typechecked):
- Ticket codes could collide across different products: the
sequence counter was scoped by internal productId, but the code
column's uniqueness is global, and deriveProductCode's 4-character
truncation means different products can share a prefix. Fixed by
counting against the actual code prefix instead.
- Three existing 002-saas-integration integration tests' cleanup
started failing an FK RESTRICT check once ticket creation was
wired in (deleting a Product before the Ticket/Problem that now
reference it). Fixed their afterAll ordering.
All 9 integration test files (24 tests, spanning this feature and
the pre-existing suite) verified passing against real Postgres,
Redis, and MinIO, including a genuine presigned-PUT/GET round trip.
Full quality gate (typecheck/lint/format/architecture/unit tests)
passes.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
34 lines
892 B
Bash
34 lines
892 B
Bash
NODE_ENV=development
|
|
PORT=4501
|
|
|
|
# Build
|
|
BUILD_COMMAND=npm run build:development
|
|
|
|
# Database
|
|
POSTGRES_HOST=postgres
|
|
POSTGRES_DB=support_dev
|
|
POSTGRES_USER=support_user
|
|
POSTGRES_PASSWORD=CHANGE_ME
|
|
DATABASE_URL=postgresql://support_user:CHANGE_ME@postgres:5432/support_dev
|
|
|
|
# Redis
|
|
REDIS_HOST=redis
|
|
REDIS_PORT=6379
|
|
REDIS_PASSWORD=CHANGE_ME
|
|
|
|
# Security & CORS
|
|
JWT_SECRET=CHANGE_ME_32_CHAR_MINIMUM_SECRET
|
|
JWT_ACCESS_EXPIRES=15m
|
|
JWT_REFRESH_EXPIRES=7d
|
|
|
|
# 64 hex chars (32 bytes) — generate with: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
|
|
INTEGRATION_CREDENTIAL_ENCRYPTION_KEY=CHANGE_ME_64_HEX_CHARACTERS
|
|
CORS_ORIGINS=http://localhost:3000
|
|
|
|
# AWS S3 / storage (MinIO locally — see docker-compose.development.yml)
|
|
AWS_REGION=us-east-1
|
|
AWS_S3_BUCKET=supporthub-attachments
|
|
AWS_ACCESS_KEY_ID=CHANGE_ME
|
|
AWS_SECRET_ACCESS_KEY=CHANGE_ME
|
|
AWS_S3_ENDPOINT=http://minio:9000
|