Ajax Davis dc4846c7b1 fix: set env vars in both Deno.env and process.env for Node.js compat ... The Node.js compatibility layer (npm: specifier) broke environment variable passing because tools imported via npm: expect process.env, not Deno.env. Root cause: Recent commit added npm: specifier for Node compatibility, but env injection code only set Deno.env.set(), not process.env. Fix: Set environment variables in BOTH locations: - Deno.env.set() for esm.sh imports - globalThis.process.env for npm: imports This restores functionality for tools like Firecrawl that require API keys via environment variables. Fixes regression from commit 8562eb5. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>		2025-12-04 17:29:42 +10:00
..
playground	feat: add collated error reporting to batch tool loading	2025-12-04 16:59:12 +10:00
railway-executor	fix: set env vars in both Deno.env and process.env for Node.js compat	2025-12-04 17:29:42 +10:00
web	fix: handle undefined npmKeywords in tool detail page	2025-12-04 17:14:20 +10:00