fix: PDF worker loading — use Vite ?url import for reliable asset resolution

The new URL() pattern failed in production because the worker file URL
didn't match the emitted asset path. Using ?url suffix lets Vite emit
the worker as a hashed asset and return the correct URL.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: IM.codes

web/src/components/OfficePreview.tsx

@@ -29,9 +29,9 @@ function PdfPreview({ data }: { data: string }) {
     (async () => {
       try {
         const pdfjsLib = await import('pdfjs-dist');
-        // Use the bundled worker via URL import — Vite handles this
-        const workerUrl = new URL('pdfjs-dist/build/pdf.worker.min.mjs', import.meta.url);
-        pdfjsLib.GlobalWorkerOptions.workerSrc = workerUrl.href;
+        // Vite ?url suffix emits the worker as a hashed asset and returns its URL
+        const workerUrl = (await import('pdfjs-dist/build/pdf.worker.min.mjs?url')).default;
+        pdfjsLib.GlobalWorkerOptions.workerSrc = workerUrl;
         const pdf = await pdfjsLib.getDocument({ data: base64ToArrayBuffer(data) }).promise;
         if (cancelled || !containerRef.current) return;
         containerRef.current.innerHTML = '';

web/src/env.d.ts

@@ -1 +1,7 @@
 declare const __BUILD_TIME__: string;
+
+// Vite ?url suffix — returns the asset URL as a string
+declare module '*?url' {
+  const src: string;
+  export default src;
+}