Files
faunosteo/.claude/memory/evals.md
T
Bastien Chanot f4bb7cf9e0 chore(memory): capitalize ⚠ WinAnsi hotfix — LRN-021 + EVAL-003 + journal
- LRN-021: pdf-lib StandardFonts use WinAnsi (cp1252) — any non-Latin-1
  codepoint throws on measure or draw. Fix paths: ASCII surrogate
  (quick) or embed TTF via pdfDoc.embedFont (right). CLAUDE.md spec
  prescribed TTF; current StandardFonts is a documented drift.
- EVAL-003: bug slipped past 154/154 CI because roundtrip tests had no
  observation with a requires_vet_referral leaf. Regression test now
  measures a prefixed label via widthOfTextAtSize to canary any future
  non-WinAnsi marker reintroduction.
- journal 2026-05-21 appended with the hotfix note and the
  TTF-migration follow-up.
2026-05-21 03:34:56 +02:00

2.5 KiB

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.


EVAL-003 | 2026-05-21 | PDF vet-marker ⚠ WinAnsi crash slipped past CI

Method: user manual export of a v2.0 horse report containing requires_vet_referral leaves → EditorRoute.tsx:263 PDF export failed Error: WinAnsi cannot encode "⚠" (0x26a0). Result: 154/154 tests stayed green; bug shipped to user-facing path. Static signal absent (the ⚠ literal was visible in the source but typecheck/lint don't flag font-encoding issues). Anomaly: pdf.roundtrip.test.ts exercised export with empty observations + no vet findings. The ⚠ prefix was added in 60e1b04-era (observationPage.ts:407 ternary) without a regression case covering a flagged leaf. Action: hotfix swapped ⚠ → (!) (WinAnsi-safe). Added regression vet-referral marker is encodable by the body font that calls widthOfTextAtSize on a prefixed label — would catch any future non-WinAnsi marker. LRN-021 captured the pdf-lib StandardFonts WinAnsi limitation. Follow-up: switch PDF body to embedded TTF (Inter/Fraunces per CLAUDE.md spec) so the catalog can carry arbitrary glyphs — out of hotfix scope.