Inline JavaScript resolves dynamic import() from / instead of the working directory

Inline execute / evaluate code cannot import a package installed in the VM's working directory.

Repro

const vm = await AgentOs.create({ permissions: { network: "allow" } });
await vm.javascript.npm.install(["zod"]);            // installs to /workspace/node_modules
await vm.javascript.evaluate(`import("zod").then(() => "ok")`);

Actual
Cannot resolve module 'zod' (imported from '/[agentos-evaluation.js]'). The inline importer path is /[agentos-evaluation.js], /[agentos-inline.js], or /<entry>.js, so resolution starts at /. TypeScript static imports (rewritten to require) do resolve, so the two paths disagree.

Expected
Match node -e: inline code resolves bare specifiers from the working directory.

Workaround
Pass filePath: "/workspace/main.mjs", or run a file with executeFile.

Start by tracing the javascript.evaluate and execute inline-code entry points, then compare dynamic import resolution with static imports and executeFile. Reproduce the issue with a package installed in /workspace; done means bare imports resolve from the working directory like node -e, without requiring filePath.