Skip to content

PB-001: @sparkleideas/ruvector never published — breaks agentdb dependency chain #93

@sparkling

Description

@sparkling

Defect

@sparkleideas/ruvector was never published to Verdaccio or npm. The agentdb package
depends on it as a hard dependency (ruvector: "^0.1.99"), so when npm tries to install
@sparkleideas/memory@sparkleideas/agentdb@sparkleideas/ruvector, it gets a
404, and the entire memory/controller stack silently fails to install.

This causes: 0 controllers, "Registry not available" errors, 14+ acceptance test failures.

Root Cause

Three gaps in the pipeline:

  1. publish.mjs line 164-169: explicitly skips npm/ subdirectories, preferring the
    root package.json. The ruvector root is private: true (it's a Rust workspace),
    but the publishable JS package at npm/packages/ruvector/ was skipped.

  2. config/publish-levels.json: @sparkleideas/ruvector was not listed in any level.

  3. scripts/fork-version.mjs: ruvector was not in UNSCOPED_PUBLISHABLE, so its
    version was never pinned in agentdb's dependency references.

Fix

  • publish.mjs: prefer non-private packages over private ones when resolving duplicates
  • publish-levels.json: add @sparkleideas/ruvector to level 1
  • fork-version.mjs: add ruvector and claude-flow to UNSCOPED_PUBLISHABLE
  • agentic-flow fork: keep ruvector as hard dependency (not optional workaround)

Files Changed

  • scripts/publish.mjs
  • config/publish-levels.json
  • scripts/fork-version.mjs

Upstream Reference

None — this is a pipeline-only issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    patchBehavioral fix applied to fork source

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions