fix(vite): clear module runner cache before dev worker reload

The dev worker's ViteEnvRunner.reload() re-imports the environment entry
without clearing the ModuleRunner's evaluatedModules cache. When a module's
transform is already populated on the Vite side at fetch time (for example
re-transformed by an assets crawl during the reload itself), fetchModule
answers {cache: true} and the runner reuses the stale evaluation, so the
server keeps executing old code until the dev server is restarted.

Vite's own full-reload handler clears evaluatedModules before re-importing;
do the same here.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: brenelz

src/runtime/internal/vite/dev-worker.mjs

@@ -55,6 +55,11 @@ class ViteEnvRunner {
 
   async reload() {
     try {
+      // Drop stale evaluations so the re-import walks the whole graph.
+      // Without this, any module whose transform is already populated on the
+      // Vite side is answered with `{cache: true}` and its old evaluation is
+      // reused. Vite's own full-reload handler clears the cache the same way.
+      this.runner.evaluatedModules.clear();
       this.entry = await this.runner.import(this.entryPath);
       this.entryError = undefined;
     } catch (error) {