This commit closes the chain started in ca0a6fa5c (standalone use recipes
landed in repo but never reached npm because no version bumps shipped).
## Changes
### Module version bumps (alpha.43)
- @claude-flow/memory → 3.0.0-alpha.17 (republish standalone use README)
- @claude-flow/embeddings → 3.0.0-alpha.18 (republish standalone use README)
- @claude-flow/security → 3.0.0-alpha.8 (republish standalone use README)
- @claude-flow/neural → 3.0.0-alpha.9 (pin @ruvector/sona to 0.1.5,
republish standalone use README)
- @claude-flow/cli → 3.7.0-alpha.43 (repin to new modules above)
- claude-flow → 3.7.0-alpha.43 (umbrella)
- ruflo → 3.7.0-alpha.43 (umbrella)
### Umbrella bump (alpha.44) — npm download badges
- @claude-flow/cli → 3.7.0-alpha.44
- claude-flow → 3.7.0-alpha.44
- ruflo → 3.7.0-alpha.44
### Neural sona pin (root fix for #2022)
@claude-flow/neural alpha.8 had `"@ruvector/sona": "latest"`, and
@ruvector/sona@0.1.6 (current latest on npm) shipped as an empty publish
— README + package.json only, no index.js or native bins. So every
fresh `npm install @claude-flow/neural@alpha.8` broke at import time
with `Cannot find package '.../node_modules/@ruvector/sona/index.js'`.
Alpha.9 pins to the exact known-good 0.1.5 (which has index.js + 7
platform-specific .node bins). Will revert to a range once
@ruvector/sona@0.1.7+ ships with content (tracked in #2022).
### npm download badges across every published package README
Added `shields.io/npm/dm/<pkg>` (monthly downloads) badges to:
- claims, cli-core, plugins (had no npm badges at all)
- plugin-agent-federation, plugin-iot-cognitum (no npm badges)
- browser, codex, mcp (had version badge, missing downloads)
- umbrella root README (now badges both `ruflo` + `claude-flow`)
The ruflo/README.md and v3/@claude-flow/cli/README.md auto-copy from
root via prepublishOnly, so they inherit the new badges on publish.
Packages that already carried downloads badges (aidefence, deployment,
embeddings, guidance, hooks, integration, memory, neural, performance,
providers, security, shared, swarm, testing) are unchanged.
## Live functional check on the published artifacts
- Fresh `npm install @claude-flow/neural@3.0.0-alpha.9`:
sona resolves to 0.1.5; `import('@claude-flow/neural')` returns
A2CAlgorithm, BalancedMode, BaseModeImplementation, BatchMode,
CuriosityModule, ... (was broken before alpha.9).
- Standalone use sections from ca0a6fa5c now visible on npmjs.com for
memory@alpha.17, embeddings@alpha.18, security@alpha.8, neural@alpha.9.
- npm dm/ badges resolve and render the current weekly download count.
Co-Authored-By: RuFlo <ruv@ruv.net>
* fix(wasm): bump default Sonnet model from 20250514 to 4.6 (#1810)
`wasm_agent_create` (gallery + plain) hardcoded
`anthropic:claude-sonnet-4-20250514` as the default model. New WASM
agents silently inherited a year-old Sonnet ID unless the caller
passed an explicit `model`, which is a quiet UX/pricing failure that
new users won't catch until they hit version-specific behaviour.
Bump to `anthropic:claude-sonnet-4-6` (current Sonnet at time of
writing) in all four locations the previous ID was hardcoded:
- `src/ruvector/agent-wasm.ts` — actual default (this is what
actually shipped to users)
- `src/commands/agent-wasm.ts` — `--model` flag description
- `src/commands/agent-wasm.ts` — example command
- `src/mcp-tools/wasm-agent-tools.ts` — MCP `wasm_agent_create`
schema description
- `__tests__/ruvector/agent-wasm.test.ts` — assertion in
"creates agent with defaults"
A future follow-up should replace the hardcode with a config-driven
default (e.g. read from `claudeFlow.modelPreferences.default`) so
Anthropic version cuts don't require a code change. Tracked
separately.
Closes#1810.
Co-Authored-By: RuFlo <ruv@ruv.net>
* fix(wasm,plugins): pin gallery test + sweep remaining stale model IDs (#1810)
Follow-up to the WASM default bump in this same PR. Reviewing the
issue more carefully, the reporter's repro path goes through
`createAgentFromTemplate('researcher')` (the GALLERY path) — and
while that path *does* inherit the new default (it passes
`model: undefined`, falling through to `createWasmAgent`'s default),
nothing in the test suite actually pinned the gallery output to the
new default. A future regression would only surface in
`creates agent with defaults` (the bare-call test), not in the
gallery test the user actually hits.
__tests__/ruvector/agent-wasm.test.ts:326
+ expect(info.model).toBe('anthropic:claude-sonnet-4-6');
While I had grep open, also swept the rest of the workspace for
the `claude-sonnet-4-20250514` literal and the matching old
Claude 4.x model IDs:
- plugins/examples/plugin-creator/index.ts (×2 — runtime + code-gen template string)
- plugins/examples/plugin-creator/plugin-creator.test.ts (assertion)
- plugins/src/collections/official/index.ts (×4 — coder, tester, reviewer, coordinator agent defs)
- plugins/src/providers/index.ts (Claude provider's models[] list — also bumped opus-4-5 → opus-4-7 and 3-5-haiku → haiku-4-5)
- plugins/README.md (example snippet)
- mcp/.claude/settings.json (modelPreferences default + routing)
Historical ADR docs (`v3/implementation/adrs/`) still reference
the old IDs by design — they capture decisions at issuance time.
Comments in the WASM agent source that reference the old hardcode
for context are kept too.
Strengthens the original closes-#1810 fix from "default works"
to "default works AND a regression of the gallery path is caught
by tests AND no other surface in the workspace ships the stale
ID anymore."
Co-Authored-By: RuFlo <ruv@ruv.net>
ruv