ci: typecheck only what the plugin actually imports

The release workflow failed on `tsc --noEmit`: the plugin's tsconfig
globbed `../engine-js/src/**/*.ts`, which sweeps in the engine's *Node*
adapters (`src/pdf.ts`, `src/vlm.ts`). Those import `@napi-rs/canvas` and
`pdfjs-dist/legacy` — dependencies of the engine-js package, which CI
never installs because it runs `npm ci` in plugin/ alone. It passed
locally only because engine-js/node_modules happened to be populated from
running that package's tests, so the check was quietly machine-dependent.

Listing just the plugin's own sources is both the fix and the more
accurate description: tsc follows imports, so engine core/ and browser/
are still fully checked — verified by planting a type error in
browser/device.ts and watching it fail — while the Node adapters, which
the plugin never imports, are left to engine-js's own tsconfig.

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

Author: rcurrie

plugin/tsconfig.json

@@ -14,5 +14,13 @@
     // Bundler-mode resolution; point at it directly.
     "paths": { "onnxruntime-web": ["./node_modules/onnxruntime-web/types.d.ts"] }
   },
-  "include": ["*.ts", "../engine-js/src/**/*.ts"]
+  // Only the plugin's own sources are listed. tsc follows imports from here, so
+  // the engine's core/ and browser/ modules are still fully checked — while its
+  // *Node* adapters (src/pdf.ts, src/vlm.ts) are not, which is the point: they
+  // import @napi-rs/canvas and pdfjs-dist/legacy, dependencies of the engine-js
+  // package that the plugin does not install. Globbing all of engine-js/src
+  // typechecked clean on a machine that happened to have engine-js/node_modules
+  // populated, and failed in CI, which installs only plugin/. engine-js has its
+  // own tsconfig for its own files.
+  "include": ["*.ts"]
 }