Distillation

Date: Sep 16, 2026

• 🔴 (14:50) User stated the embedding runtime switched to native ONNX Runtime because native execution scales with CPU cores (#999).
• 🔴 (14:50) User requires native ONNX Runtime resolution to fail closed and never interrupt the WASM fallback.
• 🔴 (14:50) User requires the native resolver to search only the worker package’s own node_modules; it must never select an arbitrary onnxruntime-node installation from elsewhere in the dependency tree.
• 🔴 (14:50) User requires resolveNativeOrtBinding()-style package resolution never to throw: an unresolvable package is the expected dist-only case and must degrade to WASM rather than crash embedding.
• 🔴 (14:50) User requires nativeIntraOpThreads() to leave ONNX Runtime’s thread default untouched on an unrestricted host; when availableParallelism() === os.cpus().length, it returns undefined. A thread override is only appropriate when availableParallelism() < os.cpus().length, indicating a genuine CPU restriction.
• 🟡 (14:50) Native package resolution uses the literal package naming form @loreai/onnxruntime-<os>-<arch> through ortNativePackageName(). Unknown Linux libc fails closed to WASM, and supported native bindings are validated as canonical files with platform binary signatures such as ELF magic bytes 0x7f 0x45 0x4c 0x46.
• 🟡 (14:50) packages/core/src/embedding-worker.ts configures the WASM backend with wasmEnv.onnx.wasm.proxy = false; the native onnxruntime-node backend ignores these WASM settings. The feature-extraction pipeline uses dtype: "q8".
• 🟡 (14:50) The native-to-WASM recovery protocol uses init-needs-wasm, distinct from init-error. In packages/core/src/embedding/local.ts, the request is one-shot, clears transient initialization debt, and invokes respawnForWasm() so the original request can be resubmitted rather than lost.
• 🟡 (14:51) Runtime/package-boundary work plan contained 6 ordered tasks: 1. “Fix cgroup topology, fail-closed headroom, and pool reservation defects” — completed, high priority; 2. “Audit and finish native loader classification, diagnostic privacy, binary validation, and generated-artifact freshness” — in progress, high priority; 3. “Prove critical guards with fail-first baselines and isolated mutations” — pending, high priority; 4. “Run full format, typecheck, lint, bundle, and test validation” — pending, high priority; 5. “Freeze exact candidate and obtain independent correctness and security reviews” — pending, high priority; 6. “Commit the completed Jujutsu change and report runtime guidance” — pending, medium priority.
• 🟡 (14:51) Assistant stated the remaining work was concentrated at the runtime/package boundary: verify the native resolver against actual package manifests and bundle generation, close diagnostic-privacy and stale-generated-artifact gaps, then prove the guards independently.
• 🟡 (14:51) A repository search found exactly 57 matches for worker outbound/error and WASM-respawn terms across packages/core/src/embedding/local.ts, packages/core/src/embedding-worker.ts, packages/core/src/embedding-worker-types.ts, packages/core/src/vector-worker.ts, packages/core/src/vector-worker-types.ts, and packages/core/src/vector-pool.ts.