Files
LexAI/docs/EVALS.md
john kevin asprec efdae32ae1
All checks were successful
CI — Website / Website — typecheck, build (pull_request) Successful in 1m1s
fix: serve the website dist so Coolify answers GET /
Nixpacks built Vite but had no production start command, so Coolify returned Cannot GET /.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-17 22:27:25 +08:00

1.3 KiB

Project evaluations

This file contains small, repeatable checks derived from verified failures. Prefer a deterministic command, test, assertion, lint rule, schema check, or review checklist over a prose-only reminder.

Active failure-derived checks

E-2026-08-17-01 — Website production server answers GET /

  • Prevents: L-2026-08-17-01 (Cannot GET / on Coolify)
  • Type: command
  • How to run: npm run website:build; then from packages/website PORT=34567 node server.mjs and GET http://127.0.0.1:34567/
  • Pass condition: HTTP 200 and body contains LexAI; /healthz returns ok
  • Failure signal: Cannot GET /, connection refused, or 500 dist/ missing
  • Cost: fast
  • Last verified: 2026-08-17 pass (status 200, title present)

Eval template

### E-YYYY-MM-DD-NN — [short check name]

- **Prevents:** [lesson ID and failure mode]
- **Type:** automated test | command | lint/schema rule | manual checklist
- **How to run:** `[exact command or steps]`
- **Pass condition:** [observable condition]
- **Failure signal:** [what indicates recurrence]
- **Cost:** [fast / moderate / expensive]
- **Last verified:** [date and result]

Retired checks

Move obsolete checks here with the reason and the lesson they covered.