# Evals Registry Format: EVAL-XXX | Date | What evaluated | Method | Result | Anomalies | Action --- ## EVAL-001 | 2026-05-18 | Scaffold build + test pass Method: pnpm install → pnpm build → pnpm test:run → pnpm typecheck. Result: all pass, 0 errors. Anomalies: pnpm version 11 instead of 9 (corepack issue on host). Action: document in BDR-007, BLK-001. --- ## EVAL-002 | 2026-05-20 | B3 i18n — code review caught hardcoded FR in PDF import Method: cavecrew-reviewer ran against full diff `0a05c47..HEAD` after self-review + analyzer agent both reported CLEAN. Result: reviewer flagged 3 CRITICAL: pdf/import.ts:9, pdf/attachment.ts:9-10, app/routes/HomeRoute.tsx:32 — hardcoded FR error messages leaking to EN UI. Anomaly: prior i18n grep ('Annuler', 'Valider', etc.) missed these because the error-path files contained different French vocabulary ("Ce PDF n'a pas été..."). Implementer's TODO checklist did not include the PDF import error paths since they were not in the original component migration list. Analyzer also missed because the leak only surfaces under EN locale at runtime (no static signal in code). Action: fixed in d602726+next via typed ImportError discriminant (BDR-015). Future i18n migrations should enumerate ALL files that emit user-facing strings (not just components/routes) — include error path files, exception messages, anything that may end up in window.alert or setError.