saqib mirandClaude Sonnet 5
82d02bcdcd
Real Anthropic Claude integration per explicit product decision: a ticket's AI session diagnoses the problem via a structured-output call, applies a DB-configurable confidence-band policy (FR-005), and on "proceed" reasons and acts through a small permission/risk-gated tool system (FR-011/FR-012), optionally walking a matching runbook step by step with the application — never the model — owning the step index (FR-015/FR-016). Resolution requires real tool evidence, never customer claims alone (FR-018) — verifyProductResolution is a documented fail-closed placeholder mirroring the existing malware-scanner precedent, since no real per-product operational signal exists yet. AISupportSession.status mirrors onto Ticket.status through 003-ticketing's existing AI_ANALYZING/AI_TROUBLESHOOTING/AI_VERIFYING/AI_RESOLVED/ HUMAN_ESCALATION state machine, discovered during planning to have been built anticipating this exact feature. Two circular module dependencies (escalation<->sessions, tools<->sessions) were designed around rather than found as bugs: escalation is a pure summary formatter with no state dependencies of its own, and tools stays a clean leaf module with zero dependency on ai-support/sessions. Ticket creation enqueues the first diagnosis turn via the existing queue infrastructure (off the hot path of the inbound SaaS integration endpoint); a human actor changing ticket status ends the AI session via the event-bus scaffold that existed in this codebase but had never been wired to anything. A real Prisma limitation was found and fixed before it reached tests: compound-unique upsert rejects null for a nullable key column, so AIConfidencePolicy uses find-then-update/create instead, same fix class 004 already used for the same underlying limitation. Adds 9 unit tests (confidence-band, tool-policy-gate, runbook-step- advance) and 6 integration test files, including the two constitution- required standing E2E scenarios. AI-independent tests were run against real Postgres/Redis/MinIO (88 passed, 0 failed across the full suite, including every pre-existing 002/003/004 test). The AI-dependent tests compile and skip cleanly via describe.skipIf but were not run against a live model — no ANTHROPIC_API_KEY was available in this session; a real key must be supplied before this feature can actually run. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
44 lines
1.3 KiB
Bash
44 lines
1.3 KiB
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
|
|
|
|
# AI Support — real Anthropic Claude integration (specs/005-ai-support). A real key is required
|
|
# for the AI support feature to function; the app boots without one, but every AI session errors.
|
|
ANTHROPIC_API_KEY=CHANGE_ME
|
|
AI_SUPPORT_MODEL=claude-opus-5
|
|
AI_SUPPORT_EFFORT=medium
|
|
AI_SUPPORT_DEFAULT_HIGH_CONFIDENCE=0.75
|
|
AI_SUPPORT_DEFAULT_LOW_CONFIDENCE=0.4
|
|
AI_SUPPORT_DEFAULT_MAX_CLARIFYING_QUESTIONS=2
|
|
AI_SUPPORT_MAX_REASONING_ITERATIONS_PER_TURN=4
|