rag-memory-epf-mcp 6.3.2 → 6.4.0-rc.1

package/README.md

@@ -154,6 +154,26 @@ storeDocument(id, content, metadata)
 
 ## Changelog
 
+### v6.4.0 (2026-10-03)
+
+- (Release candidate `6.4.0-rc.1` on the `next` dist-tag; `latest` stays 6.3.2 until the published artifact passes a
+  canary against a real project database.)
+
+- **Changed** `hybridSearch` default ranking = reciprocal rank fusion of the vector and FTS5 candidate lists
+  (k=60). A chunk that only FTS5 finds — typically an exact identifier, filename or setting key — can now reach
+  the top; before, it scored at most 0.0164 and sat under every vector candidate in the measured corpora.
+  `relevance_score` on the default call is a rank score (at most 2/61, comparable only within one call). Measured on frozen snapshots: exact-identifier hit@10 7/20 → 18/20; worse on 0 of
+  203 queries across three corpora.
+- **Changed** the per-result summary path is opt-in (`RAG_MEMORY_SEARCH_SUMMARIES=on`). It embedded every
+  sentence fragment of every candidate (median 121 s per search) and its context boost pushed vector-0 chunks
+  to rank 1. `off` keeps working. Legacy paths (`summaries=on`, `useGraph: true`) keep the 6.3.2 formula.
+- **Changed** with the default model (bge-m3) queries are embedded as raw text: the bge-v1.5 instruction the loader
+  prepended to every query is gone (bge-m3 needs none; stored vectors never had it). A custom `EMBEDDING_MODEL` keeps
+  the previous query instruction. Paraphrase hit@10 7 → 9 of 20, identifier hit@1 7 → 8,
+  document known-item (`hybridSearch`) unchanged or +1; entity known-item (`searchNodes`) hit@10 unchanged,
+  hit@1 -1 / -1 / +1 (hub / uap / hal). No re-index.
+- Details and rollout: `docs/UPDATING.md`, `specs/changes/search-fusion-rrf/proposal.md`.
+
 ### v6.3.2 (2026-09-25)
 
 - **Changed — on macOS the engine takes `-wal` and `-shm` out of cloud sync.** It sets

package/dist/index.d.ts

@@ -3,6 +3,11 @@ import { type SourceInput } from './src/observations/lifecycle.js';
 import { EmbeddingGate } from './src/embeddingGate.js';
 import type { EmbedPriority } from './src/embeddingGate.js';
 import { BackfillCoordinator } from './src/backfillCoordinator.js';
+export declare const LEGACY_QUERY_INSTRUCTION = "Represent this sentence for searching relevant passages: ";
+export declare function embeddingInput(text: string, isQuery: boolean, defaultModel?: boolean): string;
+export declare function makeEmbedFn(model: (input: string, opts: any) => Promise<{
+    data: any;
+}>, defaultModel: boolean): (text: string, dims: number, isQuery: boolean) => Promise<Float32Array<ArrayBuffer>>;
 export declare function compileFtsLiteralQuery(q: string): string | null;
 export declare function resolveDbFilePath(envValue: string | undefined, cwd: string, serverDir: string): string;
 export declare function parseMmapSize(raw: string | undefined): number;

package/dist/index.js

@@ -67,6 +67,24 @@ function printBanner(opts) {
 // operators (every term is double-quoted; special characters stripped exactly
 // as the pre-3.6 hybridSearch sanitizer did). Returns null when nothing
 // searchable remains (contract: caller returns empty results + warning).
+// search-fusion-rrf (query input): what the model sees for a text. For the DEFAULT model (bge-m3) queries are
+// embedded as raw text — the model card: "the BGE-M3 model no longer requires adding instructions to the
+// queries"; measured on the frozen hub snapshot (93 queries, full-corpus vector rank): 36 better, 6 worse, 51 same.
+// A CUSTOM model (EMBEDDING_MODEL set to something else) keeps the pre-change query instruction: the evidence
+// above is for bge-m3 only, and some models (e.g. bge v1.5) still recommend an instruction on queries.
+// Passages are always raw. `isQuery` stays in the signature and in the embedding cache key.
+export const LEGACY_QUERY_INSTRUCTION = 'Represent this sentence for searching relevant passages: ';
+export function embeddingInput(text, isQuery, defaultModel = true) {
+    return isQuery && !defaultModel ? `${LEGACY_QUERY_INSTRUCTION}${text}` : text;
+}
+// The embed function handed to the gate. Exported so the input wiring is testable with a stub model.
+export function makeEmbedFn(model, defaultModel) {
+    return async (text, dims, isQuery) => {
+        const input = embeddingInput(text, isQuery, defaultModel);
+        const r = await model(input, { pooling: 'cls', normalize: true });
+        return new Float32Array(r.data.slice(0, dims));
+    };
+}
 export function compileFtsLiteralQuery(q) {
     const sanitized = q.replace(/["\*\(\)\-]/g, ' ').trim();
     if (!sanitized)
@@ -335,8 +353,12 @@ export class RAGKnowledgeGraphManager {
             .get(EMBEDDING_MODEL, MODEL_REVISION, MODEL_DTYPE, dims, 'cls', 1);
         this.db.prepare(`INSERT INTO server_meta(key,value) VALUES('current_profile_id',?)
       ON CONFLICT(key) DO UPDATE SET value=excluded.value`).run(String(row.id));
-        this.db.prepare(`INSERT INTO server_meta(key,value) VALUES('query_prefix_version','1')
-      ON CONFLICT(key) DO NOTHING`).run();
+        // query_prefix_version: diagnostic marker of the query-input convention of the engine that last INITIALISED
+        // this DB — 1 = instruction prepended to queries (<= 6.3.2, and custom models now), 2 = raw queries (default
+        // bge-m3 since search-fusion-rrf). It is written at init, not per query: it does not prove what the last query
+        // used, which engines are attached, or vector compatibility. Nothing reads it for logic.
+        this.db.prepare(`INSERT INTO server_meta(key,value) VALUES('query_prefix_version',?)
+      ON CONFLICT(key) DO UPDATE SET value=excluded.value`).run(IS_DEFAULT_MODEL_CONFIG ? '2' : '1');
         return row.id;
     }
     // Real model loader used by the gate: version-independent cache dir with a
@@ -374,11 +396,7 @@ export class RAGKnowledgeGraphManager {
             if (role === 'owner')
                 lock.markComplete();
             console.error(`✅ ${EMBEDDING_MODEL} model loaded (${MODEL_DTYPE})`);
-            return async (text, dims, isQuery) => {
-                const input = isQuery ? `Represent this sentence for searching relevant passages: ${text}` : text;
-                const r = await model(input, { pooling: 'cls', normalize: true });
-                return new Float32Array(r.data.slice(0, dims));
-            };
+            return makeEmbedFn(model, IS_DEFAULT_MODEL_CONFIG);
         }
         catch (e) {
             // Cache policy by CAUSE and ROLE (beta 2R B3 -> 4R M1 -> 5R M1), unit-
@@ -3549,6 +3567,9 @@ export class RAGKnowledgeGraphManager {
             throw new Error('Database not initialized');
         if (!this.encoding)
             throw new Error('Tokenizer not initialized');
+        // search-fusion-rrf: summary mode is read ONCE, at call entry (before any await), and used for the
+        // whole call. Opt-in since this change (was opt-out via =off in v5..6.3.2).
+        const summariesOn = process.env.RAG_MEMORY_SEARCH_SUMMARIES === 'on';
         console.error(`🔍 Enhanced hybrid search: "${query}"`);
         // Parity with searchNodes (beta 1R supplement): an unsearchable query gets
         // an explicit warning instead of a silent empty envelope.
@@ -3612,6 +3633,11 @@ export class RAGKnowledgeGraphManager {
             }
             catch (embErr) {
                 vectorDegraded = true;
+                // search-fusion-rrf (D5): a failure on a LATER cross-lingual variant used to leave the earlier
+                // variants' vector candidates in resultMap while the envelope said 'fts-only'. Drop them so the
+                // degraded call really is FTS-only (no vector rank, no summary, no graph) in every mode.
+                resultMap.clear();
+                primaryQueryEmbedding = null;
                 // 'inference_error' (not 'model_not_ready'): model_state may still read
                 // 'ready' here — a contradictory reason pair confused callers (beta B6).
                 degradationReason = this.degradationReason() ?? 'inference_error';
@@ -3619,6 +3645,12 @@ export class RAGKnowledgeGraphManager {
             }
         }
         const vectorResults = Array.from(resultMap.values()).sort((a, b) => a.distance - b.distance);
+        // search-fusion-rrf: vector rank (1-based, best distance across variants) for rank fusion.
+        // Taken here, before FTS5-only candidates are appended to vectorResults below.
+        const vectorRankOf = new Map(vectorResults.map((r, i) => [r.chunk_id, i + 1]));
+        // Default ranking = reciprocal rank fusion of the vector list and the FTS5 list (k=60).
+        // The legacy formula stays for the opt-in diagnostics (summaries on, graph re-ranker on).
+        const rankFusion = !useGraph && !summariesOn;
         // FTS5 full-text search as additional signal (Reciprocal Rank Fusion)
         const ftsBoostMap = new Map();
         try {
@@ -3807,12 +3839,12 @@ export class RAGKnowledgeGraphManager {
                 graphBoost += Math.min(entityBoost, 0.4);
             }
             // Generate semantic summary (skip when degraded — no embeddings available).
-            // RAG_MEMORY_SEARCH_SUMMARIES=off: diagnostic escape hatch (v5) — the summary
-            // path embeds EVERY sentence of EVERY candidate (~100+ inferences per search,
-            // measured 90-120s cold). Off = preview slices + relevanceScore 0; ranking
-            // then rests on vectorSimilarity + boosts. Default unchanged.
+            // search-fusion-rrf: the summary path is OPT-IN (RAG_MEMORY_SEARCH_SUMMARIES=on). It embeds
+            // every sentence fragment of every candidate one at a time (~400 inferences per search on a
+            // real corpus, median 121 s measured 2026-10-03) and its unbounded context boost let
+            // vector-0 chunks take rank 1 (known-item hit@1 9/10 off vs 4/10 on). Default = preview slices.
             let summary, keyHighlight, relevanceScore;
-            if (vectorDegraded || !primaryQueryEmbedding || process.env.RAG_MEMORY_SEARCH_SUMMARIES === 'off') {
+            if (vectorDegraded || !primaryQueryEmbedding || !summariesOn) {
                 keyHighlight = result.text.slice(0, 150);
                 summary = result.text.slice(0, 300);
                 relevanceScore = 0;
@@ -3822,8 +3854,11 @@ export class RAGKnowledgeGraphManager {
                 ));
             }
             const vectorSimilarity = Math.max(0, 1 - result.distance / 2);
-            const ftsBoost = ftsBoostMap.get(result.chunk_id) || 0;
-            const finalScore = Math.max(vectorSimilarity, relevanceScore) + graphBoost + ftsBoost;
+            const ftsBoost = ftsBoostMap.get(result.chunk_id) || 0; // = 1/(60 + FTS rank), 0 if not an FTS hit
+            const vectorRank = vectorRankOf.get(result.chunk_id);
+            const finalScore = rankFusion
+                ? (vectorRank !== undefined ? 1 / (60 + vectorRank) : 0) + ftsBoost
+                : Math.max(vectorSimilarity, relevanceScore) + graphBoost + ftsBoost;
             // Determine document title and source ID
             let documentTitle;
             let sourceId;

package/dist/src/tools/knowledge-graph-tools.js

@@ -277,7 +277,7 @@ export const addObservationsTool = {
 };
 // === HYBRID SEARCH TOOL ===
 const hybridSearchCapability = {
-    description: 'Perform advanced hybrid search combining vector similarity with knowledge graph traversal',
+    description: 'Perform hybrid search over vector and FTS5 candidates with default reciprocal rank fusion and an optional legacy graph re-ranker',
     parameters: {
         type: 'object',
         properties: {
@@ -300,7 +300,8 @@ const hybridSearchCapability = {
     },
 };
 const hybridSearchDescription = () => `<description>
-Hybrid document search: vector similarity + FTS5 BM25 over document chunks, with an **opt-in** knowledge-graph re-ranker.
+Hybrid document search: vector similarity + FTS5 BM25 over document chunks, fused by rank (reciprocal rank fusion,
+k=60, so an exact identifier that only FTS5 finds can still enter the returned top results), with an **opt-in** knowledge-graph re-ranker.
 Default (useGraph false) is the harm-reduced default for finding a fact you know exists (known-item retrieval).
 useGraph: true is a legacy/experimental re-ranker kept for backward compatibility and controlled evaluation — it does not
 add candidates, it only re-orders the vector/FTS pool, and measured on three real corpora (2026-08-17) it pushed the exact
@@ -310,14 +311,14 @@ chunk out of the top-5 in ~40% of known-item queries. For relationship explorati
 <importantNotes>
 - (!important!) **Graph re-ranking is opt-in (default false since v5.3.0)** — it re-orders candidates by matched/connected entity links, which is measured to hurt known-item retrieval; enable it only for backward compatibility or controlled evaluation
 - (!important!) Graph re-ranking does not generate candidates — for "what is connected to X" use openNodes -> getNeighbors
-- (!important!) Results include similarity scores, graph boost, and hybrid rankings
+- (!important!) relevance_score is a RANK score on the default call: 1/(60 + vector rank) + 1/(60 + FTS rank), at most 2/61; it is not a similarity or probability and is only comparable within one call (vector_similarity and fts_boost are reported alongside)
 - (!important!) **Best results when knowledge graph is well-populated** with entities and relationships
 </importantNotes>
 
 <whenToUseThisTool>
 - When you need comprehensive search across documents and knowledge
 - For complex queries requiring conceptual understanding
-- When exploring relationships between concepts
+- Exact identifiers (file names, setting keys, function names, hashes) as well as natural-language questions
 - **Before making decisions** - to gather all relevant information
 - When researching topics that span multiple domains
 - For discovery of implicit connections and patterns
@@ -325,7 +326,8 @@ chunk out of the top-5 in ~40% of known-item queries. For relationship explorati
 
 <features>
 - Vector similarity search using sentence transformers
-- Knowledge graph traversal for conceptual enhancement
+- Rank fusion of vector and FTS5 candidates: an exact term found only by FTS5 can enter the returned top results even when vector candidates are present
+- Optional legacy graph re-ranker (re-orders only; no traversal — use openNodes -> getNeighbors)
 - Hybrid scoring combining multiple relevance signals
 - Entity association highlighting
 - Configurable result limits and graph usage
@@ -333,7 +335,7 @@ chunk out of the top-5 in ~40% of known-item queries. For relationship explorati
 </features>
 
 <bestPractices>
-- Use natural language queries rather than keywords
+- Natural-language questions and exact identifiers both work; pass the identifier itself when you know it
 - Keep graph re-ranking off for "find the fact I know exists"; for "what is connected to this" use openNodes -> getNeighbors, not useGraph
 - Start with broader queries, then narrow down based on results
 - Review entity associations to understand why results were selected
@@ -342,7 +344,7 @@ chunk out of the top-5 in ~40% of known-item queries. For relationship explorati
 </bestPractices>
 
 <parameters>
-- query: Natural language search query (string, required)
+- query: Search query — a natural-language question or an exact term/identifier (string, required)
 - limit: Maximum results to return, default 5 (number, optional)
 - useGraph: Enable knowledge graph re-ranking, default false / opt-in (boolean, optional)
 </parameters>

package/docs/UPDATING.md

@@ -108,6 +108,52 @@ path and holder pid (e.g. `.download-<key>.lock`). Verify the holder process
 is genuinely gone or hung (`ps -p <pid>`), then remove the lock file manually;
 the next start becomes a clean download owner.
 
+## v6.4.0 (schema v14, unchanged): `hybridSearch` default = rank fusion, summaries opt-in
+
+(Release candidate `6.4.0-rc.1` on the `next` dist-tag first; `latest` stays 6.3.2 until the published artifact
+passes a canary against a real project database.)
+
+**What changed.** (1) The per-result summary path runs only with `RAG_MEMORY_SEARCH_SUMMARIES=on` (it used to
+run unless the variable was `off`; `off` still means off). (2) With summaries off and `useGraph: false` — the
+default call — results are ranked by reciprocal rank fusion of the vector list and the FTS5 list:
+`relevance_score = 1/(60 + vector rank) + 1/(60 + FTS rank)`, a list a chunk is absent from contributes 0.
+Healthy-path candidate gathering and depth are unchanged. If vector search fails after an earlier query variant
+succeeded, the call now discards those partial vector candidates and returns a true FTS-only result (the previous
+version could keep them while reporting `fts-only`). `summaries=on` or `useGraph: true` keep the 6.3.2 formula
+(`max(vector_similarity, summary relevance) + graph boost + FTS term`) unchanged.
+
+**Why.** Measured 2026-10-03 on the frozen eval snapshots (spec `specs/changes/search-fusion-rrf/proposal.md`):
+the summary path embedded ~400 sentence fragments per search (median 121 s) and its unbounded context boost let
+vector-0 chunks take rank 1 (known-item hit@1 9/10 with summaries off vs 4/10 on). With summaries off, a chunk
+found only by FTS scored at most 0.0164 against ~0.4-0.6 for every vector candidate, so exact-identifier
+queries surfaced their target in the top 10 for 7/20 queries although FTS ranked it first for 17/20. Rank fusion:
+18/20, and worse than the old formula on 0 of 203 queries across three corpora.
+
+**Query input (same release).** With the default model (bge-m3) queries are embedded as raw text; a custom
+`EMBEDDING_MODEL` keeps the previous query instruction (the evidence below is for bge-m3 only). Up to 6.3.2 the loader prepended the bge-v1.5
+instruction `Represent this sentence for searching relevant passages: ` to every query (hybridSearch, searchNodes,
+graph seeds) while stored vectors were embedded without it; the bge-m3 model card says the model needs no query
+instruction. Measured on the frozen snapshots: hybridSearch paraphrase hit@10 7 -> 9 / 20 and MRR 0.217 -> 0.275,
+identifier hit@1 7 -> 8, known-item unchanged on hub / uap and hit@1 +1 on hal; searchNodes known-item (40 entities per
+corpus) hit@10 unchanged, hit@1 -1 / -1 / +1. No re-index: only query vectors change; rolling back means a restart.
+`server_meta.query_prefix_version` is a diagnostic marker written at init (2 = raw queries with the default model,
+1 = instruction); it does not prove what the last query used.
+
+**What a caller notices.** On the default call `relevance_score` is a rank score — at most 2/61 ≈ 0.0328, no lower
+bound (a chunk in one list at rank r gets 1/(60+r)), comparable only within one call; do not threshold it against
+old values or across queries/modes. `vector_similarity` and `fts_boost` keep their meaning. `content_summary`
+/ `key_highlight` are preview slices unless summaries are turned on. The fragment-summary work is gone from default
+searches: measured query-cached medians were 20 / 10 / 6 ms on the frozen hub / uap / hal runs; with the query
+embedding cache cleared before every call (one Mac, final build) medians were about 220 / 228 /
+203 ms (max 888 ms). Other machines and corpora are unmeasured — this is not a universal millisecond guarantee. With
+`useGraph: true` and the variable unset, summaries are now off; set `RAG_MEMORY_SEARCH_SUMMARIES=on` to reproduce
+the previous summary-enabled graph path.
+
+**Fleet rollout.** No migration. Recommended like v5.3.0: publish an rc on the `next` dist-tag first, run it
+against a real project database (identifier query + known-item probe), then promote to `latest`.
+Regression locks: `test/search-fusion-rrf.test.mjs`, `test/search-summaries-off.test.mjs`, and
+`test/graph-context-explain.test.mjs` (legacy path byte-identical with summaries on).
+
 ## v5.3.0 (schema v14, unchanged): `hybridSearch` graph re-ranking is opt-in
 
 **What changed.** `useGraph` defaults to `false` (was `true`) — in the manager signature, the tool JSON
@@ -207,8 +253,10 @@ the real v14 (this is exactly how code-v8 never ran in production).
 **Diagnostic env (v5)**: `RAG_MEMORY_SEARCH_SUMMARIES=off` disables the per-result
 sentence-similarity summaries in `hybridSearch` (which embed every sentence of every
 candidate — 100+ inferences, 90-120s cold per search, measured). Off = preview-slice
-summaries, `relevance_score` 0, ranking rests on vector similarity + boosts. Default
-unchanged. The 3-arm release harness sets this uniformly across all arms.
+summaries, the internal summary relevance is 0 (the response's `relevance_score` is still the final score) and
+ranking rests on vector similarity + boosts. **Superseded by the next
+release: summaries are off by default and opt-in with `=on`** (see the section above). The 3-arm release
+harness sets this uniformly across all arms.
 
 ## v3.6 breaking response changes
 

package/package.json

@@ -1,6 +1,6 @@
 {
  "name": "rag-memory-epf-mcp",
- "version": "6.3.2",
+ "version": "6.4.0-rc.1",
  "engines": {
   "node": ">=24"
  },
@@ -45,7 +45,7 @@
   "prepare": "npm run build",
   "watch": "tsc --watch",
   "verify:invariants": "node test/chunk-invariants.test.mjs",
-  "verify:engine": "node test/engine-smoke.test.mjs && node test/launch-smoke.test.mjs && node test/sync-atomicity.test.mjs && node test/dedup.test.mjs && node test/search-degradation.test.mjs && node test/entity-embed-cap.test.mjs && node test/migration12.test.mjs && node test/model-cache.test.mjs && node test/embedding-gate.test.mjs && node test/lazy-boot.test.mjs && node test/reconciliation.test.mjs && node test/backfill.test.mjs && node test/fts-query.test.mjs && node test/search-contracts.test.mjs && node test/tool-contracts.test.mjs && node test/bounded-exit.test.mjs && node test/observation-schema.test.mjs && node test/search-graph-default.test.mjs && node test/observation-migration.test.mjs && node test/observation-lifecycle.test.mjs && node test/observation-contracts.test.mjs && node test/observation-search.test.mjs && node test/observation-cascade.test.mjs && node test/observation-realdata.test.mjs && node test/chunker-c.test.mjs && node test/migration14.test.mjs && node test/chunk-params-validation.test.mjs && node test/vector-reuse.test.mjs && node test/entity-range-linking.test.mjs && node test/alias-link-gate.test.mjs && node test/entity-name-boundary.test.mjs && node test/stats-chunking.test.mjs && node test/migration14-realdata.test.mjs && node test/migration14-realdata-sync.test.mjs && node test/search-summaries-off.test.mjs && node test/document-return-contracts.test.mjs && node test/observation-date-prefix.test.mjs && node test/delete-entities-cascade.test.mjs && node test/delete-entities-kg-hygiene.test.mjs && node test/backup-publish-portable.test.mjs && node test/graph-context-explain.test.mjs && node test/eval-graph-role-libs.test.mjs && node test/eval-graph-role-t5b.test.mjs && node --test test/eval-graph-role-t8-fix.test.mjs && node --test test/eval-graph-role-t7-upstream.test.mjs && node --test test/eval-graph-role-t11-decision.test.mjs && node --test test/eval-graph-role-prereq-fix.test.mjs && node test/db-path.test.mjs && node test/mmap-option.test.mjs && node test/wal-exit.test.mjs && node test/wal-sidecar-guard.test.mjs",
+  "verify:engine": "node test/engine-smoke.test.mjs && node test/launch-smoke.test.mjs && node test/sync-atomicity.test.mjs && node test/dedup.test.mjs && node test/search-degradation.test.mjs && node test/entity-embed-cap.test.mjs && node test/migration12.test.mjs && node test/model-cache.test.mjs && node test/embedding-gate.test.mjs && node test/lazy-boot.test.mjs && node test/reconciliation.test.mjs && node test/backfill.test.mjs && node test/fts-query.test.mjs && node test/search-contracts.test.mjs && node test/tool-contracts.test.mjs && node test/bounded-exit.test.mjs && node test/observation-schema.test.mjs && node test/search-graph-default.test.mjs && node test/observation-migration.test.mjs && node test/observation-lifecycle.test.mjs && node test/observation-contracts.test.mjs && node test/observation-search.test.mjs && node test/observation-cascade.test.mjs && node test/observation-realdata.test.mjs && node test/chunker-c.test.mjs && node test/migration14.test.mjs && node test/chunk-params-validation.test.mjs && node test/vector-reuse.test.mjs && node test/entity-range-linking.test.mjs && node test/alias-link-gate.test.mjs && node test/entity-name-boundary.test.mjs && node test/stats-chunking.test.mjs && node test/migration14-realdata.test.mjs && node test/migration14-realdata-sync.test.mjs && node test/search-summaries-off.test.mjs && node test/search-fusion-rrf.test.mjs && node test/query-input.test.mjs && node test/document-return-contracts.test.mjs && node test/observation-date-prefix.test.mjs && node test/delete-entities-cascade.test.mjs && node test/delete-entities-kg-hygiene.test.mjs && node test/backup-publish-portable.test.mjs && node test/graph-context-explain.test.mjs && node test/eval-graph-role-libs.test.mjs && node test/eval-graph-role-t5b.test.mjs && node --test test/eval-graph-role-t8-fix.test.mjs && node --test test/eval-graph-role-t7-upstream.test.mjs && node --test test/eval-graph-role-t11-decision.test.mjs && node --test test/eval-graph-role-prereq-fix.test.mjs && node test/db-path.test.mjs && node test/mmap-option.test.mjs && node test/wal-exit.test.mjs && node test/wal-sidecar-guard.test.mjs",
   "test": "npm run build && npm run verify:invariants && npm run verify:engine",
   "prepublishOnly": "npm run build && npm run verify:invariants && npm run verify:engine"
  },