Distillation

Date: Sep 16, 2026

• 🔴 (10:03) User showed a new isNativeOrtLoadError(msg: string) detector in both packages/core/src/embedding-worker-types.ts and packages/core/src/embedding-worker.ts. It first identifies native ONNX Runtime artifacts using onnxruntime_binding.node, libonnxruntime[_providers_*].so/.dylib/.dll, or OrtGetApiBase, then recognizes loader failures including ERR_DLOPEN_FAILED, invalid ELF/Mach-O/Win32 files, file too short, missing shared objects/images/modules, undefined or missing symbols, and dlopen.
• 🔴 (10:03) User showed failed worker pipeline initialization now distinguishes a selected native ONNX Runtime addon load failure and requests worker respawn with WASM forced, rather than treating it as an ordinary purge/retry failure.
• 🔴 (10:03) User stated native ONNX Runtime resolution in packages/core/src/ort-native.ts is fail-closed and must never interrupt WASM fallback.
• 🔴 (10:03) User stated native ONNX Runtime resolution searches only the relevant worker package’s own node_modules and never selects an arbitrary package.
• 🔴 (10:03) User stated resolveNativeOrtBindingPath must never throw: an unresolvable native package is the expected dist-only case and must degrade to WASM fallback rather than crash embedding.
• 🔴 (10:03) User showed native resolver validation canonicalizes paths with realpathSync, validates the resolved binding, and returns the canonical binding only when valid; otherwise it returns null.
• 🔴 (10:03) User showed native ONNX Runtime version discovery checks gateway manifest dependency declarations, including gatewayManifest?.devDependencies?.["onnxruntime-node"].
• 🔴 (10:03) User showed resolver tests covering absent native packages, with the explicit required outcome that resolution returns null and never throws.
• 🔴 (10:03) User showed resolver tests for a declared, hoisted workspace dependency, ensuring supported hoisting can resolve without permitting arbitrary package selection.
• 🔴 (10:03) User showed native binding fixture validation uses platform-specific binary signatures, including Mach-O bytes [0xcf, 0xfa, 0xed, 0xfe], and creates an onnxruntime-node workspace fixture at join(gatewayDir, "node_modules/onnxruntime-node").
• 🔴 (10:03) User showed bundle-level worker tests parameterized with test.each(...) to verify that a selected native addon load failure requests WASM. A test fixture throws new Error("onnxruntime_binding.node: file too short"), launches a Worker, listens for its message, and exercises embedding with inputType: "query".