rvagent-wasm-v0.2.0

cortezaproject/cortezarvagent-wasm-v0.2.0May 28, 2026by ruvnet

AI Summary

This release focuses on documentation and metadata corrections, including fixing the npm package name and adding integration patterns for JsModelProvider and addMcpTools.

Key Highlights

Corrected npm package name and build targets
Added JsModelProvider and addMcpTools integration patterns
Added WasmGallery direct API examples
Added CI workflow for npm publishing

New Features

JsModelProvider integration patterns
addMcpTools integration patterns
WasmGallery direct API examples
CHANGELOG.md documentation
Publishing GitHub workflow

Full Release Notes

## @ruvector/rvagent-wasm 0.2.0

### Changes from 0.1.0

**Documentation + metadata release. No Rust changes.**

- Corrected npm package name: `@ruvector/rvagent-wasm` (previously README showed unscoped `rvagent-wasm`)
- Corrected build target documentation: `nodejs` (not `web`) for `@claude-flow/cli` usage
- Added `JsModelProvider` + `addMcpTools()` integration patterns (ruflo ADR-129 Gaps 1 & 2)
- Added `WasmGallery` direct API examples
- Added `CHANGELOG.md`
- Added `.github/workflows/publish-rvagent-wasm.yml` for npm publish via CI

### ADR-129 context

All gap APIs were already present in 0.1.0:
- **Gap 1** (`JsModelProvider` / `set_model_provider`): WASM API complete — wiring gap is in ruflo's `agent-wasm.ts`
- **Gap 2** (`addMcpTools`): WASM API complete — wiring gap is in ruflo's `buildRvfContainer`
- **Gap 3** (`get_state`, `get_todos`, `reset`): WASM API complete — MCP tools missing in ruflo
- **Gap 4** (full `WasmGallery` surface): WASM API complete — MCP tools missing in ruflo

See [ADR-129](https://github.com/ruvnet/ruflo/blob/main/v3/docs/adr/ADR-129-rvagent-full-integration.md) for the ruflo-side fix plan.

### Compatible with

- `@claude-flow/cli >= 3.10.4`
- wasm-pack 0.14.x, 0.15.x
- Rust 1.80+

### Installing

```bash
npm install @ruvector/rvagent-wasm@0.2.0
```

### PR

https://github.com/ruvnet/RuVector/pull/512