fix: remove evals/promptfoo from workspace to fix concurrent execution hang

[stack72]

Summary

• Remove evals/promptfoo from the deno.json workspace array
• Add --exclude evals to scripts/compile.ts compile flags
• Regenerate deno.lock (shrinks from 6578 → 1527 lines)

Root Cause

Commit 356fab3 regenerated deno.lock, which fully resolved the evals/promptfoo workspace member's dependency tree for the first time. This pulled in:

promptfoo@0.121.3 → drizzle-orm@0.45.2 → better-sqlite3@12.8.0

better-sqlite3 is a native Node.js addon (C++ SQLite binding). When deno compile --unstable-bundle builds the swamp binary, this native addon gets included in the dependency resolution graph and interferes with Deno's built-in node:sqlite DatabaseSync — causing concurrent model method run processes to hang indefinitely.

Evidence:

• Last good binary: 20260406.174233.0-sha.287b665f — deno.lock had 0 sqlite refs
• First bad binary: 20260406.181921.0-sha.356fab32 — deno.lock had 5 sqlite refs
• The swamp-uat Tier 3 concurrency test (5 concurrent model method run) passes on the good binary and hangs on the bad binary
• Two independent PRs in swamp-uat (Issue 11: Remove deprecated artifact entities and repositories #126, Issue 12: Add data lifecycle and garbage collection #127) both reproduce the same hang

Fix

Remove evals/promptfoo from the workspace so its transitive deps don't pollute the shared deno.lock. The evals directory retains its own package.json and can manage deps independently via npm install.

Test plan

• deno check main.ts — passes
• deno.lock has zero references to sqlite, drizzle, better-sqlite3, or promptfoo
• CI tests pass
• After binary release, swamp-uat Tier 3 concurrency tests pass

🤖 Generated with Claude Code

[github-actions]

Code Review

Blocking Issues

None.

Suggestions

None — this is a clean, well-scoped fix. The root cause analysis is thorough and the change is minimal: removing the workspace member, regenerating the lockfile, and adding the compile exclusion. The --exclude evals addition to scripts/compile.ts is consistent with the existing exclude pattern already in place for other dev-only directories.