Repository navigation
feat(ruvector): weight-space as a hard dependency, plus weights set-layer/perturb/learn - #1503
Merged
Merged
Conversation
…8 amendment) Promote @ruvector/weight-space from an exact-pinned optional peer to an exact-pinned runtime dependency, as @ruvector/e-means was. It stays lazy-loaded, so start-up is unchanged, and a pruned install still degrades to the install hint. - package.json: dependencies, removed from peerDependencies(+Meta) - tests: manifest assertion flipped; weight-space-cli fails instead of skipping - CI: drop the pack-and-install workaround now that the package is on npm - README/ADR-358: reword; document that ruv-fann now arrives transitively, so neural-q uses its MLP backend by default on npm installs - version bump left to the release PR, as in #1491
Expose the registry's versioned edit and fine-tune operations. Each writes a child snapshot and never changes its parent. - ruvector weights set-layer|perturb|learn; MCP weights_set_layer|weights_perturb|weights_learn - new bin/weights-edit.js (shared plumbing injected from weights.js, no circular import) - bounded inputs (epochs, rows, vector/patch sizes, seeds); file inputs confined to the working directory like save; a fine-tune that misses its held-out check writes nothing and returns accepted:false rather than an error - test/weight-space-edit.js (10 tests, real package), wired into npm test and CI - README + ADR-358 amendment; RUVECTOR_MCP_DENY verified to hide the write tools
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes
@ruvector/weight-spacea primary dependency ofruvectorand adds the missing edit and fine-tune surface to the CLI and MCP server. Three commits.Changes
@ruvector/weight-space@0.1.0is an exact-pinneddependenciesentry and is removed frompeerDependencies/peerDependenciesMeta, as@ruvector/e-meanswas in feat: add shared e-means clustering and ecosystem integrations #1489. It is still lazy-loaded inside theweightscommands, so--helpand MCP start-up are unchanged (test/startup-budget.js). The package-absent path stays as a degradation path. ADR-358 has an amendment recording this, since it reverses the "optional peer" decision.ruvector weights set-layer|perturb|learnand MCPweights_set_layer|weights_perturb|weights_learn(newbin/weights-edit.js). Each writes a child snapshot and never changes its parent. Inputs are bounded, file inputs are confined to the working directory likesave, and a fine-tune that misses its held-out check writes nothing and returnsaccepted: false(exit 0).weight-space-cli.jsnow fails instead of skipping when the package is missing.rabitq-optional.js's hard-dependency list includes@ruvector/weight-space.Behaviour change to be aware of
ruv-fannstays an optional peer but now also arrives transitively, so on a default npm installneural-quses its MLP backend instead of falling back to tabularq-learning. pnpm's strict layout may not expose it; those users installruv-fann@0.1.0directly.Write tools over MCP
The three new tools write to the registry.
RUVECTOR_MCP_DENY=weights_save,weights_set_layer,weights_perturb,weights_learnhides them (verified).Verification
test/weight-space-edit.js(10 tests against the real package), wired intonpm testand CI.weights save,perturbandlearnwork, all sevenweights_*tools are listed,learntook held-out MSE from 0.7173 to 0.0020.npm testpass locally exceptadd-extras.js, whose CLI dry-run test needs an extra that does not resolve. In my checkout every extra resolves (hoisted from a parentnode_modulesand installed optional deps), so it reports "every extra is pre-installed". This does not involve the weight-space change; CI should be the check here (its main job installs with--no-optional).Not in this PR
No version bump and no publish.
ruvectoris still 0.3.26; releasing goes through theruvector-publishworkflow, as in #1491.