Browser docs advertise unshipped RVF APIs; WasmBackend has no persistence export/import

[thesoulpole]

Versions

• @ruvector/rvf@0.2.3
• @ruvector/rvf-wasm@0.1.7
• agentdb@3.0.0-alpha.17

Observed published surfaces

• @ruvector/rvf@0.2.3 exports a working WasmBackend; create, ingest, query, and status work in memory.
• The advertised WasmRvfStore symbol is absent from @ruvector/rvf-wasm.
• The high-level RvfDatabase exposes no byte export/open API, so the working WASM database cannot be durably saved through the public SDK.
• agentdb/browser is documented but is not exported.
• None of these packages declares a React Native entry point.

Exact-name repository searches found WasmRvfStore and createBrowserDb in documentation/examples, not in the shipped implementation.

Impact

A browser integration can work during one page lifetime but cannot implement supported IndexedDB/OPFS persistence through the high-level API. Consumers following the examples receive missing-export errors. React Native/Expo users may also mistake a mobile C FFI design for a published JavaScript integration.

Requested fix

1. Correct the READMEs/examples to describe the currently shipped in-memory WasmBackend.
2. Expose a supported exportBytes() / openBytes() or equivalent API through WasmBackend/RvfDatabase.
3. Provide or document an IndexedDB/OPFS persistence adapter.
4. Document React Native/Expo as unsupported unless and until a native module/package is published.

This is primarily a feature/design-gap report; the documentation mismatch can be fixed independently and immediately.