Node documentation advertises HybridSearch absent from ruvector@0.2.34

[thesoulpole]

Version

• ruvector@0.2.34
• Compared with agentdb@3.0.0-alpha.17
• Node 26.4.0

Reproduction

const ruvector = require('ruvector');

console.log(Object.keys(ruvector).filter(
  key => /hybrid|bm25|keyword|rrf/i.test(key)
));
// []

The published package exposes 206 symbols, but none for hybrid search, BM25, keyword search, or RRF.

The Node API documentation nevertheless shows:

const { HybridSearch } = require('ruvector');

AgentDB separately exports a JavaScript HybridSearch and KeywordIndex, and the RuVector Rust core contains real hybrid-search functionality. The missing piece is the published ruvector Node binding/export.

Impact

Consumers following the Node documentation receive undefined/constructor errors and may design against an API that is not shipped.

Requested decision

Either:

1. Bind and export the Rust hybrid-search functionality from the Node package and add an npm smoke test, or
2. Mark the feature as Rust-only and remove/correct the Node example and package feature claim.

Until a RuVector Node surface ships, the documentation can point JavaScript users to AgentDB's separate hybrid-search implementation if that is the intended supported path.