Eval runner: load operator env files at startup
npm run evals previously saw only shell-exported variables; the operator keeps keys in repo-root .env.local. Loader reads .env.local / .env / backend/.env (in that order, existing environment always wins), so keys work from any of the documented locations. Values stay in the process environment; nothing is printed or persisted. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
| Repository | Sloth-ninja/JessicaOSS |
|---|---|
| Author | sloth-ninja <ezanahaddis@gmail.com> |
| Authored | |
| Parents | e1fea922 |
| Stats | 3 files changed , +43 |
| Part of | Excise CourtListener (US case-law) integration |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-c67faa97.md
from inside the repo you want the change in.