chore(release): bump ruvector-core workspace to 2.3.0, ruvector-exten…

…sions to 0.1.2 (ruvnet#685)

Version bumps to publish the recently-merged Lattice embeddings work:
- Workspace (ruvector-core + 25 sibling crates): 2.2.3 -> 2.3.0 (minor --
  new opt-in `lattice-embeddings` feature is additive, no default-build
  changes). crates.io already has 2.2.3 published; this unblocks a new
  ruvector-core release.
- ruvector-extensions (npm): 0.1.0 -> 0.1.2. Local package.json was
  stale -- the registry already had 0.1.0 and 0.1.1 published
  out-of-band, so 0.1.2 is the next available version.

Note: neither package currently has a working automated publish
pipeline (release.yml, the documented Rust release pipeline, fails
with a workflow-file startup_failure; ruvector-extensions has never
had CI publish coverage at all) -- publishing this round by hand with
the equivalent gates run locally (full test suite incl. the
lattice-embeddings feature, npm test suite via tsx since `npm test`'s
plain glob silently only runs one of five test files, dry-run for both
registries) in lieu of CI.

chore(release): bump ruvector-core workspace to 2.3.0, ruvector-exten…

…sions to 0.1.2 (ruvnet#685)

Version bumps to publish the recently-merged Lattice embeddings work:
- Workspace (ruvector-core + 25 sibling crates): 2.2.3 -> 2.3.0 (minor --
  new opt-in `lattice-embeddings` feature is additive, no default-build
  changes). crates.io already has 2.2.3 published; this unblocks a new
  ruvector-core release.
- ruvector-extensions (npm): 0.1.0 -> 0.1.2. Local package.json was
  stale -- the registry already had 0.1.0 and 0.1.1 published
  out-of-band, so 0.1.2 is the next available version.

Note: neither package currently has a working automated publish
pipeline (release.yml, the documented Rust release pipeline, fails
with a workflow-file startup_failure; ruvector-extensions has never
had CI publish coverage at all) -- publishing this round by hand with
the equivalent gates run locally (full test suite incl. the
lattice-embeddings feature, npm test suite via tsx since `npm test`'s
plain glob silently only runs one of five test files, dry-run for both
registries) in lieu of CI.

chore(release): @ruvector/rvf 0.2.3, ruvector 0.2.34 (ruvnet#641 fixes)

Co-Authored-By: claude-flow <ruv@ruv.net>
Claude-Session: https://claude.ai/code/session_017sXWL4ox5bhC86FYwJpmyK

ruvector 0.2.33 — MCP tool-count accuracy + optimizer module + contra…

…ct-test skip fix

ruvllm 2.3.0 — GPU optimization sweep (ADR-258)

New model: RDT (Recurrent-Depth Transformer) + OpenMythos recurrent-depth model
in Rust/Candle with Adaptive Computation Time halting.

Key optimizations:
- Vectorized ACT halting: 4–21× GPU prefill speedup (RTX 5080)
- candle 0.9 + cudarc 0.19: CUDA 13.0 native (RTX 5080/SM 12.0)
- KV cache pre-allocation via scatter_set: O(N²)→O(N) decode bandwidth
- On-device argmax: 128 KB → 4 bytes per greedy decode step
- GPU top-k sort for temperature sampling: 128 KB → ~320 bytes per step
- Fused CUDA ACT kernel (--features fused-act) via cudarc nvrtc
- Zero-copy tensor pointer path: candle public API, no patching needed
- True per-token streaming (generate_stream_sampled callback)
- RDT: generate_sampled + generate_stream_sampled with GPU top-k sampling

Benchmarks (RTX 5080 BF16):
  Prefill seq=512: ~91 ms CPU → 3.54 ms CUDA (21× speedup)
  Decode prompt32/gen16: 73.4 ms CPU → 44.3 ms CUDA (-40%)

ruvector 0.2.32 — ADR-256 harness router + default-deny MCP policy

chore(ruvector-wasm): publish @ruvector/wasm 0.1.31 with corrected ad…

…apter

Ships the RuvectorWasmAdapter (ruvnet#568) and restores a functional package —
0.1.30 published with only package.json (empty pkg/). 0.1.31 includes the
built web pkg/ plus the adapter that corrects similarity score, metadata
round-trip, and flat-index reporting.

Co-Authored-By: claude-flow <ruv@ruv.net>

fix: repair the self-learning intelligence/SONA pipeline (ruvnet#552)

* fix(sona): wire WASM learn-to-inference loop; single-step gradient fallback (ruvnet#519)

start_trajectory/record_step/end_trajectory now drive real TrajectoryBuilders
through SonaEngine instead of console.log stubs; learn_from_feedback
synthesizes a one-step trajectory and flushes so a single feedback call
updates MicroLoRA weights. LearningSignal::estimate_gradient falls back to
baseline-free REINFORCE only when the baselined gradient is exactly zero
(single-step / constant-reward trajectories), leaving multi-step
varying-reward behavior unchanged. 3 regression tests added.

Co-Authored-By: claude-flow <ruv@ruv.net>

* fix(ruvector): force-learn crash and learned-route namespace mismatch (ruvnet#529, ruvnet#517)

force-learn: stop calling intel.tick() on the engine-less Intelligence
wrapper (TypeError); use the native engine forceLearn()/tick() like the MCP
handler does, degrade to success:false + exit 0 when the engine is
unavailable, never throw (ruvnet#529).

route learning: Q-patterns were written as command/edit outcome episodes
under state keys route() never queries, so routing always returned default
mapping. Add recordRouteOutcome() writing agent outcomes under the exact
getState() key route() reads; trajectory-end now closes the loop (and
trajectory-begin gains --file); Intelligence.load() preserves
activeTrajectories so cross-process trajectories survive; sync route() uses
the canonical state key and includes learned agents in candidates (ruvnet#517).
New test suite tests/hooks-route-learning.test.mjs.

Co-Authored-By: claude-flow <ruv@ruv.net>

* fix(sona-npm): guard publish against missing build output; bump to 0.1.7 (ruvnet#516)

0.1.6 shipped with only README + package.json because index.js/index.d.ts
are napi build artifacts absent at publish time and npm silently skips
missing `files` entries. Add a prepublishOnly check that hard-fails without
build output; bump platform optionalDependencies 0.1.4 -> 0.1.5 (latest
published for all 7 targets). CI had the same latent gap: sona-napi.yml only
staged .node artifacts for publish — now uploads index.js/index.d.ts as a
js-bindings artifact and verifies presence before npm publish.

Co-Authored-By: claude-flow <ruv@ruv.net>

* style(sona): rustfmt the ruvnet#519 regression tests

Co-Authored-By: claude-flow <ruv@ruv.net>

---------

Co-authored-by: ruv <ruvnet@users.noreply.github.com>

ruvector 0.2.28 — remove dead external parallel-worker import (ruvnet…

…#531)

release: @ruvector/rvagent-wasm 0.2.0 — ruflo ADR-129 integration sup…

…port

- Bump version 0.1.0 → 0.2.0 in Cargo.toml and test_version_string
- Add CHANGELOG.md with 0.1.0 history and 0.2.0 changes
- Update README: correct package name (@ruvector/rvagent-wasm, not rvagent-wasm)
- Update README: Node.js target docs, JsModelProvider + addMcpTools examples (ADR-129)
- Update README: ruflo/@claude-flow/cli >=3.10.4 compatibility note
- Add .github/workflows/publish-rvagent-wasm.yml for one-shot npm publish via CI

No Rust logic changes. All ADR-129 gap APIs (JsModelProvider, set_model_provider,
addMcpTools, get_state, get_todos, reset, WasmGallery full surface) were already
implemented in 0.1.0. Gaps are purely ruflo TypeScript wiring issues.

Co-Authored-By: RuFlo <ruv@ruv.net>