Nicolas
18abae7b6a
Remplace TechStepClassifierService's node-nlp (NlpManager) par services/tech-step-intent-service, un microservice FastAPI/spaCy dedie (PhraseMatcher pour le NER par synonymes, textcat pour la classification d'intention). Corpus (TECH_STEP_TRAINING_DATA) toujours possede par apps/api, pousse au service via POST /v1/train a chaque warm-up ; le service ne touche jamais Postgres (meme posture que services/tech-step-llm-worker). Cote apps/api : - intent-service-client.ts : client HTTP vers le nouveau service - tech-step-matcher.ts : delegue NER + intent classification au client, logique pure (splitIntoClauses, seuil/fallback) inchangee - env.ts : INTENT_SERVICE_BASE_URL/INTENT_SERVICE_SECRET (secret requis, service coeur non optionnel) - server.ts : warm-up avec retry/backoff (service Python demarre a part) - scripts/calibrate-tech-step-threshold.ts : recalibration empirique de CONFIDENCE_THRESHOLD contre le jeu d'eval existant - node-nlp retire (package.json, node-nlp.d.ts, model.nlp du .gitignore) docker-compose.yml : nouveau service tech-step-intent-service (pas de port expose, healthcheck, app en depend). CI : job intent-service-test (pytest) + le job test demarre le service en arriere-plan avant la suite Mocha (jamais de mock d'un service interne, cf specs/dev-conventions.md). Verifie : 26/26 tests pytest du service (dont les offsets caracteres exacts de tech-step-matcher.test.ts), lint + build complets du monorepo, smoke test HTTP reel bout en bout. La suite Mocha et docker compose build/up n'ont pas pu etre executes dans cet environnement (pas de Postgres/Docker disponibles ici) — a confirmer via la CI et en local. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
29 lines
1.8 KiB
Text
29 lines
1.8 KiB
Text
NODE_ENV=test
|
|
PORT=3000
|
|
# Must point at a *different* database than your `.env`'s — `pnpm test`
|
|
# (test-support/reset-db.ts's `resetDatabase()`) TRUNCATEs almost every
|
|
# table before each test. Pointing this at the same database `pnpm dev`
|
|
# uses will wipe real local data on every test run. Easiest setup: same
|
|
# Postgres server/credentials as `.env`, just a different database name —
|
|
# create it once with e.g.:
|
|
# pnpm exec prisma db execute --url "postgresql://USER:PASSWORD@localhost:PORT/postgres?schema=public" --file - <<< "CREATE DATABASE batchcooking_test;"
|
|
# DATABASE_URL="postgresql://USER:PASSWORD@localhost:PORT/batchcooking_test?schema=public" pnpm exec prisma migrate deploy
|
|
DATABASE_URL="postgresql://changeme:changeme@localhost:5432/batchcooking_test?schema=public"
|
|
|
|
# Required, no default on purpose — generate your own, e.g.:
|
|
# node -e "console.log(require('crypto').randomBytes(48).toString('hex'))"
|
|
JWT_SECRET=changeme-generate-a-real-random-secret-at-least-32-chars
|
|
|
|
# Required — the Mocha suite exercises the real techStepClassifier, which
|
|
# now round-trips over HTTP to services/tech-step-intent-service (no mocks
|
|
# of internal services, per this repo's test conventions). Start that
|
|
# service locally first (see its own README) with a matching
|
|
# INTENT_SERVICE_SECRET, or every test touching tech-step-matcher.ts fails
|
|
# with a connection error rather than a useful assertion failure.
|
|
INTENT_SERVICE_BASE_URL=http://localhost:8000
|
|
INTENT_SERVICE_SECRET=changeme-generate-a-real-random-secret-at-least-32-chars
|
|
|
|
# Optional — only needed to exercise tech-step-worker.routes.test.ts's
|
|
# success path (a request with a matching secret); every other test runs
|
|
# fine without it. Any value at least 32 chars works locally.
|
|
# INTERNAL_WORKER_SECRET=changeme-generate-a-real-random-secret-at-least-32-chars
|