fix(eve): resolve dev model module map from authored source

[oksr]

Description

Fixes #104.

Under eve dev, model resolution loaded the compiled module map with the raw loader (loadCompiledModuleMap). That loader statically re-imports authored entry modules, so a run-handler schedule importing a channel via a .js specifier crashed the turn with LoadCompiledModuleMapError (native ESM can't map the .js specifier to the dev snapshot's .ts source). Builds and production were unaffected.

The fix routes model resolution through the runtime's existing loadRuntimeCompiledModuleMap (now exported from compiled-agent-cache.ts), which already hydrates source-backed/dev runs through the authored-source loader and falls back to the raw loader for bundled/production. One call swapped; production path unchanged.

How did you test your changes?

• Added packages/eve/test/scenarios/schedule-channel-model-resolution.scenario.test.ts: spawns a real eve dev subprocess (with real, unmocked model resolution) for an agent whose run-handler schedule imports a channel, then asserts a turn starts and resolution does not raise LoadCompiledModuleMapError. It fails before the fix with the exact error and passes after. (In-process tests can't catch this: vitest's resolver maps .js→.ts, and the model mock seam skips the load.)
• Manually verified against a real agent running this branch's build: a run-handler schedule that delivers to a Telegram channel failed with LoadCompiledModuleMapError under eve dev before the fix, and after it the session resolved the model, ran the turn, and delivered the message.
• pnpm typecheck, pnpm lint, pnpm guard:invariants, pnpm test:unit, pnpm test:integration, pnpm test:scenario all pass.

PR Checklist

• I ran the relevant checks from CONTRIBUTING.md
• I added tests and documentation where relevant
• I added a changeset if this touches the published eve package
• DCO sign-off passes for every commit (git commit --signoff)

[vercel]

@oksr is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[AndrewBarba]

Thanks a lot we'll take a look at this Monday. We're just wrapping up some plumbing on our side so we can officially accept outside contributions, safely run CI etc.