entroly-wasm 0.19.5 → 0.19.8

package/js/server.js

@@ -157,7 +157,9 @@ class EntrolyMCPServer {
       }
 
       case 'recall_relevant':
-        return this.engine.recall(args.query, args.top_k || 5);
+        // Use BM25-backed relevance recall, not SimHash near-duplicate recall.
+        // This mirrors the Python MCP server's recall_relevant path.
+        return this.engine.recall_auto(args.query, args.top_k || 5);
 
       case 'record_outcome': {
         const ids = (args.fragment_ids || '').split(',').map(s => s.trim()).filter(Boolean);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "entroly-wasm",
-  "version": "0.19.5",
+  "version": "0.19.8",
   "description": "Information-theoretic context optimization for AI coding agents. Zero-friction, pure WebAssembly - no Python dependency.",
   "main": "index.js",
   "types": "pkg/entroly_wasm.d.ts",

package/pkg/entroly_wasm.d.ts

@@ -93,6 +93,22 @@ export class WasmEntrolyEngine {
      * Semantic recall of relevant fragments.
      */
     recall(query: string, top_k: number): any;
+    /**
+     * AUTO retrieval — zero-config: relevance recall is *always* a
+     * relevance need, so route to BM25, never the SimHash `recall()`.
+     * Mirrors entroly-core's `recall_auto` exactly so every surface
+     * (pip / Python-MCP / npm-wasm) ships ONE behaviour.
+     */
+    recall_auto(query: string, top_k: number): any;
+    /**
+     * BM25 relevance retrieval — byte-identical behaviour to
+     * entroly-core's `recall_bm25` (same ported `bm25.rs`, same schema
+     * incl. the auditable score breakdown). This is the npm/wasm half
+     * of the cross-runtime parity fix: SimHash `recall()` is a
+     * near-duplicate metric (~0.44 R@1); a real BM25 is the correct
+     * tool (~1.0). pip / Python-MCP / npm now behave the same.
+     */
+    recall_bm25(query: string, top_k: number): any;
     /**
      * Record failed outcome for specific fragment IDs.
      */

package/pkg/entroly_wasm.js

@@ -209,6 +209,38 @@ class WasmEntrolyEngine {
         const ret = wasm.wasmentrolyengine_recall(this.__wbg_ptr, ptr0, len0, top_k);
         return ret;
     }
+    /**
+     * AUTO retrieval — zero-config: relevance recall is *always* a
+     * relevance need, so route to BM25, never the SimHash `recall()`.
+     * Mirrors entroly-core's `recall_auto` exactly so every surface
+     * (pip / Python-MCP / npm-wasm) ships ONE behaviour.
+     * @param {string} query
+     * @param {number} top_k
+     * @returns {any}
+     */
+    recall_auto(query, top_k) {
+        const ptr0 = passStringToWasm0(query, wasm.__wbindgen_malloc, wasm.__wbindgen_realloc);
+        const len0 = WASM_VECTOR_LEN;
+        const ret = wasm.wasmentrolyengine_recall_auto(this.__wbg_ptr, ptr0, len0, top_k);
+        return ret;
+    }
+    /**
+     * BM25 relevance retrieval — byte-identical behaviour to
+     * entroly-core's `recall_bm25` (same ported `bm25.rs`, same schema
+     * incl. the auditable score breakdown). This is the npm/wasm half
+     * of the cross-runtime parity fix: SimHash `recall()` is a
+     * near-duplicate metric (~0.44 R@1); a real BM25 is the correct
+     * tool (~1.0). pip / Python-MCP / npm now behave the same.
+     * @param {string} query
+     * @param {number} top_k
+     * @returns {any}
+     */
+    recall_bm25(query, top_k) {
+        const ptr0 = passStringToWasm0(query, wasm.__wbindgen_malloc, wasm.__wbindgen_realloc);
+        const len0 = WASM_VECTOR_LEN;
+        const ret = wasm.wasmentrolyengine_recall_bm25(this.__wbg_ptr, ptr0, len0, top_k);
+        return ret;
+    }
     /**
      * Record failed outcome for specific fragment IDs.
      * @param {string} fragment_ids_json